Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.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."
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | node.info.patch | 558 bytes | chrisshattuck |
Comments
Comment #1
chrisshattuck commentedThis 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.
Comment #2
catchWe should fix the UI issue, but not by renaming node.module just to fix one string. Clever solution, but, no.
Comment #3
chrisshattuck commentedcatch - 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. :)
Comment #4
Tor Arne Thune commentedStill a valid issue after the release of 7.0. Moving to 8.x.
Comment #5
xjm(Merging "node system" and "node.module" components for 8.x; disregard.)
Comment #19
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #20
acbramley commentedPermissions are grouped by module name and Node obviously won't be changed. Content has a much broader scope now that we have content entities. This is a won't fix I think.