Let’s say you have a very visually attractive site in Plone and its design is not using any of Plone’s features besides navigation and rendering of contents (don’t ask…). It’s absolutely disturbing when logging in as site member and you can’t find any of the helpful config links because the lovely design won’t support it.
But there is help in Plone itself. Every user can select its own skin. In theory! But this useful feature does not work in Plone 2.5.2, which is the current release. Fortunately in the upcoming 2.5.3 RC1 skin selection is re-enabled and it works.
Update: It kind of works or should I say it sucks? Plone does not use the saved (is it even saved in Plone?) member skin if you log in for the first time. Then the portal’s default skin becomes the user selected skin. A user selected skin must stay the same wherever I log in. As a simple workaround you can edit the Cookie, but that’s not what I want my customers to do…
