posts not marked as read leaving causes all marked as read

Nuke Cadet Joined: Feb 03, 2006 Posts: 3

greetings! hopefully someone can give some direction.

recently my webhost upgraded to php 5.1.2 which prompted me to upgrade phpbb to 2.0.19, however, posts are no longer being marked as read. furthermore, if you leave the site and come back all posts will be marked as read. ive looked on multiple sites and forums and have not found a solution that works here.

the site is 7.8 with 3.1patched, phpbbtonuke2.0.19.

my cookie settings are:
Cookie domain: *blank*
Cookie name: *blank*
Cookie path: /
Cookie secure: Disabled
Session length: 3600

the only thing i can think of is something in session.php is no longer working properly but i know nothing of how to fix it. Sad

would anyone be able to provide some help here? it would be very much appreciated.

edit: i went from phpbb2.0.17 > 2.0.18NP > 2.0.19NP during tne upgrade process.

Site Admin Joined: Aug 17, 2003 Posts: 12388

Try setting your Forums domain and name

Nuke Cadet Joined: Feb 03, 2006 Posts: 3

did. i tried with and without the subdomain and with a name.

logged out, totally wiped cookies just because i could, logged in, same thing.

Site Admin Joined: Aug 17, 2003 Posts: 12388

Odd, maybe something in BBToNuke 2.0.19. I'll try and duplicate this

Nuke Cadet Joined: Feb 03, 2006 Posts: 3

that would be keen.

any luck so far?

i have reinstalled everything a number of times as well as redownloaded the software packages. yet it remains.

so either there is one step someplace i am missing or there is a bug someplace.

Nuke Soldier Joined: Jun 07, 2004 Posts: 22

I am having the same problem and have discovered that when my sid (session id) is set as a cookie everything works fine. If the cookie expires it stops working as every time the forum index page is reloaded the last visit is updated to the current date/time without the sid cookie.

I have tried all the fixes I could find on the web and tried all cookie setting combos.

My sid almost never shows in the url.