Jump to content
Froxlor Forum
  • 0

Problems after Update to 0.10.1


JizaiGinji

Question

Halle Everyone,

today i tried to update my froxlor from version 0.9.38 to 0.10.1. Im running on a debian Jessie server.

After the update i cant edit, create or manage everything in froxlor anymore. On Customer-Edit for example i get an empty page. If i try to change a domain i get an empty page after pressing the save button.

Im a little bit lost here. Has someone any idea what could cause this problem?

 

Best Regards

Ginji

Link to comment
Share on other sites

13 answers to this question

Recommended Posts

  • 0

Hello Ginji,

like d00p wrote, php version 7 or higher is required to run Froxlor 10. You are running Debian Jessie, and although that is long-term supported until June 2020 (see https://www.debian.org/releases/jessie/ for more info on this), I think you won't get php7 or greater packages for it (please see https://packages.debian.org/search?keywords=php7&searchon=names&suite=all&section=all for more on this).

So my suggestion would be to also upgrade Debian itself to the latest stable version (currently 10, codename "Buster"). I did, and Froxlor 0.10.1 runs very nicely on it.

Hope that helps,

and cheers,

Wolfgang

Link to comment
Share on other sites

  • 0
On 10/12/2019 at 7:55 PM, d00p said:

Ehm, sure you get php7 and greater for jessie, see https://packages.sury.org/php/

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.

Link to comment
Share on other sites

  • 0
1 minute ago, vrt said:

EOL or not, the php version check is an must have.

Yes, that's why I've added it (see https://github.com/Froxlor/Froxlor/blob/master/admin_autoupdate.php#L40) sadly I cannot change old installations where this check is not included. Sorry.

Also, it's clearly stated in the announcement of 0.10.0 - that's what things like that are there for, informing users about critical changes...

Link to comment
Share on other sites

  • 0
11 minutes ago, d00p said:

Yes, that's why I've added it (see https://github.com/Froxlor/Froxlor/blob/master/admin_autoupdate.php#L40) sadly I cannot change old installations where this check is not included. Sorry.

Also, it's clearly stated in the announcement of 0.10.0 - that's what things like that are there for, informing users about critical changes...

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.

Link to comment
Share on other sites

  • 0
3 minutes ago, d00p said:

well, as long as you did not run the updater / did the database backups. But why copy from an old server? Grab the files here -> https://files.froxlor.org/releases/

 

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.

Link to comment
Share on other sites

  • 0

Autoupdater Downloads and extracts. Then it redirects to the update procedure to update the database. Sounds like you did that. So using 0.9.40.1 files with that database won't work. Always backup before updating, it's even in our update wiki entry.

Link to comment
Share on other sites

  • 0
7 minutes ago, d00p said:

Autoupdater Downloads and extracts. Then it redirects to the update procedure to update the database. Sounds like you did that. So using 0.9.40.1 files with that database won't work. Always backup before updating, it's even in our update wiki entry.

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.
 

Link to comment
Share on other sites

  • 0

if you are using php-fpm or fcgid you can without a problem set up php7 only for froxlor and keep 5.6 for all customers.

16 minutes ago, vrt said:

I guess the name Auto-Update made me trust in it a bit to much, lesson learned.

Sorry....but "auto" and "update" together should never be trusted blindly. But hey, I've made that mistake myself quite a few times - could be worse, trust me :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...