![]() who'd have thought that all my desperate fixes were thereby having zero effect? How is anybody supposed to know this? lol it was my host's aggressive caching retaining the broke wiki (for up to 12 hours!). but after hours of frustration, it turns out it wasn't my wiki's problem at all. First on Monday I appear to have completely gorked my wiki due to a simple LocalSettings.php typo. and Bam, I can log in just fine! (not incognito) Problem fixed. So I deleted all cookies associated with my tiny wiki website. So then, given what the Manual said, it seemed quite possible that my cookies (on my own PC browser) were causing the problem. So I tried logging into the Editor account incognito. Remember I said I could log in with my Admin account just fine, but not Editor account? Well, I had been logging into the Admin account incognito (Win10 Chrome) so it would not confuse my non-incognito Editor logon. One of the first bullets here was "Does it persist after clearing cookies for the wiki domain? When logging in in incognito mode?"Īt which point it hit me. So I googled "Mediawiki browser dev console" and the top hit was Manual:How to debug/Login problems. or ones on the host server? I have no idea where any of this would be on the host server, or if there even is such a thing. what "browser dev console"? The browser on my PC? Something on my SiteGround site tools? Cookies on my PC. I wasn't sure what you were even talking about. I have manually flushed the server cache to make sure that's not a problem. In case it matters: Yesterday I had problems that I later id'd as due to host-server caching problems, thanks to helpful people here. Can someone point me in the right direction? I'm using MW 1.35.1. If I try to google this, all I get are a zillion hits about how to reset my password. (But I do all edits with the User account, so folks won't see the admin username.) The one with problems is my User account, but the admin account has no issues and can log on okay. Please resubmit the form.įortunately I'm not panicked because it's my tiny personal wiki that only has two accounts for me. I keep getting a message that it's wrong that inevitably leads to the error message: There seems to be a problem with your login session this action has been canceled as a precaution against session hijacking. So I used Reset Password and typed in what it said. I didn't change my password but my usual one quit working. So I deleted all the cookies in my local Win10 Chrome for my wiki site and voila, no more problem. Which told me it was probably my browser's cookies. I tried that, just for giggles, then deleted the directory.Update / Fix: After recommend, I googled Manual:How to debug/Login problems and tried logging in using incognito - and it worked. I tried this crazy solution that said you should create a tmp directory in the root of mediawiki and give it 777 access. I looked through the user accounts in the database to make sure their change password script hadn't done anything odd, and it all looks fine. But obviously, that can't fix this issue. I find other's who have had this error with an older version of mediawiki, and the next version of mediawiki seems to have fixed their problem. Go back to the previous page, reload that page and then try again. There seems to be a problem with your login session this action has been canceled as a precaution against session hijacking. Now no one can log in, and everyone gets the same error of When I ran their command php maintenance/changePassword.php -conf=/var/www/html/LocalSettings.php -user=myuser -password=newPassword I haven't set up email on the server yet, so I was going to reset a users password using the maintenance/changePassword.php script that mediawiki provides. I'm using MediaWiki 1.27.0 on Ubuntu 14.04
0 Comments
Leave a Reply. |