Last modified: 2013-08-22 14:55:47 UTC
2012-11-06 00:54:07 mw72 enwiki: [2b5db4b8] /w/api.php?action=feedcontributions&feedformat=atom&user=95.86.124.51 Exception from line 36 of /usr/local/apache/common-local/php-1.21wmf3/includes/content/TextContent.php: TextContent expects a string in the constructor. 2012-11-06 00:54:07 mw72 enwiki: [310fec97] /w/api.php?action=feedcontributions&feedformat=atom&user=95.86.124.51 Exception from line 1727 of /usr/local/apache/common-local/php-1.21wmf3/includes/GlobalFunctions.php: Internal error in ApiFormatFeedWrapper::execute: Invalid feed class/item #0 /usr/local/apache/common-local/php-1.21wmf3/includes/api/ApiBase.php(1423): wfDebugDieBacktrace('Internal error ...') #1 /usr/local/apache/common-local/php-1.21wmf3/includes/api/ApiFormatBase.php(381): ApiBase::dieDebug('ApiFormatFeedWr...', 'Invalid feed cl...') #2 /usr/local/apache/common-local/php-1.21wmf3/includes/api/ApiMain.php(938): ApiFormatFeedWrapper->execute() #3 /usr/local/apache/common-local/php-1.21wmf3/includes/api/ApiMain.php(404): ApiMain->printResult(true) #4 /usr/local/apache/common-local/php-1.21wmf3/includes/api/ApiMain.php(349): ApiMain->executeActionWithErrorHandling() #5 /usr/local/apache/common-local/php-1.21wmf3/api.php(77): ApiMain->execute() #6 /usr/local/apache/common-local/live-1.5/api.php(3): require('/usr/local/apac...') #7 {main}
This seems to log two errors on the same request. I'm a bit confused about the format. The first one is an Exception from TextContent, but where is the stack traced for that? The second one is trigged by ApiFormat base - here we have a stack trace, but I don't understand why that codes gets executed if previously an exception occurred... Anyway, I can't see where the bad value for TextContent's constructor comes from. This is pretty much the problem described by bug 41735, but it seems to me this is a general problem with mediawiki's error reporting system.
They were appearing in pairs from the same apache at the same time, I guessed they must've been related.. That and the same request was coming in semi-frequently The same URL works for me locally, which is really helpful. Not.
Is this still a problem?
closing, no further reports. re-open as needed.
Closed older resolved bugs as verified.
