Correct behaviour for theme: no serialization for the moment - do we need one?
Or is it a bug?
----------------------------------------------------------------------------------------------
Key: TEMPLATES-460
URL: http://www.jahia.net/jira/browse/TEMPLATES-460
Project: Jahia Default Templates / Web Design / General Usability
Issue Type: Bug
Components: Corpv3 Default Core Templates
Affects Versions: Templates 6.0
Environment: 22906
Reporter: Stephane Croisier
Assignee: Clement Egger
Fix For: Templates 6.0
There is no serilaization of the themes for the moment (or at least it looks
like that).
If I logued myself with a user (john) which has no specific rights on the site
(just created a new user and logued on the site with it) and if I change the
theme (to organge), the theme is not saved when I logout and relogin. Same is
true if I logued myself with the same John user but on another browser
instance. I am still getting the default theme.
So should'nt the them be saved in a user preference (Preference API) if we want
to let each user chhose its own theme.
Or is the thems choosed by an author in edit mode (staging) and then need some
validation in order to be be "published". Anoynmous or Read-only logued user
could not then change the current chose theme by the marketing authors (e.g the
Marketing decides to resking the intranet to a "winter" look&feel). In such a
case the theme should be stored in a Jahia field which will have some different
staging and live values.
What was the correct behaviour decided for Andromeda? If both, how could we
test both behaviours?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
