You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Florian Holeczek (JIRA)" <ji...@apache.org> on 2010/07/07 12:13:50 UTC

[jira] Closed: (JSPWIKI-652) Save user preferences on the server side

     [ https://issues.apache.org/jira/browse/JSPWIKI-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Holeczek closed JSPWIKI-652.
------------------------------------


Closing

> Save user preferences on the server side
> ----------------------------------------
>
>                 Key: JSPWIKI-652
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-652
>             Project: JSPWiki
>          Issue Type: New Feature
>            Reporter: Jürgen Weber
>            Priority: Minor
>             Fix For: 3.0
>
>
> Initial idea from Dirk Frederickx:
> we could introduce the notion of a 'version' number for user preferences. This prefs-version-nbr should then be stored in the cookie. Upstepping this version number could be used to force a rewrite of all cookies, avoiding incompatibilies between server side settings and cookies.
> This could be useful for things like timeformats, introduction of new skins, introudction of new editors, etc. Also useful when upgrading JSPWiki from v2.4.x to v2.6.x.
> My comment:
> I'd refine this to two version numbers: one internal for JSPWiki version changes (automatically trigger a cookies update) and one in the properties file for the site admin to change and therefore trigger a cookies update manually after configuration changes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.