Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
user.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Oct 2007 at 14:55 UTC
Updated:
26 Oct 2007 at 12:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
catchI agree. I've clicked the wrong one before as well, and "Permissions" is standard across a lot of systems. Tentatively marking RTBC.
Comment #2
catchHit submit too fast, sorry.
This would also make for less confusion with node_access modules.
Comment #3
gábor hojtsyI agree, but I'd love to see some more people chime in about this.
Comment #4
dries commentedI agree 300% but I think we want to change the path as well (admin/user/access should become admin/user/permissions).
Comment #5
anders.fajerson commentedAgree, I'll roll a patch. This then needs to go into the D5 -> D6 documentation since a lot of modules have that link in their INSTALL.txt.
Comment #6
catchIn which case we should change the permission to "administer permissions" for consistency.
Comment #7
anders.fajerson commentedThere should be more links to /access in core.
Comment #8
catchthat's true.
Updated patch changes all admin/user/access to admin/user/permissions
it also changes "Access control" to "Permissions" where this was relevant (i.e. not in relation to file handling etc. where access control seems fine as general terminology)
Comment #9
anders.fajerson commentedThere probably has to be an upgrade path if a permission is renamed. I looked in system.install but couldn't find an example of this.
Comment #10
catchalso true. Requires a regexp or MySQL REPLACE on the permissions table.
will work, although presumably not on pgsql.
I can't find any such permission update referenced on drupal.org though so hopefully someone will come along who knows.
Comment #11
gábor hojtsyInstead of an SQL level regex, grab the permisisons to PHP, and replace there. It is more portable SQL wise.
Comment #12
anders.fajerson commentedHere is a shot at it. Tested on MySQL.
Comment #13
sun- Even after clearing the cache, permissions are still in admin/user/access, title is still 'Access control'.
- If I enable 'access administration pages', 'administer users' and 'administer permissions' for a role (auth users) and login with a user in that role, 'Access Control' does not appear in the menu (below 'Administer').
Comment #14
JirkaRybka commentedI just tested the patch, and it works fine for me. The above problems were probably caused by patching an existing installation without necessary updates - I was able to reproduce these problems by patching on existing install, and I solved them as follows:
- The first bullet above just needed a menu-rebuild, to recognize new changes. Solved by enabling/disabling a module.
- The second is caused by renamed permission. Solved by update.php run.
Neither exists on a new install. So I can confirm that the patch works well, including the upgrade path. I'm not setting RTBC only just because I haven't time to check all the other changes in detail.
Comment #15
anders.fajerson commentedFound a leftover link in upload.module. Unless my search is failing me, this should be the last. The upgrade path still needs a code review and there needs to be a note about this change in http://drupal.org/node/114774 (Converting 5.x modules to 6.x). Here is a start:
"administer access control" permission renamed to "administer permissions"
The "administer access control" permission has been renamed to "administer permissions".
5.x:
6.x:
"Access control" page renamed to "Permissions" and new URL
The page "Access control" (found at Administer > User management > Access control) has been renamed to "Permissions". The new URL to this page is /admin/user/permissions instead of /admin/user/access. Any documentation (e.g. INSTALL.txt) pointing to this page should be updated.
[Example needed?]
Comment #16
anders.fajerson commentedHere is a list with modules that uses the "administer access control" permissions in contrib. Even though it's a bit late in the release cycle to break modules it's not that many that will be affected...
accounttypes.module 1
level1.module 1
netforum_authentication.module 2
nf_handshake.module 1
phpids.module 1
roleassign.module 9
role_delegation 3
taxonomy_access 1
Comment #17
heine commentedWe are already past the first beta and I don't think it is such a huge usability bug (isn't even marked as such) that it warrants a patch for 6.
Comment #18
nicholasthompsonI +1 this idea too - I've always wondered why it was never called Permissions!
Comment #19
hass commented+1 - Very good usability change...
Comment #20
catchSince both Gabor and Dries have chimed in positively on this thread, moving back to 6.x for them to make the decision on whether it gets postponed or not.
Comment #21
JirkaRybka commentedJust to join the recent movement - +1 from me too, and rather a "big" one (as far as I can say that): For me, this is one of the things, which were difficult to figure out when I first started with Drupal.
Comment #22
anders.fajerson commentedCould we please stop voting on this and instead get a code review/test so we can set it to "ready to be commited"? - So core commiters can decide whether it's for Drupal 6 or 7.
Comment #23
JirkaRybka commentedOK, I tested this again - didn't apply after recent changes to comment module, so attaching the same patch re-rolled.
Otherwise I see no significant changes from the version I already examined: Page and relevant links renamed to 'permissions', one permission renamed with a working upgrade path provided, otherwise no change and everything works fine. I also can't find any more links to be updated (not that I tried too hard, though), and the whole seems good to me.
So if core commiters decide for D6, I would vote for RTBC.
Comment #24
JirkaRybka commentedPatch still applies with just one offset, and I hope there's nothing wrong if I set it to RTBC, as it's really how I feel about it. We were waiting just for a commiter's decision between 6.x and 7.x, which will be done prior to commit anyway I believe.
Comment #25
gábor hojtsyI discussed this with Dries and he said this should be fixed, so looked over the patch line by line and as everything looked nice, committed.
Marking "patch (code needs work)" so the update docs will be updated.
Thanks.
Comment #26
anders.fajerson commentedThanks. I don't have access to add documentation, but I started with some at #15.
Comment #27
catchI do have access to docs, and have updated with text from #15 with minor additions. Thanks!
Marking back to fixed. If any more needs to be done to docs, please bump this issue/mark back to needs work.
This will also need to go into the new versioned core documentation which I believe is targeted at 6.x right?
Comment #28
gábor hojtsyComment #29
(not verified) commented