2013-06-18, 16:41:10
Hi, I'm not sure how to describe...
In this special case I want to have one or more pagewide accessable fields; for example called "myCustomCssFile='normalstyle.css'" which I can use in my templates. After clicking a button "Toggle Size" I want to change this variable to "myCustomCssFile='bigstyle.css'", reload the page and so use the other css file for the template. After changing to another page, the field must stay. So I think it must be forwarded in the GET parameters, also in user friendly urls somehow, so it has to be appended to every site-intern link. At this moment, I make this functionality at client side using jquery and cookies, but thats not really stable, because of caching problems for e.g. I hope someone understood what I want to say... Sorry... Is there already a mechanism included which makes me able to use custom GET-Parameters?
In this special case I want to have one or more pagewide accessable fields; for example called "myCustomCssFile='normalstyle.css'" which I can use in my templates. After clicking a button "Toggle Size" I want to change this variable to "myCustomCssFile='bigstyle.css'", reload the page and so use the other css file for the template. After changing to another page, the field must stay. So I think it must be forwarded in the GET parameters, also in user friendly urls somehow, so it has to be appended to every site-intern link. At this moment, I make this functionality at client side using jquery and cookies, but thats not really stable, because of caching problems for e.g. I hope someone understood what I want to say... Sorry... Is there already a mechanism included which makes me able to use custom GET-Parameters?
So I'll simply use sessions. Thank you for reminding me of their existance 