Category: "High Priority!"
What I mean is that every blog can have a totally different domain name (URL), which makes use for having different blogs on subdomains or other domains that are directed to the same webspace using ServerAlias.
What's with images or other media related stuff? this should be taken from each blogs path (perhaps you could enter a different "$img_url" for each blog, the same with media. It should be allowed to use the same directories for different blogs.
When you have subdomains that are simply directed to the same filesystem's path images and stuff like that (skins) would be pulled from the same directories anyway.
This is open for suggestions.
This topic is about the FRONT office and about FRONT office skin switching.
Currently, when you use the skin switcher, the desired skin is stored in a cookie named xxx_evostate.
Note: This selection is saved in a cookie because it has to be persistent accross Sessions, even for non registered users. Thus, this is neither a Session variable nor a UserSetting. And this should stay that way!
The selected skin is applied to all blogs.
Some users want to be able to select a different skin for each blog.
We could enable this with a config switch.
In that case the xxxx_evostate cookie would store a little more than just the latest chosen skin name.
It would store the latest chosen skin name, followed by the last skins chosens for each blog.
Example: I am on blog #3 and just selected the guadeloupe skin.
The xxx_evosatet cookie sent would then contain:
- when I switch to blog#2 it will display the custom skin.
- when I switch to blog#3 it will display the guadeloupe skin.
- when I switch to blog#4 it will not find a saved skin, so it will use default one for that blog.
please keep in mind, we may add other variables (not skin related) in the evostate cookie in the future.