Scheduled for resolution Choice of theme when not logged in does not persist long enough

Hey. The dev team is on Christmas holidays until early January. We'll start to see some action once they're back. Between now and then we're in a triage phase and prioritizing all the issues so they can be addresses in the right order of importance.

This is something that ties in to an earlier request I made with the dev team about storing these preferences in the database rather than a session. I'm going to update this to "scheduled".
 
Great, thanks Jason. Happy holidays to you and the dev team!

A related question: Will the database also remember the "wide" setting? I'm finding the "dark and wide" combo to be my settings of choice, it's very easy on these aging eyes. Right now the wide setting has to be reasserted after every login, and is unavailable if not logged in..
 
I set my theme to Dark, narrow, no sidebar on the Mac. Waited over an hour and moved to Windows. I have exactly the same settings here now.
However, when not logged in on Windows, I saw the default layout. That's what I would expect, as the fourm doesn't know who I am when not logged in.
 
Great, thanks Jason. Happy holidays to you and the dev team!

A related question: Will the database also remember the "wide" setting? I'm finding the "dark and wide" combo to be my settings of choice, it's very easy on these aging eyes. Right now the wide setting has to be reasserted after every login, and is unavailable if not logged in..
That's how I would like it to work.

It will also give us good stats to see how many people are making use of each theme, width setting, sidebar on/off, etc.

Jut wanted to confirm that, on two different Windoze machines (Win7 and XP), the "wide" setting is not remembered from one login to the next.
Session data is tied to a cookie, cookies are tied to a browser, I doubt the apparent light-weight implementation would go so far as to try to merge session data (and decide which data to delete / has preference in the merge) if someone logged in. That's all better handled by just putting this in the database.