doing a bit of crowd sourced debugging.
@soundz
and any other nerd-meister that likes this internet stuff.
Over the weekend, it was confirmed with the help of @stb222 that there are different versions of forum
reality for different users. While I saw a thread with posts in the future, and was blocked from posting,
Kev did not, and was able to post.
I used a laptop to log into the forum using my test account, and it also saw the posts in the future.
As did my phone (using wifi) and my regular account.
I did not switch to cellular data (different IP address) to see if that made a difference.
Running chrome and logged in through the same IP address might have something to do with it (shared cookies? cache?)
So i'm wondering if there are issues with the re-write rules? with collisions concerning mtbnj.com vs www.mtbnj.com
What about cache at the server level - session based, ip based (i don't know the tricks apache uses)
I'm going to start shutting things off - like automagic redirection to https.
shouldn't shut down anything functional.
I'll also put together a couple of database queries that can be run from the browser. Links to come.
Might help identify what the database thinks, vs the presentation.
@soundz
and any other nerd-meister that likes this internet stuff.
Over the weekend, it was confirmed with the help of @stb222 that there are different versions of forum
reality for different users. While I saw a thread with posts in the future, and was blocked from posting,
Kev did not, and was able to post.
I used a laptop to log into the forum using my test account, and it also saw the posts in the future.
As did my phone (using wifi) and my regular account.
I did not switch to cellular data (different IP address) to see if that made a difference.
Running chrome and logged in through the same IP address might have something to do with it (shared cookies? cache?)
So i'm wondering if there are issues with the re-write rules? with collisions concerning mtbnj.com vs www.mtbnj.com
What about cache at the server level - session based, ip based (i don't know the tricks apache uses)
I'm going to start shutting things off - like automagic redirection to https.
shouldn't shut down anything functional.
I'll also put together a couple of database queries that can be run from the browser. Links to come.
Might help identify what the database thinks, vs the presentation.