The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.The module adds an 'edit domain content' permission, but the documentation, and the rest of the code in the module, refers to the 'edit domain nodes' permission. As a result, users with 'edit domain content' aren't allowed to edit content on their assigned domains.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 1074144-perms.patch | 20.4 KB | agentrickard |
| #6 | 1074144-perms.patch | 10.21 KB | agentrickard |
| #2 | 1074144-perm.patch | 578 bytes | agentrickard |
Comments
Comment #1
agentrickardSame is true of the 'delete domain content.'
/me blames the core terminology change..
Comment #2
agentrickardThis patch will also need an update hook.
Comment #3
yrro commentedI did a find and replace of all 'edit domain nodes' strings in the domain and domain_content modules, changing them to 'edit domain content' and permissions seem to work as I expect. I did the same for 'delete domain nodes' -> 'delete domain content'.
The 'affiliated content' list now has the following warning at the top. I will file this as a separate bug if you like.
Comment #4
yrro commentedAh, changing it back would also fix the problem. I assumed the renaming was deliberate! :)
Comment #5
agentrickardThe renaming doesn't matter much, now that title is separated. But fixing code may be easier than an update hook for end-users. Revising patch.
The other is a separate bug.
Comment #6
agentrickardPatch try #2.
Comment #7
agentrickardPatch that includes a docs fix.
Comment #8
agentrickardNeeds an update hook, too, for those coming from D6.