Topic on Project:Support desk

Hi all,

I had a bit of a mare during an attempt to update my implementation of Mediawiki 1.24.1 to the current version, and I ended up having to back out and re-implement 1.24.1. Since then, there has been a recurring issue whereby changes to pages don't show up immediately after saving an edit and there will be edit locks as though multiple people are editing the same page, even though I know that is not the case.

I'm guessing this is a database issue, but I do not know how to remedy it - if there is a script to run to reboot the database? or if that is even the solution?

What you describe is handled by the Manual:Job queue. There's nothing wrong in the database, nor something to "reboot" it, unless you want to start from scratch...

If during your failed attempt to upgrade, you ran the update script on the new version, and then you rolled back to the old version without rollink back also the database (using a recent backup), some things may be broken, since downgrading is not supported.

I didn't run any scripts other than 'Runjobs.php' prior to the update, what i did was mostly just changing my php default document and moving files around. I went to update via the browser when I received an error regarding a missing dependency, so I just undid the steps and put back in the older files which I had backed up.

It all seems to work as expected other than this issue - I'll check out that manual page, thanks.

Further to this it would seem that Mediawiki isn't handling log in that well, after logging in some users report seeing another username at the top of their screen. I had thought that since I did not run anything when I navigated to the browser update facility, that nothing was changed on the database.

Any ideas how to fix this issue? Restoring the database perhaps?

Seeing another user at the top of the screen may indicate you're using some caching mechanism on the webserver, like a proxy-cache (varnish, squid), which is not properly configured. MediaWiki doesn't cache pages for logged-in users, although if there's a bug you won't get any support here if you run an old and insecure version.

Thanks a lot! My issue turned out to be with IIS's default caching settings, instead of 'do not cache' I needed to put 'prevent caching'

I'll look into it thanks, I've a view to upgrade this to the newest version but I had trouble last time I attempted it.