Last modified: 2011-04-04 21:28:16 UTC
I am member of the development team of PHP, maintaining the NSAPI webserver module. During tests of my module and the 1.13.2 version of mediawiki, I have seen blank pages whenever a page was not in the (parser?) cache. My installation has enabled the cache that puts these html files into this temp folder (I do not know whats the difference between parser cache an cache is). After enabling printout of errors (error_reporting(E_ALL) in LocalSettings.php), whenever I call a page not in the cache, I get the following error: Fatal error: Call to a member function getCacheTime() on a non-object in /pangaea/htdocs/wiki.pangaea.de/includes/Article.php on line 3387 Other pages (when previously called) are shown normal, without errors. Special pages and so on show correct, too. It seems to be a difference between parsing of the mentioned line in PHP 5.2 (where the wiki normally runs, it was only a test of the preview, using the wiki installation normally running in 5.2). I do not know if this i san error in PHP, but I think the problem is a more strict checking of the if-clause there. To reproduce, install a PHP-5.3 snapshot version (I used the one from November 29, 2008) or the alph3 version hopefully coming on Monday, Dec. 1, 2008. By the way, Mediawiki is running perfect with Sun Java System Webserver 7.0U3 using the NSAPI PHP module (see http://wiki.pangaea.de/wiki/Special:Version) and some extra (self-made) URL rewriting instructions in the webserver (as they are different from Apache).
Maybe related to bug 15854, try to update to the latest development version (http://www.mediawiki.org/wiki/Download_from_SVN) and see if this bug is still present in that version.
This looks like the problem. I try later! Sorry for not finding this bug report, but i used the search function with parts of the error message, but bugzilla does not seem to full text index the comments. The title of bug 15854 is not very descriptive for my problem :)
I changed the one line in Parser.php according to bug 15854, this fixes this bug. So it is a dupe. *** This bug has been marked as a duplicate of bug 15854 ***
*** Bug 17407 has been marked as a duplicate of this bug. ***