Last modified: 2004-12-08 17:52:50 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 T3039, 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 1039 - Warning [host=]: array_key_exists(): The second argument should be either an array or an object in /usr/local/apache/common-local/php-1.4/includes/MessageCache.php on line 233
Warning [host=]: array_key_exists(): The second argument should be either an ...
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC Linux
: Highest major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://commons.wikimedia.org/wiki/Mai...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2004-12-08 15:36 UTC by Peter Gervai (grin)
Modified: 2004-12-08 17:52 UTC (History)
0 users

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

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

Description Peter Gervai (grin) 2004-12-08 15:36:26 UTC 
shows php error on top, page visible though.

Warning [host=]: array_key_exists(): The second argument should be either an array 
or an object in /usr/local/apache/common-local/php-1.4/includes/MessageCache.php on 
line 233
Comment 1 Peter Gervai (grin) 2004-12-08 15:40:36 UTC 
correction, it's on the top of every commons page. raising prio and severity.
Comment 2 Zigger 2004-12-08 17:42:02 UTC 
From #mediawiki : "... someone changed the memcacheds configuration but did not
update the 1.4 settings" ... "syncing...".
Comment 3 Brion Vibber 2004-12-08 17:52:50 UTC 
Root cause was that someone rearranged the memcache systems without updating the configuration file.

Error message was caused by incorrect checking at runtime for failure.
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