Is anyone familiar enough with both ThemeKey and Administration Theme (6.x versions) to describe how the two compare? I realize they're built with some overlapping, but ultimately differing features, which is why i think a comparison would help more users than just me. In any case, please let me explain my use case...

I would like the ability to extend Drupal's default administration theme option (allowing me, as Administration Theme does, to specify more pages than simply admin/* that should render in my chosen administration theme). This configuration, however, is not yet ideal, in that i've created roles that have limited administration permissions and yet when Administration Theme's "access admin theme" permission is granted to these users, ALL administration pages, whether the user is permitted to access them or not, are rendered in my administration theme. I'd prefer that these users with limited administration privileges see an "Access Denied" page rendered in the site's default theme, rather than an "Access Denied" page rendered in the administration theme.

Anyone experienced in using both modules? Thanks for any and all help...

Oh and lastly, i've also posted this topic in ThemeKey's Issues and i therefore ask the forgiveness of the respective maintainers of each module if this is at all in violation of Drupal standard practice.

Comments

John Pitcairn’s picture

Hmm. I can't speak to ThemeKey's abilities, not sure whether you'd need to explicitly specify the desired theme there, ie would it pick up the current admin theme even if you changed that?

For the 403 if the user doesn't have access, make a custom Access Denied node, exclude that path in Admin Theme settings?

[edit] nope, won't work, that node gets included, but the path is still the one for which the user has no access.

justy’s picture

Status: Active » Closed (outdated)