marvinp wrote:

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

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?

marvinp wrote:

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?

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. :(

Closed as invalid. No useful information to go on provided, unfortunately, and all hints that could be given, haven been given.