Last modified: 2004-12-08 17:52:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
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 treegraph
 
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

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.


Navigation
Links