Webpage Expired using back in the search

Regular Joined: Sep 25, 2006 Posts: 57

Why am i getting this error? whenever you search and then look at a topic in the results list you backup to the initial search finding and the webpage has expired. It will expire even when you back out immediatly. Where do I look?

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

I just tested this on http://www.ravennuke.com and did not have this result. It may be something that was resolved in 2.20?

Posted: Mon Feb 04, 2008 10:46 pm

I have 2 sites. both used to be hosted on the same host. I moved this one to a new host. Maybe it has something to do with the way the new host handles cookies etc. Only change i made when i moved was i ran the bbtonuke upgrades(2) that were included in the latest 2.10.01
I do notice when i view posts since last visit that backing out of a topic in that list now shows that post marked as read, when before it would not have.

registered · Posted: Tue Feb 05, 2008 6:01 am

I cannot think of anything that we have changed in 2.20.00 (what ravennuke.com is running on) to fix anything like this. Does it still do this after you clear your cookies and browser cache and then come back in with a fresh browser instance?

Posted: Tue Feb 05, 2008 4:07 pm

montego wrote:

I cannot think of anything that we have changed in 2.20.00 (what ravennuke.com is running on) to fix anything like this. Does it still do this after you clear your cookies and browser cache and then come back in with a fresh browser instance?

I think it has to do with the way sessions are handled, but since I don't know jack it could be anything. I have my other site which works correctly, like I said it didn't happen until I moved to a new host and upgraded the phpbb upgrades I forgot to run when I upgraded to 2.10.01

Posted: Tue Feb 05, 2008 9:33 pm

You shouldn't need to know how to set up sessions. Ask your host to check whether they have PHP sessions properly configured.

However, the module you are talking about doesn't in of itself do any form of PHP session handling (it does its own using the query string), however, in NukeSentinel, which is basically invoked everywhere, does. So, not sure these are related, but lets rule out a host problem since you just moved recently.