-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I know you guys are probably getting tired of seeing my name appear on this list by now, but I've run into yet another 1.18.0 upgrade issue. After lots of debugging over at the Bugzilla site, I finally found out my custom skin was the cause of most of my 500 server errors. I now have 1.18.0 running successfully, complete with my own custom skin (now properly derived from MonoBook rather than the hack job I did earlier).
Only... now I can't log in.
Every time I attempt to log in I receive the following cryptic error:
Login error <nocookiesforlogin>
I know for a fact that my username and password are correct, and this is my own site so I'm certainly not blocking my own cookies. I'm not using any of the $wgCookie* variables; those are all set to their default values. I've tried tweaking some of these, including setting $wgDisableCookieCheck = true, with no obvious change in the result.
The only thing I can possibly think of that might be affecting this is the fact that I use Apache mod_rewrite to force login requests to HTTPS mode so the password will be encrypted. The <form> tag does not include the protocol as part of the action value, so if I submit the form in HTTPS mode it *should* stay in HTTPS. However, as with everything else I've complained about, this worked without a hitch in 1.17.1 and below and stopped working with 1.18.0.
Any ideas? I want to make sure it's not something stupid I've done before filing a bug report.
- --
Jeff Darlington General Protection Fault http://www.gpf-comics.com/