MediaWiki upgrade problems: Difference between revisions

From Cor ad Cor
Jump to navigation Jump to search
No edit summary
Line 26: Line 26:
I do not understand why ''$wgDisableOutputCompression'' was not sufficient.  I had my 1.35 installation running side-by-side with the 1.36 installation.  The two versions each had their own folder, but both connected to the same database through the configuration in ''LocalSettings.php''.  1.35 worked perfectly while 1.36 produced gobbledeygook
I do not understand why ''$wgDisableOutputCompression'' was not sufficient.  I had my 1.35 installation running side-by-side with the 1.36 installation.  The two versions each had their own folder, but both connected to the same database through the configuration in ''LocalSettings.php''.  1.35 worked perfectly while 1.36 produced gobbledeygook


== A better fix ==
I have the feeling that I need to learn how to use MemCached with MediaWiki.  The documentation for ''$wgDisableOutputCompression'' says that the time spent compressing is trivial and that the savings in bandwidth are worth the effort.


[[Category:Wiki management]]
[[Category:Wiki management]]

Revision as of 10:56, 5 June 2021

The Problem

My wiki is hosted on GoDaddy. I used Installatron to create the original installation.

When I upgraded to version 1.35 and 1.36 of MediaWiki, all I saw on the welcome page was undecipherable strings of ASCII characters and symbols. The page was completely illegible and unintelligible. The image in the thumbnail is from a MediaWiki discussion on Discord.

Solution for MediaWiki 1.35 upgrade

Disable output compression in LocalSettings.php:

## Uncomment this to disable output compression
$wgDisableOutputCompression = true;

Solution for MediaWiki 1.36 upgrade

If you already have an .htaccess file in the root folder of your MediaWiki installation, add this line to it:

SetEnv no-gzip 1

Or create an .htaccess file with that line.

I do not understand why $wgDisableOutputCompression was not sufficient. I had my 1.35 installation running side-by-side with the 1.36 installation. The two versions each had their own folder, but both connected to the same database through the configuration in LocalSettings.php. 1.35 worked perfectly while 1.36 produced gobbledeygook