vrt

Well that sucks ... I guess the name Auto-Update made me trust in it a bit to much, lesson learned. Of course it was on the only server i didn't set up and they forgot to include the froxlor db in the weekly db backup. I think i try to install php 7 then beside php 5.6. If i remember correct it was php-fpm on an other debian jessie server that let me choose which site runs with which php version. I could run froxlor with PHP 7 then and change the other sites one by one to php 7. Really bad timing, i had plans for summer 2020 to do that.

That's easier, thank you didn't think of that. What do you mean with "run the updater" ? I completly installed over "Auto-Update". It finished with a lot of "OK" Messages and that's it.

Are there known problems If i copy the froxlor folder from an old server. Should work if there are no database changes and i could at least win some time to try it on a local copy.

I have multiple systems running on php 5.6 and today i used the auto-update function on one server. Now i can't edit / manage anything (Null coalescing operator). .. If it's clear the update won't work with php 5.6, there should be a check if froxlor runs on php 5.6 and there should be at least a warning. I'm forced to do an update to php 7 now if i want to use froxlor again but on a productive server with a lot of sites it is an experiment. EOL or not, the php version check is an must have.