Last modified: 2011-04-04 21:32:40 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T18227, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16227 - Page saving error MW1.13
Page saving error MW1.13
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.13.x
All other
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-03 13:08 UTC by Paul Marvin
Modified: 2011-04-04 21:32 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Paul Marvin 2008-11-03 13:08:55 UTC
* MediaWiki version: 1.13.2
* PHP version: 5.2.4
* MySQL version: 5.0.45
* URL: Intranet only
* Server OS: AIX 5.2

We have recently upgraded to MW1.13.2. Since upgrading from v1.12 we have been having frequent problems with saving pages. I have been unable to identify any patten as to when the failure to save can occur. A page preview will work but on "action=submit" you may get a "The page cannot be displayed" error in IE, a blank page in firefox and safari. It has gotten so bad on one site I reverted it back to v1.12. 

I have found some workarounds but they are not 100% effective. I hope these give a clue as to where the error is occurring. The first thing to try when you get this error is to use the back button and check the "This is a minor edit" before clicking the save button. If that does not work then have the sysop change the protection state from "(default)" to "Block unregistered users" or visa versa depending on current state.

Any help/direction you can give will be greatly appriciated by our MW community.

Thanks,
Paul
Comment 1 Paul Marvin 2008-11-07 19:27:21 UTC
Has anyone looked at this? It is really a big problem. I am being asked to move sites back to v1.12 as the work around. I need some ideas on how to debug this issue. I did try enabling PHP error reporting to e_ALL but that did not show anything. MW 1.13 is clearly doing something that 1.12 did not do on "action=submit". 

We have also stated to notice that emails for watched pages are not being sent out even after all pages are marked as read. Is it possible that these two are related?

Help,
Paul
Comment 2 Aaron Schulz 2008-12-06 01:32:04 UTC
Add to localsettings.php:

error_reporting( E_ALL | E_NOTICE );

As well as either:
ini_set('display_errors', true);

Or, to be more secure:
ini_set('log_errors', true);
ini_set('error_log,'SOME DIRECTORY YOU CHOSE');

These can also be set in PHP.ini.

What results do you get?
Comment 3 Paul Marvin 2008-12-08 14:06:37 UTC
I have added the below code to LocalSetting.php. When the problem occurs I am not getting any output to the screen or error directory.

For veification here is what I added near the bottom of the LocalSettings.php:

error_reporting( E_ALL | E_NOTICE );

ini_set('display_errors', true);
ini_set('log_errors', true);
ini_set('error_log','/opt/app/cbwiki/tmp');


(In reply to comment #2)
> Add to localsettings.php:
> error_reporting( E_ALL | E_NOTICE );
> As well as either:
> ini_set('display_errors', true);
> Or, to be more secure:
> ini_set('log_errors', true);
> ini_set('error_log,'SOME DIRECTORY YOU CHOSE');
> These can also be set in PHP.ini.
> What results do you get?

Comment 4 Brion Vibber 2008-12-20 02:21:23 UTC
The "The page cannot be displayed" error in IE indicates to me that this is probably from PHP crashing -- this is usually due to one of the following:

* Infinite recursion in PHP code

* Some nasty bug in PHP itself or a library PHP uses (such as the PECL regular expressions)

* Some weird bug in a PHP extension, especially one that was not properly updated for a PHP upgrade? (Especially if something core like an opcode cache)

Make sure the PHP installation is good, check if it's changed recently. Check the web server's error logs for any crash information. Try installing the XDebug extension for PHP, which can help point out recursion problems -- if that doesn't turn it up, you may have to start debugging the Apache/PHP process itself. :(
Comment 5 Siebrand Mazeland 2009-02-15 00:46:15 UTC
Closed as invalid. No useful information to go on provided, unfortunately, and all hints that could be given, haven been given.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links