Closed (fixed)
Project:
Role Theme Switcher
Version:
6.x-1.5
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
5 Nov 2009 at 05:38 UTC
Updated:
8 Sep 2010 at 15:00 UTC
Hi, I used Role theme switcher mainly to force admin theme to the front-end theme for users with certain roles (general site users rather than admins) but the node/edit pages they are exposed to (their profile nodes for example) are showing up in the back-end theme which is not assigned to their role.
How do I use the chosen role-based theme for node/edit pages?
Comments
Comment #1
tiutiun commentedHmm
It looks there may be some other modules that could set up other themes for node/edit pages
Could you please:
1. Send me screenshot of your Role Theme Switcher preferences
2. Screenshot of "Administration theme" settings. It is here: /admin/settings/admin
Thank you
Comment #2
tiutiun commentedUP
Any news?
Comment #3
ta5ae commentedDear all,
I have a similar problem. I want to use role them switcher module to change the theme of the site, including the administration theme, used for specific roles.
At present some pages, such as /admin/content/node, appear in a different theme than the one selected for that role, in my case the default theme.
Current settings:
Role theme switcher
Anonymous user: Default (a custom theme)
Authenticated user: Garland
Administrator: Garland
Editor: Root candy
I have this set up for the 'Administration theme': Use system default and 'Use administration theme for content editing' unchecked.
It seems as if, the administration theme setting overrides anything set using the role theme switcher, which is not what the documentation suggests.
Thanks.
Comment #4
tiutiun commentedHello, ta5ae
Thank you very much for debugging
Yes, it looks that Role_Theme_Switcher doesn't override "Administration Theme" settings.
By the way, when you set Administration Theme to "System default" and uncheck "Use the administration theme when editing existing posts or creating new ones" - then Role_Theme_Swither behavior is the same as expected?
Comment #5
ta5ae commentedHi,
If I do the above and keep the role theme switcher settings as described above, I still have the problem of this page /admin/content/node appearing in the default theme for the editor role instead of the specified, root candy.
However, if I change the theme associated for the Editor role to be Garland then the theme stays switched for this page, /admin/content/node. NB: I cannot make this happen for other themes. For instance, I tried various other themes as in place of root candy and Garland with the settings described above to no avail. Also switching all non anonymous roles to use the same non garland theme, still has the problem.
HTH.
Comment #6
tiutiun commentedHello, ta5ae
Could you please connect me via
Skype: serj.tiutiun
or
ICQ: 322379814
I'll try to help you online
Comment #7
venutip commentedI wrote a small module based on RTS that lets you specify the admin theme by role. I could release it as a separate module, but I think it would make sense if we merged the changes into RTS.
@tiutiun, contact me if you want to have a look at the module or discuss this more.
Comment #8
tiutiun commentedThe setting Home->Administer->Site configuration->Administration theme "Use administration theme for content editing" - if it is enabled, this setting overwrites the Role_Theme_Switcher behavior. So probably you would like to disable "Use administration theme for content editing" setting.
Role_Theme_Switcher consciously do not overwrite "Use administration theme for content editing" - if something can be done via Drupal interface just disabling the checkbox, it should be done there.
Could you please check if this text brings some light to the problem?
Comment #9
GBain22 commentedHi,
I'm having the same issue, if you disable "Use administration theme for content editing" then set the specific role to use "Garland" then they constantly see Garland whether viewing or editing the page. However, the admin now has to use Garland instead of the specified admin theme.
Are there any advances with this? I've tried a few modules but none seem to work the way it's intended to. They were: "Theme Setter" and I also tried "Sections".
Cheers, Garry.
Comment #10
tiutiun commentedHello, Garry,
If I understood correctly - at the moment you have only two roles: Authenticated user and Anonymous user, and you have assigned Garland to Authenticated user. Am I right?
If it is so - then it is an expected behavior.
What would I advice: if you want to show two different themes for admin and for regular authenticated users, you should create a separate role for admin, and you should assign to this role the theme that you would like to show to admin
Please let me know if it works for you
Thank you
Comment #11
tiutiun commentedComment #12
rhapsodic commentedHey there,
Great module, but I'm wondering if it were at all possible to add a check box that would allow for theme switcher to override admin theme for content?
Here's the situation.
I have 3 roles.
Role: Anonymous: Only views the "front-end" theme.
Role" Authenticated: Only sees the "front-end" theme. But this role can add forum topics and small things. (But I don't want this role to use the "admin" theme)
Role: Administrator: Sees front-end for viewing, but uses "admin" theme for editing content. (So I have to use the "Use administration theme for content editing" checkbox).
But of course this check boxes overrides everything. So I need the option to override that checkbox, but for only the "authenticated" role.
This possible somehow?
Thanks!!
Comment #13
tiutiun commentedHello rhapsodic
I would suggest to create a separate role for users, that are "authenticated" and are not "admins", and assign to this role a "front-end" theme
RTS cannot be used in your case to override theme for admin, because it will use the same theme for admin and front-end pages, so I would advice to create an additional role for authenticated non-admins, for ex "common users"
Please let me know if this solution works for you
Thank you
Comment #14
rhapsodic commentedI see what you mean.
It would be nice though later to have an option that will make a Role use a certain theme no matter what.
For example:
1) I had "Use administration theme for content editing" checked (turned on)
2) I had a specific role that WAS an administrator, but I wanted to use the 'front-end' theme, no matter what, so this role would see only the front-end theme for both admin pages and front-end pages.
So the result would be:
1) I can have one type of administrator that would see both front-end and admin themes.
2) I can have another type of administrator that would only see the front-end theme.
Thanks for the help though :D :D :D
Cheers!!
Comment #15
tiutiun commentedI see your point and agree with it :-)
It will be fixed in next release, possibly these weekends
As temporary solution - you can make lower the weight of module "RTS", from "-2" to "0"
You can do it in table "system" or using additional module util
High weight was used to avoid problems with modules, that start using theme before RTS was able to change it, like "nodewords"
I believethat ability to override "Use administration theme for content editing" checkbox by default is more important, than solving possible problems with other modules, as far as these problems can be easily solved by attributing proper weights to these modules
Thank you for the valuable feedback
Comment #16
tiutiun commentedCould you please check last version, 6.x-1.6
I've tried to fix the issues - could you please test it, if it works for you?
Thank you
Comment #17
tiutiun commented