Last modified: 2006-04-04 02:42:48 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 5432 - Incorrect cookie prefix leads to problems with persistent logins
Incorrect cookie prefix leads to problems with persistent logins
Product: MediaWiki
Classification: Unclassified
User login and signup (Other open bugs)
PC All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-04-02 20:17 UTC by Ilya Schurov
Modified: 2006-04-04 02:42 UTC (History)
0 users

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

quick and dirty patch (1.88 KB, patch)
2006-04-02 20:19 UTC, Ilya Schurov

Description Ilya Schurov 2006-04-02 20:17:52 UTC
If $wgDBprefix is set and $wgCookiePrefix not equal to $wgDBname, problem with
persistent logins occurs (i.e. the system doesn't remember user even if
appropriate options is set). In file includes/User.php the system tries to use
$wgDBname as cookie prefix on setting and then $wgCookiePrefix on getting the

See also bug #1396.
Comment 1 Ilya Schurov 2006-04-02 20:19:49 UTC
Created attachment 1494 [details]
quick and dirty patch

Proposed patch looks to solve the problem, but not yet well tested.
Comment 2 Brion Vibber 2006-04-03 00:55:02 UTC
Fixed in trunk, r13436. Per patch, plus fixes in User::logout().
Comment 3 Ilya Schurov 2006-04-03 18:37:36 UTC
OK, thanks. How long does it takes for fix to appear in current CVS version? 
Comment 4 Rob Church 2006-04-03 19:30:43 UTC
We're no longer using CVS due to SourceForge's unannounced and unexplained
downtime. The SVN repo is now maintained at and there's
no lag for anonymous reads. More information at
Comment 5 Ilya Schurov 2006-04-03 21:26:33 UTC
Thanks, Rob. BTW, there's no any notes about SVN on -- is it just temporarily situation and
will be fixed soon?
Comment 6 Rob Church 2006-04-04 02:42:48 UTC
Brion's in the process of updating that documentation, etc. now.

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