Last modified: 2008-09-19 12:34:09 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 12304 - Using CACHE_DB as main cache throws a fatal error
Using CACHE_DB as main cache throws a fatal error
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.12.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-need-review
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-14 21:32 UTC by Alexandre Emsenhuber [IAlex]
Modified: 2008-09-19 12:34 UTC (History)
2 users (show)

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


Attachments
patch for Setup.php (2.62 KB, patch)
2007-12-14 21:32 UTC, Alexandre Emsenhuber [IAlex]
Details

Description Alexandre Emsenhuber [IAlex] 2007-12-14 21:32:28 UTC
Created attachment 4439 [details]
patch for Setup.php

When i want to use CACHE_DB as main cache, i got an fatal error saying "Call to a member function getConnection() on a non-object in /Library/WebServer/Documents/phase3/includes/GlobalFunctions.php on line 2267" wich is the function wfGetDB.
I suppose this due to wfIncrStats() on lines 205 and 209 in Setup.php that need the cache. However, $wgLoadBalancer is initialized at line 228.
When i put the 'SetupSession' of the setup just before 'User' and then the cache just before the initialization of $wgMessageCache, all works fine.
I suggest to change the order of the setup order to fix that error.
Comment 1 Aaron Schulz 2008-09-19 12:34:09 UTC
Fixed in r41023, 1.12 issue only

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


Navigation
Links