The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.On a Drupal 4.7 site, I gave a user the 'administer content types', who can now create any content type she likes, but she cannot create or edit any of them until someone with ''administer access control" permission grants it to her.
Is there a reason this is set up this way?? It seems kind of silly.
If this is a bug and not a feature, I'll submit a patch to flexinode.module, since the change in flexinode_access is trivial to enable this.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | flexinode-issue-55614.patch.txt | 2.16 KB | Torenware |
Comments
Comment #1
Torenware commentedHere's a patch that implements this behavior. With this patch, someone with 'administer content types' will be able to create flexinode content types without requiring permissions for each content type separately.
Comment #2
Torenware commentedAaron Welch's reviewed the patch and at his advice, I've checked it into HEAD.
Comment #3
Bèr Kessels commentedThis patch makes sense. And therefore I will not revert it. But please make sure you get some reviews before committing.
flexinode is one of the more popular modules. Do not just add features!
Comment #4
Torenware commentedAaron Welch (crunchywelch) is the current maintainer of the module. He reviewed the patch and told me to check it in.
I assume that before you'd revert my (or someone else's) patch you would ask Aaron first ;-)
Rob
Comment #5
(not verified) commented