Module access control

[LostKobrakai]

With pages it's possible to circumvent access control manually in templates, but I've an page action module I'd like to control the access to in the backend. But this does prevent me from triggering the page action from my templates via the api, as users might not have enough access rights to use it. Is there any way around this?

[Martijn Geerts]

Maybe when you add page-view permission to the info array of that module?

[LostKobrakai]

Even guests have page-view access. Shouldn't this therefore deny the backend access control. Essentially I don't want all editors to be able to batch geocode addresses, but I'd like to use the module to geocode single instances in my templates.

[kixe]

I think in your template you can extend the users role on runtime.

$user->set('roles',41);