Page 1 of 1

Forum page age too high? "someone else has edited"

Posted: October 25th, 2017, 1:02 am
by OneCD
Hello.

Firefox ESR 52.4.0 on Debian 9.1
Safari mobile on iOS 10.3.3

Ever since the forum transformed into the new-hotness, I've been having trouble with pages not refreshing (as in: they show me previous page versions when I know the page now has new data).

This is most noticeable when I write a post, submit it, immediately go back and edit it (yes, the programmer within demands it), then try to submit or preview the edited post. I get a (false) warning that "someone else has edited... blah, blah", and the edit window shows my old data.

I have to perform a full page refresh (CTRL+F5), then submit. My iPhone shows the same issue. Not just when submitting posts but viewing too.

I wrote a post eariler today that became quite a battle as the forum server fought me all the way. I'd make a new post, submit post, post has an error, edit, fix, submit post again, realise it posted the previous version data, edit again, fix again, add something new, submit post, old data again, (ugh!), edit, manual full-page refresh edit page, post, data is now correct but I've made a new mistake, edit again, manual full-page refresh edit page, make my change, submit, done.

Kinda hazy on this, but isn't there an age value that the web-server can put on each page so the client browser knows when the data is old and should be re-downloaded instead of using its local cache? Maybe it's set too high?

Thank you. ;D

Re: Forum page age too high?

Posted: October 25th, 2017, 1:27 am
by safihre
I noticed the same yeah, it needs about 30 seconds of peace.
This is probably due to the Cloudflare in between.
Let me ask our web guy!

Re: Forum page age too high?

Posted: October 25th, 2017, 1:45 am
by sander
I can confirm. Quite annoying.

Re: Forum page age too high? "someone else has edited"

Posted: October 25th, 2017, 2:42 am
by OneCD
Thanks guys. 8)

Re: Forum page age too high? "someone else has edited"

Posted: January 21st, 2018, 3:47 am
by OneCD
A quick follow-up: I think this has now been fixed as I no longer see the same behaviour from the site. ;D