-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/10/2011 12:18 PM, Platonides wrote:
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. The md5 of the file is:
59498d33f47acb0a25cb1eec986fad1d languages/messages/MessagesEn.php
The MD5 hash matches my copy, and the two lines you quoted were present. Since I installed 1.18.0 into a clean directory, this makes sense.
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)
After digging a bit deeper, I'm getting the same behavior. I may have just been looking at the wrong line in the output, as I'm seeing the cookie being sent now.
Again, having the cookie secure isn't necessarily a problem; in fact, I rather like it that way, truth be told. (I'm all about encrypting session data.)
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...
Now that you mention it, I've had trouble with this in the past. I'm not sure if it's the occasional PHP upgrade, but sometimes I lose write permissions on the directory session.save_path is set to in php.ini. This often doesn't present a problem as none of my code and apparently none of the other third-party apps I have installed seem to use sessions. It's often MediaWiki where this first crops up.
I just went and checked on it, and the path seems to have 770 permissions, owned by root:apache. Unfortunately, I have Apache running under a non-standard group, meaning Apache shouldn't be able to write there. I just changed the group ownership to the group Apache is running under and, as you might guess, it suddenly works. I guess I'm just going to have to be more diligent when Fedora pushes out PHP updates and watch the permissions on that directory.
I'm still getting the "You must have cookies enabled to log in" message over the login prompt, however. This isn't necessarily a problem since I'm the only one with login access (at the moment), but it seems odd that it should still be showing. That is, unless it's a generic notification and it's always meant to be shown. I don't remember seeing it before, but maybe I just hadn't noticed it.
Thanks for the input.
- --
Jeff Darlington General Protection Fault http://www.gpf-comics.com/