Dwarf Fortress Wiki:Centralized Discussion/Your edit was saved

When not logged in, each time I reload certain pages (eg DF2014:Quickstart guide) the "Your edit was saved" popup shows, even though I have not edited the page and did not navigate to the page via an edit. I have not so far seen this happen while logged in.

I don't know if it is related, but logging in also seems dodgy: logging in on one tab does not make me logged in in the browser as a whole (ie reloading a tab showing a logged-out page reloads it still logged-out), and I'm getting an awful lot of "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form." when trying to log in. I have not encountered this behaviour on other wikimedia sites. Hv (talk) 19:38, 31 October 2020 (UTC)

For the first part: there appears to be a flag (wgPostEdit) saved in the cached version of the page - when you're logged in, you don't see the cached version. Apparently it isn't supposed to be cacheable, so I'm not sure what to do about it. Perhaps a MediaWiki upgrade could help (which I've been meaning to do for a while). Update: purging the page's cache entry seems to have resolved it for this particular page - feel free to try this if you see it occur on other pages.

Thanks, I'll try to remember the Purge if I see this again. Usually I don't bother to log in until I need to edit something, then mostly stay logged in forever.

For the second part: Make sure that you are accessing the wiki consistently over HTTP or HTTPS. The wiki currently supports both (maybe we should make it always redirect to HTTPS now...) but logging in on one does not log you in on the other. Is is possible that you are sometimes navigating to the wiki via links or bookmarks that use HTTP? —Lethosor (talk) 00:24, 2 November 2020 (UTC)

Ah, that's very likely it: I see now that if I'm on an http page and attempt to log in, I get "There seems to be a problem with your login session" and it's still on http (and not logged-in) but _has_ logged me in under https (presumably due to the cookie domain). If that's intended and/or unavoidable, then having the "Log in" link force you to https might reduce the confusion - but I commonly log in in a separate tab and then reload the page I wanted to edit, so I'd still have been confused; fixing that would indeed require redirecting everything to https. Hv (talk) 02:18, 2 November 2020 (UTC)