Problem Upgrading from 1.16.1 to 1.18.3

Fragment of a discussion from Project:Support desk
Jump to: navigation, search

Anyone have any suggestions on how to troubleshoot this? Is there any error log I can look at or checks I could place in the index.php file to help in determining why it quits out?

Thanks, Wes

144.188.24.2912:07, 3 May 2012

An update from 1.16 to 1.18 should not be too difficult. Replacing all files and then running the DB updater sounds good. Now you might have incompatible extensions or skins installed, which still need adjustements.

When you get a white screen without any output a good start to debug this is to turn on error logging in PHP. Then have a look at the PHP error log. It will show you the error, which is happening when you try to view your wiki. Then this error must be fixed.

88.130.91.21515:46, 3 May 2012

Thanks. That helped.

The error log shows a redeclare error for wfProfileIn(). It is being declared in both:

\includes\profiler\Profiler.php
and
\includes\ProfilerStub.php

I'm guessing the ProfilerStub.php file is a leftover from the old install since it isn't inlcuded in the 1.18.3 files?

144.188.24.2915:35, 7 May 2012

If ProfilerStub.php is not included in 1.18.3, you can remove it.

But I think the root of your problem might be somewhere else: See if you have a file called StartProfiler.php (or somehow like that) in the root directory of your wiki installation. If you have, this file is outdated and might likely cause the error.

Remove it or check the new example file, which comes with MW 1.18.3 to see how you must adjust this profiling file so that it works again.

88.130.124.21416:31, 7 May 2012

Ok, I've proven that I'm an idiot yet again! The upgrade instructions clearly state:

Files remaining that may cause

If you are not using profiling, but have a StartProfiler.php file in the MediaWiki root folder, 
you may receive errors referring to /includes/Profiler.php. Deleting, or renaming, the 
StartProfiler.php file will resolve this error. 

Removing that file solved the issue. No idea why I didn't see that in the first place!

Thanks for the help,

Wes

144.188.24.2916:52, 7 May 2012