On 05/12/11 04:02, Jeffrey T. Darlington wrote:
On 12/4/2011 3:58 PM, Platonides wrote:
That's strange. Do you have the language files up to date?
I have no idea. I'm starting from a clean yet slightly tweaked copy of the 1.18.0 code (I have a custom skin derived from MonoBook), and I made sure to run maintenance/update.php to update my database during the upgrade. I've also run maintenance/rebuildLocalisationCache.php, which was requested when someone else was trying to debug my prior upgrade issues. Beyond these steps, I've never had to "update my language files" before.
I was thinking that instead of the languages/messages/MessagesEn.php shipped with MediaWiki 1.18 you could have there a copy of an older release.
You should have there on line 1074:
'nocookiesforlogin' => '{{int:nocookieslogin}}', # only translate this message to other languages if you have to change it
and in line 1072 (you also seem to miss this):
'nocookiesfornew' => 'The user account was not created, as we could not confirm its source. Ensure you have cookies enabled, reload this page and try again.',
The md5 of the file is:
59498d33f47acb0a25cb1eec986fad1d languages/messages/MessagesEn.php
Is your wiki available somewhere?
It's publicly available in read-only mode; I'm the only one with admin privileges, and nobody else has or can create a login. I've been planning on taking on a few volunteer wiki-wranglers, but I haven't started taking applications yet. You can take a look if you want, but since you won't be able to log in anyway I don't know if that will help.
Yes. I just wanted to confirm if it was sending the cookies. Unlike what you report, I do get a wikidb_session cookie (and it is indeed marked as secure, $wgCookieSecure is defaulting to true from the https access) Still, filling a random user & password, I get the same error you reported. Your setup _should_ work, these errors are usually related to php not being able to write in the session_path, but if you didn't touch php and it worked before... The rewrite rule shouldn't matter, either but I'd ask you to remove it, and check if that makes a difference (you don't even need to enter the right credentials, as nocookies has higher priority than badpassword).