Jump to content

Recommended Posts

Posted

It seems that right now unread threads are automatically marked read after a relatively short period of inactivity. This is a common problem with the vBulletin software but it is adjustable. Would it be possible to change the setting on the forum server from #1 to #3 as described here:

 

http://www.vbulletin.org/forum/showthread.php?t=175423

 

Failing that, would it be possible to increase the timeout to something like 24hrs?

 

Thanks

Posted

Yes I have noticed it has changed recently and is a little annoying.

PC:

 

6600K @ 4.5 GHz, 12GB RAM, GTX 970, 32" 2K monitor.

 

Posted

It's annoying as hell, i dunno why we have it enabled. I'll forward it to the higher ups.

Good, fast, cheap. Choose any two.

Come let's eat grandpa!

Use punctuation, save lives!

Posted
Thanks working better now.

 

I guess that is relative. Every thread was marked unread this morning. That does not equal 'better' to me.

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Posted

What do you mean? Did some other setting get changed around for you?

Good, fast, cheap. Choose any two.

Come let's eat grandpa!

Use punctuation, save lives!

Posted
What do you mean? Did some other setting get changed around for you?

Me? No. Just trying to be sarcastic as usual ... :o)

 

What I was refering to is the timestamp of the cookies in our browsers that determine the age of the threads that are assumed being already read or being new. (or maybe it is even stored server side)

 

For those confused about what threads are new or old after const has reset this cookie update timer, it would probably been helpfull if they had access to that cookie/timestamp for reference ... instead of just starting over by clicking "Mark Forum Read" on top of the page ...

Posted

Right now the threads are NOT marked as read to me (expect the ones that were actually read) unless I explicitly use function "Mark forums read".

AMD R7 5800X3D | Aorus B550 Pro | 32GB DDR4-3600 | RTX 4080 | VKB MGC Pro Gunfighter Mk III + STECS + VKB T-Rudder Mk4 | Pimax Crystal

FC3 | A-10C II | Ка-50 | P-51 | UH-1 | Ми-8 | F-86F | МиГ-21 | FW-190 | МиГ-15 | Л-39 | Bf 109 | M-2000C | F-5 | Spitfire | AJS-37 | AV-8B | F/A-18C | Як-52 | F-14 | F-16 | Ми-24 | AH-64 | F-15E | F-4 | CH-47

NTTR | Normandy | Gulf | Syria | Supercarrier | Afghanistan | Kola

Posted

What I was refering to is the timestamp of the cookies in our browsers that determine the age of the threads that are assumed being already read or being new. (or maybe it is even stored server side)

 

It's no longer stored in the cookie.

Good, fast, cheap. Choose any two.

Come let's eat grandpa!

Use punctuation, save lives!

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...