Last modified: 2014-11-12 01:45:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T72709, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70709 - PHP fatal error: Call to a member function getTitle() on a non-object in /includes/Feed.php:309
PHP fatal error: Call to a member function getTitle() on a non-object in /inc...
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.23.3
Other All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
https://www.mediawiki.org/w/index.php...
aklapper-moreinfo
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-11 11:52 UTC by taraathan@gmail.com
Modified: 2014-11-12 01:45 UTC (History)
2 users (show)

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


Attachments

Description taraathan@gmail.com 2014-09-11 11:52:57 UTC
I just installed 1.23.3 using Softaculous. I am seeing an error in my log:

PHP Fatal error:  Call to a member function getTitle() on a non-object in /home/rulemlso/public_html/wiki.ruleml.org/includes/Feed.php on line 309

This error message seems odd because line 309 in Feed.php reads

return gmdate( 'D, d M Y H:i:s \G\M\T', wfTimestamp( TS_UNIX, $ts ) );

There is no obvious affect on the wiki itself - I'm not really sure where to look for it.

I have the following extensions installed:
Multi-Category Search (1.66)
Replace Text (1.0)
Cite (-)
ParserFunctions(1.6.0)
Privacy(1.2.3)
SyntaxHighlight(1.0.8.11-wmfm1)
Lockdown (d08bc8)
WikiEditor (0.4.0)

PHP is 5.3.29 (litespeed)
MYSQL is  	5.5.36-cll-lve
Comment 1 Andre Klapper 2014-09-11 19:27:30 UTC
Thanks for taking the time to report this!

http://www.mediawiki.org/wiki/Manual:How_to_debug might help to get a bit more info, and I'd also recommend to ask on https://www.mediawiki.org/wiki/Project:Support_desk
Comment 2 Andre Klapper 2014-09-22 10:55:58 UTC
Tara: Did you ask on the support desk? Could you link to that request?
Comment 5 Andre Klapper 2014-09-23 09:46:41 UTC
"The errors seem to have disappeared on their own, so this seems like a likely culprit."
Comment 6 taraathan@gmail.com 2014-09-23 11:23:16 UTC
I was mistaken about the errors disappearing - I was just looking for them in the wrong place. The errors continue to appear, at a rate of between 2-8 times per day, in the error_log file in my wiki directory.
Comment 7 Sam Reed (reedy) 2014-09-23 11:27:30 UTC
A stack trace would be useful for debugging this further.

Can you add "$wgShowExceptionDetails = true;" (without the ") to your LocalSettings.php?
Comment 8 Florian 2014-09-23 12:19:41 UTC
(In reply to Tara Athan from comment #6)
> The errors continue to appear

-> Ropen
Comment 9 taraathan@gmail.com 2014-09-23 12:23:00 UTC
I have added $wgShowExceptionDetails = true; to LocalSettings.php
Where do I look for the stack trace?
Comment 10 taraathan@gmail.com 2014-09-25 15:42:27 UTC
Based on my webhost's suggestion, I added

$wgCacheEpoch = '20140924154644';

to my LocalSettings.php

This has had no effect on the errors.
Comment 11 Andre Klapper 2014-09-28 23:21:11 UTC
(In reply to taraathan@gmail.com from comment #9)
> I have added $wgShowExceptionDetails = true; to LocalSettings.php
> Where do I look for the stack trace?

https://www.mediawiki.org/wiki/Manual:How_to_debug states that more details (like a stack trace) should be shown on the "Fatal error" page itself.
Comment 12 taraathan@gmail.com 2014-09-29 12:01:58 UTC
So far I haven't figured out what the page is that triggers this "Fatal error". The frequency pattern in the log file, and the absence of users reporting problems, suggests that it happens when some bot is crawling our site.
Comment 13 Andre Klapper 2014-11-12 01:45:41 UTC
(In reply to taraathan@gmail.com from comment #12)
> suggests that it happens when some bot is crawling our site.

You might have server logs with timestamps to compare with? :)

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


Navigation
Links