GanstaZ wrote: ↑
Tue Nov 20, 2018 11:06 pm
Update to 3.1.x and after to 3.2.4. As i understand it, there's either a bug somewhere that modifies db when one is trying to update from 3.0 branch (may be related to mod mess in db) or a wrong update method that was used at some point in the past.
I received the latest backup but that is already from the messed up upgrade. I haven't been able to import it into a database yet but the config.php states 3.2.0-dev.
The files are a mix of modified 3.0.11 files and the new 3.2 files but some of the modified 3.0.11 files which still exist in 3.2.
I was hoping to get the non-working 3.0.11 database so that I could compare that to a clean 3.0.11 but since that's out of the question I compared them to 3.2.0-dev and it's mess.
I actually wanted to do that yesterday but Skype messed up my plans. I must have accidentally updated Skype from the old version (7) to the new version (8) which doesn't have the setting to stop it from listening to port 80 and 443, so Apache refused to start up. Had to uninstall Skype and search for the old version to download.
Anyway Apache is back in business now and I should be able to assess the real damage this evening.