To be honest, I'm not surprised.
You sent me the 3.3.5 database. Errors already present in the 3.2.2 may have induced other/new errors in the 3.2.11 and then more errors in the 3.3.5.Trig0r wrote: ↑Sun Nov 28, 2021 10:36 pm I downloaded the files to do a 3.2.2 to 3.2.11 upgrade, which seemed to work, I then did the same to 3.3.5, I can pick which version of PHP the site runs, 7.1/7.2/7.3/7.4/8, once I was on 3.3.5 I then set the PHP to v8.
It wasn't until I went into the ACP and started trying to prune the hundreds of inactive/spam accounts that things started going wrong and I started to get SQL errors as above, obviously I should have tested the 3.2.11 install properly as this issue might have been present at that time.
Thanks for the offer, I'll fire you a PM, it might be something simple, but I've not sat down in front of this thing for more than 30 minutes at a time as its a weekend and I keep getting interrupted by the other half which is mighty annoying when you're trying to do stuff...
Nothing wrong there - you were not logged in when you ran the update.
I wasn't doing anything on the 11th of November though, I only started looking at getting things back up and running on the 25th/26th..
So its not looking like an actual db error at all then?warmweer wrote: ↑Mon Nov 29, 2021 1:24 pm OK, it seems I spent about an hour unneeded testing and looking for the errors to no avail. I did a structural comparison of your database with a clean 335 and the table definitions are OK, the necessary data in the config_table is present, permission system and modules, all OK
If any errors occurred, they were probably due to your browser and board cache (I had a couple to start with because force server settings was set to true and I got redirected to the live site).
Just a hint (for the future should a problem arise and you need to send the database to someone): When taking a backup (with phpMyAdmin or any other database management system) don't use extended inserts. (phpBB constructed backups don't use extended inserts).
Added: almost forgot: there were no inactive users at all
I had a white page or 2 and an unwanted redirect because of force server settingTrig0r wrote: ↑Mon Nov 29, 2021 3:33 pm
So its not looking like an actual db error at all then?
Theres still something going on, the recovery from the hosts is now showing 3.2.2 which is right, but sometimes when I go from one ACP menu to another I get an HTTP500 error from my browser..
On the inactive user side, I was going to crop out all of the spam accounts that had been created, so 0 post users, manually checked against people I know are real, but not posted, and then bin them off.
I tested your board using php 7.1.11, 7.4.3 and 8.0.7 (phpBB3.3.5)Trig0r wrote: ↑Mon Nov 29, 2021 4:09 pm I've changed the cookie name, force URL, cleared the cache.
I have also pushed the PHP version back to 7.1 as mentioned I was getting PHP errors, doing that seems to have stopped the errors popping up and the board is a lot more responsive now.
Will do another backup, and then see about going to 3.2.11, if that works and is PHP error-free then I will roll the PHP version up to something a bit newer as the CP does moan about 7.17.2 being depreciated.
If 3.2.11 works, then another backup and see how 3.3.5 goes.