Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In one of my projects I don't want users (except for user no. 1) to be able to change a node default priority or a profile default priority while they're creating or editing a node or a profile. Is there any way to disallow them to do this know?
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedDrupal is designed to allow you to create custom modules with hooks that will alter the behavior of predefined items. You can code this in a custom module. There may be a module already created you can use, you'll have to do a little research.
Comment #2
Dave ReidUnless you're giving those users the 'administer xmlsitemap' permission then they won't see those XML sitemap settings.
Comment #3
adr_p CreditAttribution: adr_p commented@earnie
This is what I did, I wrote a custom module which defines additional permission 'alter xmlsitemap defaults for profiles'. The module denies access to xmlsitemap element on profile forms for everyone not having this permission. If somewhere already exists a module allowing me to do this, please write back, however I didn't find such.
@Dave Reid
In fact, even users without 'administer xmlsitemap' permission, but having 'administer users' can see those settings (on profile forms in this case) and are allowed to overwrite defaults. I don't like 'administer user' or 'administer nodes' permission (they're too powerful as for me) so I decided to write this issue.
What do you think about helping admin assinging permission more reasonably?
Thanks for your replies!
Comment #4
adr_p CreditAttribution: adr_p commented@Dave Reid
Please examine if it is a bug what I've wrote above. Also please consider introducing more granular permissions.
Thanks.
Comment #5
Dave ReidI've debated adding a lower-level permission to be able to edit XML sitemap links, but I fully support that if someone has the 'administer nodes' permission then they should be able to edit anything on a node. I feel pretty much the same for users with the 'administer users' permission. They should be able to edit anything on that user.
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commentedI still think this is a "won't fix". The user can create finer grained permissions using the API hooks as well as modifying the form elements displayed with the access information so that they don't display.
Comment #7
adr_p CreditAttribution: adr_p commented@earnie
And that's what I did, even before I wrote the issue. But in my opinion that feature should be included in the module as fine grained permissions are a big advantage. Besides, I think it'll be warmly welcomed on sites which run editorial systems.
Comment #8
gobinathmAs D6 is in EOL, I believe there won't be any support / fix for a problem identified in 6x going forward. Given the fact that D6 is already EOL. Hence i guess this issue can be closed.
Changing the status, if incorrect pls revert the status.