Bug #785
closedmyamiweb setup wizard need to modify define('GP_USER', 'users') in config.php correctly
0%
1. If they don't have a "users" group, they can create a new group called "users", and set the privilege to "Administrate/view only owned projects and view shared experiments".
2. If they already have "users" group, and the users group has other privilege than the default users privilege, they need to create a new group for default user and and set the privilege to "Administrate/view only owned projects and view shared experiments". Then edit the config.php file on line 74. Change the 'users' to the new group name they just created.
Description
We can not assume that past users creates any group other than the one administrator user is in. Current upgrade gives all other available groups user privilege. but retain their group name for obvious reason.
Setup wizard should know how to deal with each of these situations:
1. only one group (will have administrators privilege after schema-r127857.py)
2. more than one group but no group is named 'users'
3. more than one group and the group the administrator user is in is called 'users'. This will cause new users to default with administrator privileges.
4. more than one group and a group other than the administor group is called 'users'.
Updated by Eric Hou over 13 years ago
- Status changed from New to Assigned
for now before this issue got fixed, the upgrade users can do:
1. If they don't have "users" group, they can create a new group call "users", and set the privilege to "Administrate/view only owned projects and view shared experiments".
2. If they already have "users" group, and the users group has other privilege than the default users privilege, they need to create a new group for default user and and set the privilege to "Administrate/view only owned projects and view shared experiments". Then edit the config.php line 74, change the 'users' to the new group name they just created.
Thanks.
Eric
Updated by Amber Herold over 13 years ago
- Tracker changed from Feature to Bug
- Affected Version set to Appion/Leginon 2.0.2
- Show in known bugs set to Yes
Updated by Amber Herold over 13 years ago
- Target version changed from Appion/Leginon 2.1.0 to Appion/Leginon Future Version
Updated by Eric Hou over 13 years ago
- Status changed from Assigned to Won't Fix or Won't Do
This only effect to people using old version of the Leginon or Appion. Right now, all the external users should be fine