Fernando, I found a key to this issue – it happens when the ‘Refresh page after updating preferences’ setting is on, and the plugin seems to work fine with that off. It’s probably just asynchronous calls made with the ajax (updating cookie settings) and page refresh at the same time, maybe the page refresh call is placed before the ajax, so the reply to the page refresh, while not served from cache, actually has set-cookie values from the old settings (since they haven’t updated in the back end yet)?
Anyways, the change in cookie handling might well fix it, and for the short term turning off ‘Refresh page after updating preferences’ is a viable workaround. I’ve not dug into how that feature is handled, but perhaps just changing the page refresh call to happen from the ajax response would make everything work.
[edit]: in further testing, it’s not completely right with that setting off, I still have inconsistencies in trying to change settings, but it has certainly improved.
-
This reply was modified 6 years, 8 months ago by
jnorell. Reason: further testing