Page MenuHomePhabricator

Section Edits - Internal 500 Server Error
Closed, DeclinedPublic


Author: aps170

When trying to edit a page, specifically a section, the user can edit the page,
but when they try to save, they receive a "A Page Cannot be Displayed -- HTTP
500 Internal Server Error". However, when going back to the page, the new edit
is shown. So the data is being saved, however, the page is not redirecting
itself back to the edited page.

When using the Edit button at the top of the page, the error does not appear.

This error only happens when using Internet Explorer. We have tried using
Mozilla Firefox and Netscape, to which the problem does not occur. However,
most of our users use IE version 6.0

We have also used the following configuration parameter in the
LocalSettings.php: $wgActionPaths . Going through the Mediawiki Forums Website
(, we were able to find a similar situation where the user
used the $wgActionPaths parameter and it corrected their problem. It did not
work for our instance, unfortunately.

Any help or guidance will greatly be appreciated!!!!!!

Version: 1.12.x
Severity: major
OS: Windows XP
Platform: PC
Whiteboard: aklapper-moreinfo



Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 9:38 PM
bzimport set Reference to bz9681.
bzimport added a subscriber: Unknown Object (MLST).

Please look at your web server error log, there should be details
about the cause of this error 500. Without it, there is nothing
we can do to track the issue.

Please reopen the bug with the requested information.

pribulla wrote:

I have the same problem with version 1.12.0 and probably version 1.13.0 contains it too.

I tried to locate this bug and found something....
IMO problem is in class Preprocessor_Dom in method:

function splitHeading() {

		if ( !$this->nodeName == 'h' ) {
			throw new MWException( 'Invalid h node passed to ' . __METHOD__ );
		return array(
			'i' => $this->node->getAttribute( 'i' ),
			'level' => $this->node->getAttribute( 'level' ),
			'contents' => $this->getChildren()


In the first condition, '$this->nodeName' should be replaced with '$this->getName()'.

Bryan.TongMinh wrote:

Even if that would be a problem, this could never raise a php fatal error and thus a server error. $this->nodeName will be either null or something else.

Amita / Eugen: Has this problem happened again recently, or can it be assumed that this bug report is obsolete nowadays?

TTO added a comment.Jul 20 2013, 11:59 AM

No response, closing.