Hello Jeff,

Important to know abuot cookies in Wt, and which may be the cause of the
behaviour you see: WEnvironment is constant during a Wt session. For
cookies, that means that cookies are stored in WEnvironment at the moment
that the session is started. Subsequent modifications to cookies and cookie
values will NOT be updated in WEnvironment of existing sessions. Only when
a new session is started, the new state will be reflected in WEnvironment.
I believe it's best to use the WEnvironment to initialize some of the
settings of your application in your application's constructor, but for
state during the execution of the application you should rely on the state
variables of your classes rather than on what is stored in cookies (since
the cookie state changes will not be reflected).

BR,
Wim.


2014-09-30 2:53 GMT+02:00 Jeffrey Scott Flesher Gmail <
jeffrey.scott.fles...@gmail.com>:

>  I have an App that depends on cookies to change its theme, I know the
> cookie changed, but it changes back when I click on a menu item or refresh
> the page, the only thing I can think of is that its Crashing the Session, I
> have tired to isolate the code to no avail, I made smaller projects as
> proof of concept, that work fine, but once I put it all together it starts
> getting stupid, meaning it forgets the cookie value.
>
> The Project is at:
> https://github.com/WittyWizard/install
>
> I have a Forum page at
> http://redmine.webtoolkit.eu/boards/1/topics/9713
> that tries to explain the problem, and has sample code, but I have no idea
> how to troubleshoot a Crashed Session, if that is what is happening, can
> anyone give me any clues as to why this is happening and how to fix it, or
> how I should proceed, I am stuck.
>
> You can see the app here:
> http://wittywizard.org/
> The Options menu has a Theme, pick a different theme, then click on a
> different menu item, and not it reverts back to the same theme, the theme
> is stored in a cookie called "wwtheme".
>
> Currently I only have content for English, so the Languages appears not to
> work, but it does, the CMS works great despite this problem.
>
> Thanks
> Jeff Flesher
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> witty-interest mailing list
> witty-interest@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to