It looks like the last vist time is getting messed up, and that is why you are seeing all these problems with status turning white
:roll:
I am working on it today, so please stay posted.
steve
Steve, while I appreciate all of the hard work you do, and I hope that this bugfix goes well, I still can't help but feel that basing the read/unread flags on the last vist time is very much the wrong way to go. (
Especially with a timeout flag involved. It should never time out. That's what logging out is for.)
Oh, I suppose on the one hand it's the only real way to help the folks who use multiple PCs until all of the cookie data can be stored server-side.
But on the other hand, it's clearly a bad hack to everyone else.
And I'd be willing to bet that a survey would show that the number of people accessing from multiple systems is less than the number of people accessing from a single system.
Personally, I'd rather scrap the whole thing and go back to cookies being the whole shebang until this can be done right on the server side. This goofy half-way thing is just no good IMHO, even without the bugs.
I'd put this under the category of "Conflicting User Requirements" and do a customer survey or something.