Last modified: 2012-02-17 21:55:28 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 T36448, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 34448 - Call to a member function setTimestamp() on a non-object
Call to a member function setTimestamp() on a non-object
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
FeaturedFeeds (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Max Semenik
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-02-16 16:26 UTC by Sam Reed (reedy)
Modified: 2012-02-17 21:55 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Sam Reed (reedy) 2012-02-16 16:26:44 UTC 
Fatal error:  Call to a member function setTimestamp() on a non-object in /usr/local/apache/common-local/php-1.18/extensions/FeaturedFeeds/FeaturedFeeds.body.php on line 257
Comment 1 Sam Reed (reedy) 2012-02-16 16:56:33 UTC 
Fixded in trunk already it seems...
Comment 2 Sam Reed (reedy) 2012-02-16 22:49:52 UTC 
1 Fatal error:  Call to a member function setTimestamp() on a non-object in /usr/local/apache/common-local/php-1.18/extensions/FeaturedFeeds/FeaturedFeeds.body.php on line 346
Comment 3 Max Semenik 2012-02-16 23:02:04 UTC 
Blargh, mixed it up in my mind with another fix. Not sure about code path that causes it, but my guess is that r111698 should fix it.
Comment 4 Arthur Richards 2012-02-17 21:33:56 UTC 
I'm not seeing this behavior, perhaps because it's actually fixed now. But can you share steps to reproduce the problem in order to verify this is now resolved?
Comment 5 Max Semenik 2012-02-17 21:55:28 UTC 
My idea is that in some code paths objects were unserialized w/o static variables being initialized properly. Reproduction steps unclear.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links