Last modified: 2011-07-28 22:19:32 UTC
The hidesnmessage cookie is added on every page load rather than just when closing a fundraising banner.
I don't think this is actually coming from CentralNotice. I wonder if someone was messing with the Hidesitebanner gadget.
Actually, it looks like that gadget just sets CSS, and doesn't mess with the cookies. Hmm.
Actually, I think this is caused by the German survey banner that is currently running on de.wikipedia.org and en.wikipedia.org.
The German survey banner is one of those "show to each user only once" banners. In other words, it always sets the hide cookie every time it loads. Until we have cookie groups, it is important that these banners not run concurrently (or within 2 weeks) of other campaigns (especially fundraising campaigns). Does anyone know what the status of the German survey is? Are they close to being done?
It is due to finish on the 26th.
Hmm, any idea who the contact person on it would be?
Talk to Nimish. He has been the one working with them. I thought they were setting a separate cookie instead. This makes more sense.
(In reply to comment #4) > The German survey banner is one of those "show to each user only once" banners. > In other words, it always sets the hide cookie every time it loads. Until we > have cookie groups, it is important that these banners not run concurrently (or > within 2 weeks) of other campaigns (especially fundraising campaigns). Does > anyone know what the status of the German survey is? Are they close to being > done? ...or that we name the cookie something different like we did for the Editors Survey, right? Wouldn't that work? This is obviously something that wouldn't help us now, but is something we need to remember to do in the future.
Oh yeah, I forgot we actually used a different cookie for the editor survey. That would definitely be a good idea for any future banners of this type. In the meantime, I've turned off the German survey on the English Wikipedia.
Ryan, you marked this highest priority so I'm giving it to you. Cheers!
Fix to prevent this in the future checked in as r93353.
