Closed (works as designed)
Project:
Custom Permissions
Version:
7.x-2.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
14 Aug 2011 at 02:00 UTC
Updated:
26 May 2025 at 08:52 UTC
Jump to comment: Most recent
Comments
Comment #1
Docc commentedNot seeing a user case here. The module uses the menu access system wich isn't build real time. So node tokens etc wont work.
Maybe you're looking for the wildcard option?
Comment #2
Anonymous (not verified) commentedThanks for the respons.
At this moment I made a setup with the wildcard, but it gives too much power to users.
I am developing a site with domain access (+ domain-theme). The administrator of a (sub)domain can pick his own theme and make his own theme setting, access is denied for other domain themes and settings.
At the moment my custom permision setup is "admin/structure/domain/theme/*": with the wildcard. The problem is that a domain administrator has access to the domain setup for all subdomains. Domain access works with tokens, so when I could change the wildcard in de domain number (a domain access token) then it solves this issue.
I know, the "Domain acces" module should have his own theme/domain access permissions setup, it has not, so Custom Permissions came in my mind.
Maybe the use of tokens in Costum Permissions could also be handy for access permissions of views with arguments or in other situations where you want to control the access depending on tokens.
.
Comment #3
Docc commentedToken integration wont solve your problem.
You have to fill in the domain id yourself for every domain you want a permission for ex: admin/structure/domain/theme/5, admin/structure/domain/theme/4 etc
Or create a menu alter function yourself.
Comment #4
Anonymous (not verified) commentedMenu token takes care of that: http://drupal.org/project/menu_token. I have made a menupath setup with admin/structure/domain/theme/[current-domain:id]