The Elearning Community

I followed instructions at https://docs.formalms.org/reference-gui ... _procedure and copied new files to server. The instruction to go to http://www.yourwebsite.com/upgrade gave me no upgrade option and seemed entirely irrelevant. I then logged-in as admin and saw a message 'You need database upgrade'. I clicked it and followed instructions but at System Check stage the [Next step] button was inactive. Please advise what I do next to upgrade the database, bearing in mind I am on a hosted server, not my own.

Many thanks,

Bob

You have limited debug capabilities on a hosted server, and you need system investigation to understand what went wrong.

bbater2021 wrote: ↑Thu Jul 22, 2021 6:52 pm I followed instructions at https://docs.formalms.org/reference-gui ... _procedure and copied new files to server. The instruction to go to http://www.yourwebsite.com/upgrade gave me no upgrade option and seemed entirely irrelevant. I then logged-in as admin and saw a message 'You need database upgrade'. I clicked it and followed instructions but at System Check stage the [Next step] button was inactive. Please advise what I do next to upgrade the database, bearing in mind I am on a hosted server, not my own.

Many thanks,

Bob

Sorry for asking a stupid question: for sure you typed "xxxxxxxx/upgrade" where xxxxx is your domain, and not literally "yourwebsite.com/upgrade", right?
Sorry again, but I had to ask.

Not a stupid question, Max. I did enter the URL as it was (doh!). I'll try the correct one now...

Via the correct URL (greenpath.fyi/upgrade) I go though the same pages as before until the System Check page, when the [Next step] button is again inactive.

And do you see a red-coloured value, highlighting an issue? I see it right at the top, it says 7.4.21 and it's in red. And Forma 2 only supports 7.0.33

Forma 3 will support newer versions of php, but until then you should ask your provider to downgrade the php version.

Thanks Max. My management console reports that the domain in which Forma LMS is installed has PHP 5.6 installed. 7.4 is in the main domain, so maybe the install procedure is picking up the PHP version from the main domain. Other than 5.6, my other choices for PHP version are all 7+, as you can see from the image attached. I think the easiest thing for me to do to get under way is to delete the v. 2.4.4 install and revert to my backup of v. 2.3,. then wait for v. 3 to come out. Thanks for sticking with the problem anyway.

Regards,

Bob

The best thing is learning how the web server handles PHP versions for vhosts.

I am trying to move my existing FrontAccounting (v2.3.24) from an old server to a new server (v2.4.4).

My first approach was to build the new server with Ubuntu 18.04, and install FrontAccounting 2.4.4. Then backup the db's on 2.3.24 and restore them onto 2.4.4 on the new server. I soon realised that will not work,. FrontAccounting 2.4.4 refused to upload the backup.

I can't take the current server to 2.4.4 because it runs an old version of Centos and it cannot be upgraded so I cannot make the php requirements.

I then tried installing Ubuntu 16.04 on my server with frontaccounting 2.3.24 but that does not work as I am getting this error when trying to verify the install: Your PHP has to have MySQL extension enabled.

I have been unsuccessful so far in getting past this. Is there a work-around that would allow me to install and FrontAccounting 2.3.24 on Ubunu 16.04 (or even better 18.04)?

Is there another method of transferring the data from one version to another using different servers and OS?

You're in the wrong place. This is not FrontAccounting forum.