Last modified: 2011-11-29 20:31:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4546 - Error when loading page, undefined function peplacealllinks
Error when loading page, undefined function peplacealllinks
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Lowest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-01-09 22:05 UTC by That Guy, From That Show!
Modified: 2011-11-29 20:31 UTC (History)
1 user (show)

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


Description That Guy, From That Show! 2006-01-09 22:05:08 UTC
This is the what I and couple of other people have seen when trying to view pages.  It can show up on the first view of a page but the error
goes away after refreshing it from a web browser from what I have observed.

'''Fatal error: Call to undefined function: peplaceinternallinks() in
/usr/local/apache/common-local/php-1.5/includes/Parser.php on line 812'''

It looks to me like a typo (peplace instead of replace) unless that function has
been renamed.

I hope this helps.
Comment 1 Brion Vibber 2006-01-11 22:17:54 UTC

Resolving this LATER; reopen if similar issues crop up again. We should be better equipped now 
to localize the error to see which server has the corrupt pages.
Comment 2 Diederik van Liere 2011-11-29 20:30:01 UTC
Link to email thread results in 404 error, I guess the problem has been resolved. Marking it as FIXED.
Comment 3 Brion Vibber 2011-11-29 20:31:03 UTC
This was probably from the old APC cache corruption issues, which I don't think are as common anymore.

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