No announcement yet.

How to prevent marking posts read after long idle

  • Filter
  • Time
  • Show
Clear All
new posts

  • How to prevent marking posts read after long idle

    Sorry if this has been asked/posted before,

    How does one turn off the feature 'period of time a user must remain inactive before any unread posts are marked read' and thus always keeping each unread post marked unread unless the user clicks on 'mark forum as read' or actually reads them... but, without affecting the cookie setting that controls 'how long an user will remain on Who's Online after their last activity'?

    I wish they'd make this two separate options if possible.
    Last edited by Ogmuk; Fri 10 Oct '03, 3:43pm.

  • #2
    This is of interest to me as well.
    V1 Bad Bunny Emoticons > (For Dark BGs)
    Squarehead V1 Emoticons -
    Let Users select postbit style!


    • #3
      This is directly related to the cookie timeout. The only way to change this is to increase this timeout.
      Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
      Change CKEditor Colors to Match Style (for 4.1.4 and above)

      Steve Machol Photography

      Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


      • #4
        There is no way to turn off the "feature" of a user's session expiring. It's not a feature, it's the way vB works. A user's session lasts for the cookie timeout period and after that all threads are marked read (actually they aren't, what really happens is the system just looks at a user's lastvisit date vs. the time of the post and if the post is newer it shows an unread icon).


        • #5
          So if I understand correctly you can't you put the Cookie time-out on such a high number that they'd never time-out/mark read while keeping the Who's Online time-out on 900 seconds? Or do you mean not without changing the code?
          Last edited by Ogmuk; Sat 11 Oct '03, 12:50am.


          • #6
            The Who's Online timeout == the Cookie timeout, since that's how sessions are tracked.

            You could theoretically modify the code to do per-thread per-user read marking but that was tested in vB3 and was found to cause way too much overhead.


            widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.