Jump to content
  • 0

mw-config blank while trying to upgrade



I'm trying to upgrade from 1.29.2 to 1.31.1 and am having a problem I've never seen before.

I uploaded my files over FTP, then tried to browse to /mw-config/

Blank, nothing. Nothing even in "view source".

I tried renaming .htaccess, that didn't help. I tried enabling error reporting in LocalSettings, still nothing.

What I did find was someone else experiencing the same symptoms 4y ago, but no resolution:


Any thoughts? I did make a backup, so I'm not dead and can refer to that, but I'd like to get updated.


PHP 7.2.11

MariaDB and Litespeed (not entirely sure how to check those versions... shared hosting, not seeing it in cpanel)

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

Ok putting it into index.php accomplished something. Here's what I see:

Fatal error: Uncaught Error: Class 'Composer\Autoload\ClassLoader' not found in /home/xxxx/public_html/wiki/vendor/composer/autoload_real.php:23 Stack trace: #0 /home/xxxx/public_html/wiki/vendor/autoload.php(7): ComposerAutoloaderInit_mediawiki_vendor::getLoader() #1 /home/xxxx/public_html/wiki/includes/Setup.php(60): require_once('/home/xxxx/...') #2 /home/xxxx/public_html/wiki/includes/WebStart.php(88): require_once('/home/xxxx/...') #3 /home/xxxx/public_html/wiki/mw-config/index.php(39): require('/home/xxxx/...') #4 {main} thrown in /home/xxxx/public_html/wiki/vendor/composer/autoload_real.php on line 23

Link to comment
Share on other sites

  • 0

Did you get the new MediaWiki files via Git or by downloading the tarball?

If you got it via Git, you will need to install and update all of the dependencies yourself. See here for more information.

If you used the tarball, it appears that some of the files didn't get extracted properly or were possibly missed. Re-download the tarball and re-extract it to a new, empty folder. Then copy over your LocalSettings, updated versions of extensions, and images to the new folder. It's always recommended when upgrading with a tarball release to extract to a new folder as there may be issues caused by leaving around files from an old release that were removed in a future release.

Unless you are already familiar with using Git and feel comfortable with your systems administration skills, I recommend using the tarballs.

Edited by Skizzerz
explain best practice for extracting tarballs (see edit history)
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.