I use the active topics page as my ADT bookmark. I had to change the bookmark yesterday or the day before, and the new version doesn't work when I come back to the site from elsewhere -- it shows no active topics.
If I stay at ADT for a few minutes, when I hit active topics it shows the new ones. Anyone else having this problem?
Now that he mentions it, when it says the last visit was the current time, it's saying there are no active topics, but it's working for me right now (and says my last visit was 24 minutes ago). It's been doing this off and on all day, or at least since lunchtime when I started goofing off.
It's not remembering the last visit properly. It will capture the start time of your current visit but not the last visit from the cookie. It's got to be something simple.
Look for any cookies from forum.adultdvdtalk.com if you still have them and remove them. Those things are from when we tried out that other forum software a long time ago. They will cause a problem.
This thread reminds me - I've been meaning to ask you something.
Is there any way that we can 'reset' our last visit date/time to something of our choosing?
There have been a few occasions where it would have been nice to be able to do it. For example - Had to leave the computer and come back later, without having been over new messages.
Just wondering if we could edit a cookie or something.
Can the cookies be set to remember a based on active topics based on username rather than IP? I get different topics depending on where I'm goofing off from.
I should know this but I'm lazy and you might know off the top of your head.
You could do something with long ttl session vars that would accomplish what I just said, though, right? I'm thinking through about six beers here so bear with me.
I'd rather hit the database than keep sessions open longer. IIS is a bit stupid in how it handles memory allocation for sessions. Google's crawler hits our site many thousands of times per day. Each request ends up launching a new session in IIS which eats up memory. I suppose I could/should detect them and abandon the sessions for those requests but currently I don't. We currently use memory-based sessions but at some point will have to switch to a different method to support a web farm/web garden approach.
It sounds like you've had to deal with larger scalability issues than I ever would've wanted to put up with on IIS. Clustering, web server farms, high availability SQL Server, caching, the whole nine yards..I'm sorry. What a pain in the ass. Would you do it all over again?
If php5 (or even 4) was available (and if MySQL supported stored procedures and triggers) when I first started this stuff we might have gone a different route. ASP isn't great but MS SQL Server is awesome.
It's really not that bad though. We're an outdated scripting language on relatively slow servers. It still chugs along fine with 350 - 400 active sessions for the moment. There's only two IIS worker processes servicing all of ADT. One for the forum and one for the main site. If things start to get too slow I'll convert some of our more popular pages to ISAPI code, not that .NET shit.
It works then it doesn't. Getting a: Error Processing your request HTTP Error 500 - Server Error At times today. Then I closed the browser (Safari) and it worked. Then it didn't. And closed and not working again. This the link in the upper right corner.