Hi Rodney,
Here are technical specs on how it stores things: 1) For the normal hide function [Hide] it uses a session cookie so that if they return again in another session, it will show again. 2) For the permanent hide function, either through [KeepHidden], [KeepHiddenLink] or max views, it uses a normal cookie to store that. The key for the cookie is WelcomeViews + ModuleId + UserId
I did notice that the cookie expires in 1 year. I'm not sure why I picked that expiry, but I could definitely extend it or add it as an option.
The other thing that might be happening, is that the domain cookie max for the browser has been hit and it's dropping cookies, thus effectively resetting to a fresh one. The domain max is different for various browsers and I think some have increased it but it's generally been around 20.
I checked the home page for pokerdiy.com and I have 16 domain cookies now. Currently, each Aggregator also uses a cookie to track the selected tab so perhaps the combination of Agg and Welcome are pushing some people over 20 domain cookies. I have had it on my list for a while to combine all Aggregator cookie info into a single cookie but it was always pretty low priority. I'll have to take another look at that soon and see if it's possible to do the combining.
Please let me know if the cookie issue is the cause of your troubles.
|