Official Everybody Edits Forums

Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?

You are not logged in.

#1 2016-06-28 16:08:10

Anatoly
Guest

Forums laggy with (read/unread) threads.

Sometimes all unread posts get after one minute automatically read.

Threads I have read or already answered aren't marked unread.

//forums.everybodyedits.com/img/smilies/sad Why always me? //forums.everybodyedits.com/img/smilies/sad

#2 2016-06-28 16:41:35

drunkbnu
Formerly HG
Joined: 2017-08-16
Posts: 2,306

Re: Forums laggy with (read/unread) threads.

AnatolyEE wrote:

Sometimes all unread posts get after one minute automatically read.

Threads I have read or already answered aren't marked unread.

//forums.everybodyedits.com/img/smilies/sad Why always me? //forums.everybodyedits.com/img/smilies/sad

That's the default FluxBB session behavior.

hummerz5 wrote:

Well, I was looking at the forum codes, and it looks like someone has a bone to pick with you. (really, look at the code)

<!-- This is where I would put my fun. IF ONLY ANATOLYEE WEREN'T SUCH A KILLJOY. >:( -->

Besides the possibility that someone purposely coded in glitches for you, maybe you've got some cookie issues? IIRC they're based on sessions, so...

That's a message that appears when you disable the April Fools options. That has nothing to do with Anatoly's issue.

Offline

#3 2016-06-28 16:47:12

drunkbnu
Formerly HG
Joined: 2017-08-16
Posts: 2,306

Re: Forums laggy with (read/unread) threads.

hummerz5 wrote:
HG wrote:

That's the default FluxBB session behavior.

I feel like there's emphasis on "all unread posts are marked read"... are you saying it's default session behavior that's being incorrectly fired too soon?
Or that knowing which unread posts weren't read is unnecessary?

Usually the FluxBB default session lasts for 30 minutes before it expires.

Offline

Bimps1467142627610288

Board footer

Powered by FluxBB

[ Started around 1738456777.0149 - Generated in 0.076 seconds, 11 queries executed - Memory usage: 1.38 MiB (Peak: 1.48 MiB) ]