Opened 15 years ago
Last modified 20 months ago
#6433 new enhancement
Set the theme per user basis
Reported by: | Gasler Radu | Owned by: | Olemis Lang |
---|---|---|---|
Priority: | normal | Component: | ThemeEnginePlugin |
Severity: | normal | Keywords: | theme, user, preferences |
Cc: | lkraav | Trac Release: | 1.4 |
Description
It would be nice if the theme could be selected in preferences by each user.
This way each user could select the desired theme from the list of available themes, like for example he can now select the Pygments Theme.
Attachments (0)
Change History (8)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Cc: | lkraav added; anonymous removed |
---|
comment:3 Changed 11 years ago by
Owner: | changed from Noah Kantrowitz to Olemis Lang |
---|
comment:4 follow-up: 6 Changed 11 years ago by
Hey olemis. Can you tell me about your plans for this ticket? I'm assuming you have interest? Any estimation on difficulty? Do you need help?
comment:5 Changed 11 years ago by
Cc: | Ryan J Ollos added |
---|
comment:6 Changed 11 years ago by
Replying to lkraav:
Hey olemis.
:)
Can you tell me about your plans for this ticket?
/me working on it ...
I'm assuming you have interest?
sure !
Any estimation on difficulty?
In order to store theme config data on per-user basis, we need a mechanism to store the equivalent of current config options in the DB and bind them somehow to the user (session data ?) . There are other (related) issues :
- How much configurable ?
- what to do about custom + advanced theme admin panels ?
- what about color schemes et al. ?
- What are the interactions with #11463 ?
- should we forget about this and support per-user customizations based on pre-processor style sheets ?
- Should we offer ways to limit the themes that may be chosen in a given environment ?
- I'm thinking of a multi-env or multiproduct (e.g. Bloodhound) deployment with different sets of allowed themes in each case .
... those are open questions we still need to figure out
Do you need help?
If anybody has any patches for me to review they will be welcome , of course
comment:7 Changed 4 years ago by
Cc: | Ryan J Ollos removed |
---|
comment:8 Changed 20 months ago by
Trac Release: | 0.11 → 1.4 |
---|---|
Type: | defect → enhancement |
Absolutely +1. This is a critical component of any theme development workflow. Regular users can keep on working on a stable theme, but development on real data, on real amounts of data, can keep happening on another.
Premiere theme switcher on WordPress is http://plugins.trac.wordpress.org/browser/toolbar-theme-switcher/trunk
It basically sets a browser cookie with the theme slug and then re-assigns the theme based on the cookie value early in the request. Inspecting the code should provide ideas how to transfer this to Trac.
Is there any reason above strategy wouldn't work here?