Repository navigation
Upgrade from 2.3.8 to 2.3.12 locked out? #6652
Replies: 2 comments 7 replies
|
Hello @NECPWAweb, Please do carry on to 2.3.12 rather than settle back on 2.3.8. The releases since 2.3.8 close holes that let someone with no account run code on the server, or let an ordinary member make themselves an administrator (2.3.11, 2.3.12). Here's the setting I'd check first, while 2.3.8 still lets you in: Admin » Preferences » Security & Protection » Password transmission method If it says anything other than Plaintext, set it to Plaintext and press Save. If the box is greyed out, just press Save on that tab, and e107 switches it to Plaintext for you. Then upload 2.3.12 again, log in, and run the database update it asks for. Plaintext isn't a step down on an Why I suspect it. Sites set up before 2.3.0, including ones brought over from v1, were left with login tracking in cookie mode, and no later update changes that. Up to 2.3.11, cookie mode kept the CHAP script (that "transmission method") off the admin login page, so the setting did nothing. 2.3.12 removed cookie mode for security reasons, so the script now runs: when you press Log In, it empties the password box and the browser won't send the form. I set up a test site that way (2.3.8 with cookie mode and CHAP on, then the official v2.x to 2.3.12 upgrade archive unpacked over it), and the admin login did exactly that in Chrome. With the method set to Plaintext, the same site logged straight in. If it already says Plaintext, it's something else, and I'd need to know what the screen did when you pressed Log In:
|
|
OK everything finally sorted this morning however you may want to add a note to say switch from cookies to sessions in Admin Prefs Security and Protection before installing the upgrade from an earlier version |




Uh oh!
There was an error while loading. Please reload this page.
Downloaded the upgrade zip for 2.3.12, unzipped and ftp'd to site to run upgrade and can't log in. Credentials don't work. Uploaded the backup files from previous version and can login ok, so anyone got any idea what the issue could be please?
All reactions