@trialanderror I get where you’re coming from, but I agree with Tom that this for free software would be too much of a nightmare to do LTS support on. I mean, there isn’t even a support team. I’m glad they don’t spend a ton of time going back to old codebases and backporting it. The installer does a good job of not blowing stuff up and the db schema typically upgrades fine too.

I say “good” because it isn’t totally transparent about what’s going on, so you do actually have to be a bit familiar with the upgrade process to make sure that you don’t do anything that could lead to loss of data.

@tom-elliott This works after upgrading to version 1.5.2.28

@tom-elliott
I pulled the working branch: FIXED!
Thanks.

FOG 1.5.2 (working-branch)

Tested - works as expected. Thanks.

@TrialAndError phew, I’m glad the issue is mostly fixed. Thanks for helping me debug it!

@uwpviolator You should be able to use the new client, but it won’t automatically update. As far as the communications between the client the server, nothing has changed.

The only other difference, your devices won’t automatically update to 0.11.13, unless you download the files from github, place them in place of your current files (under /var/www/fog/client/), and then edit the /var/www/fog/lib/fog/system.class.php FOG_CLIENT_VERSION line to 0.11.13.

@Tom-Elliott you are right! That was the problem. I do not know why i have two instances - i will clear and fix it tomorrow! Thank you Tom!

@Tom-Elliott
@george1421

Thank you for your answers.

I will give it a try next time I need some new challenge!

https://news.fogproject.org/fog-1-3-4-rc-1/

Is this a new problem? Has it worked in the past and just quit?