Upgrade MediaWiki 1.18.0
I have been upgrading MediaWiki in so many times over 3 years without a problem. Today, I just did upgrade version 1.18.0. There are two problems:
1.) [Resolved] During command:
[user@web10 maintenance]$ php update.php
PHP error log is working Do not run update.php on this wiki. If you're seeing this you should probably ask for some help in performing your schema updates.
If you know what you are doing, you can continue with --force
Found the problem from $wgMiserMode
2.) I get blank pages without showing any error print on the page. I have looked at error log it says:
MYIPADDRESS - [09/Jan/2012:08:16:27 -0600] "GET /index.php/Main_Page HTTP/1.1" 500 0 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1"
[Mon Jan 09 07:55:26 2012] [error] [client MYIPADDRESS] File does not exist: /home2/user/webapps/mw/index.php/Main_Page
How can I resolve this problem?
PHP 5.2.11 (apache2handler)
Second issue you could try enabling php error logging (or if you have php error logging set up, look in the php error log [usually it would be seperate from your apache error log)? See manual:How to debug. Generally blank page means a php fatal error when error reporting is turned off.
I have done that what you suggested enable php error logging in LocalSettings.php before all the time like this:
ini_set( 'display_errors', 1 );
error_reporting( E_ALL );
error_log("PHP error log is working");
It doesn’t showing any error print on the page only blank pages after upgrade MediaWiki 1.18.0. That is why I asking for help. What can I do?
That's interesting. Can you access the api fine? If you put something like
die("test"); in LocalSettings.php, does "test" get printed out (as in, does mediawiki even reach to LocalSettings.php)
I have the same issue. I insert...
error_reporting( E_ALL ); ini_set( 'display_errors', 1 );
into my LocalSettings.php and i still get a white blank screen when i try to run update.php.
Checking my DB (mysql) and update hasnt created new extension tables. My user privileges are full sysadmin on the db.
Is this a 1.19 issue?