Nuke Resources » Forums » Bug Reports » forum topics marked as read when not read

richman · Resource Newbie

I did a search on this and either I couldn't find anything or creteria was wrong.

I'm using 7.6 patched to 3.2
phpbb 2.0.19

Items are being marked as read when not.

Serveral items are indicated as not read. I read one of the topics and return to the forum index and all items are now read. I use the forum index hyper link.

Evaders99 · Resource Master

Make sure the cookie settings in your Forums Configuration are correct

richman · Resource Newbie

Cookie domain = no entry
Cookie name = phpbb2mysql
Cookie path = /
Cookie secure = disabled
Session length [ seconds ] = 3600

I think this is the default. Is this correct?

I did have a domain entry = clanboa.com/nuke
where www.clnboa.com/Nuke is my nuke directory.

Thanks

Evaders99 · Resource Master

Try just "clanboa.com"

richman · Resource Newbie

will do thx E

richman · Resource Newbie

All seems to be good now. Although I did need to correct; Cookie path = / to Cookie path = /Nuke. I have nuke installed in that directory.

Thanks again Evaders

iron_dubba · Resource Seeker

I'm having a similar issue on my forums. We're running php-nuke 7.6 3.2b patched, with bbtonuke 2.0.21 (I did all of these upgrades over the weekend). I thought this issue would be resolved with the upgrade of bbtonuke to the latest version (we were still using 2.0.08 up until this weekend).

We have several groups for different administrative tasks, and one general membership group for normal users. Some of the users in the general membership group have this problem, where they see all of the items as unread the first time they come to the forum, then after reading one post everything is marked read. However, if I put these users into one of the administrative groups, everything works properly. I take them out, and it's not working properly again.

Cookie settings appear to be correct. Not sure what the unique issue is. Any help would be appreciated.

Evaders99 · Resource Master

The flip side is to leave all the cookie settings blank. That has worked for some people.

BigGuyWhoKills · Resource Seeker

I have an issue that may be related. Sometimes, and only for some users, when the browser is closed (or even crashes), all threads are marked as read upon returning to the forum.

Any ideas on what could cause this?

Evaders99 · Resource Master

That is the default behavior of phpBB. It only saves the previous login time and tracks new posts between the previous login and the current. If the browser is closed and reopened, it is a new login.. say a couple of minutes, it will only show new posts within those minutes.

BigGuyWhoKills · Resource Seeker

Is there any way to stay logged in when I close a browser window? I realize that a browser crash may always exhibit this behavior, and I'm not looking for a solution to that issue. But this makes a forum difficult for me to keep on top of.

A little more detail. I check the forum from work, and rarely from home. When I get to work, I go through all my e-mail notifications. But at work I'm forced to use IE version 6, without tabs. So I open a lot of windows and close them often to keep from getting cluttered, and the e-mail link always open in a new window.

So a user-side solution would be to visit the forum before following any e-mail links, log in, and keep that window open the entire time I'm using the forum. Is that correct?

Evaders99 · Resource Master

User-side solution is correct.

I don't know if there's a mod for phpBB2 that does that. Possibly there is.
phpBB3 may have changed that functionality, but as of yet, it hasn't been converted to work with phpNuke

BigGuyWhoKills · Resource Seeker

One last question: Are there server side "session" settings that determine how long a user can stay logged in for?

There have been times when I've kept a window logged in at the Forum Index, and after closing a different window, or now that I know, opening a new window in the forum, I will get this situation. This may only be in an IE6 environment, I'm not certain.