The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.There's just one permission "administer meta tags" which is used for accessing the Defaults page as well as the Settings page.
I think there should be a separate permission for accessing the Defaults page. We run a large multisite distribution and we want to give our site owners the ability to modify the default metatags, but don't want them to be able to change the settings for the metatag module.
For now I can do this with hook_menu_alter and my own permission, but I was a bit surprised to not see this baked into the module, so thought I'd create a request.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | metatag-separate_permissions-2890845-4.patch | 4.23 KB | byronveale |
| #2 | 2890845-add-configure-defaults-perm.patch | 4.26 KB | bkosborne |
Comments
Comment #2
bkosborneThis adds a new permission "configure meta tag defaults" and changes the access checks so a user must have this permission to view the "Defaults" page and to modify/add any of the default tags. There's also an install hook to assign this permission to all roles that already have the "administer meta tags" permission, so people won't lose access on upgrade.
Comment #3
damienmckennaThanks for putting the patch together, bkosborne. This would be a reasonable idea. The last step will be to update the tests so that they pass and so that both permissions have appropriate test coverage.
Comment #4
byronveale commentedThe 1.28 release of Metatag has a hook update that conflicts with the one introduced by this patch (they're both 7116). Here’s an updated patch that fixes the conflict. Sorry, it still doesn't update the tests…
If anyone has already used the original patch, and is stuck with an update that won't apply, I can offer another patch (this was our situation).
Comment #5
damienmckennaI thank you for your contribution to the Metatag module and the Drupal community as a whole. The D7 version of this module is no longer supported, so I am closing this issue.