Posted by beeradb on March 7, 2009 at 7:04pm
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | node.module |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
| Issue tags: | UBUserTesting2009 |
Issue Summary
Users expect content permissions to be listed under under a heading with "content" and not "node." The interface for setting up content is "content type" with no indication that this is a "node."
Comments
#1
This is a patch to fix the issue referenced in the title: 'Node permissions should be moved under "content" heading'.
The fix is to change the node.info file so that that 'name' is 'Content', rather than 'Node'. The only place core references this value for the node module is on the permissions page, so changing it won't add confusion elsewhere. It seems *possible* that something in contrib might want to list out modules, in which case 'Content' might be a little confusing. However, I would think that would be an edge case and that it is more important to make the permissions screen more readable.
The other option would be to allow modules to provide a secondary, more colloquial name for their module in the .info file. However, it seems like that's really what the 'name' value is to begin with.
#2
We should fix the UI issue, but not by renaming node.module just to fix one string. Clever solution, but, no.
#3
catch - I realized this was ill-concieved after spending a little time on patches and realizing that this is a symptom of a problem that's being discussed in several other patches. It is kind of fun to put a bold, impossible patch out there though. :)
#4
Still a valid issue after the release of 7.0. Moving to 8.x.