Update ftools to formtools

[barrydollar]

I have followed the formtools update directions. The problem I am having is when I download the zip of all the needed updates and unzip the folder, it is named 'formtools' while the folder in my cpanel /public_html is named 'ftools'. I tried uploading a zip of the 'formtools' folder and extracting in my cpanel /public_html and it breaks the site. I also zipped the 'ftools' folder and if I unzip it in the cpanel /public_html the site works again.

How can I update when the old and now folders are named differently?
currently running 2.2.5

[benkeen]

Hey @barrydollar, don't worry - the folder name doesn't matter. You just need to overwrite the contents of your ftools folder with the contents of the formtools folder from the generated zipfile. Note: you can't just renamed the new folder because your old one contains the all-important global/config.php file which contains your DB info and other settings. Plus your old folder may contain uploaded files and other stuff. So just overwrite the older folder contents with the new and the new files will overwrite the old ones, leaving the other files intact.

But yes, always back up the files & DB just as a safeguard.

[barrydollar]

I did update the form builder via FTP and the updates broke everything (see screenshot). I then attempted to reload a back-up of the /public_html/ftools folder which seemed to work but now the database apparently is no longer connected. I know noting about working with databases.

Before, I would get a log-in screen here > http://gbcforms.com/ftools/index.php
But now it opens an install screen (see screenshot) asking me to set-up a database, config file, etc. But we already have a database that has somehow become disconnected. I do not want to start over. We would never recapture all our customers.

Currently I have a ticket in with out cPanel host and hoping some how they can restore, but wanted to put it here in case I am missing something that might reconnect the database.

[barrydollar]

My cPanel support was able to restore everything. But now I am afraid of trying to update. Any thoughts?

[benkeen]

Hey Barry, I ran through some tests tonight just to check there was nothing wrong and I did ran into a problem with a blank page which is suspiciously like what you described... But I'm not convinced it wasn't caused by trying to upgrade an old invalid Form Tools installation which I had been doing manual changes to. Sorry for the wait but I'd like to test this out again tomorrow night with a clean older version.

Either way, looking through the code I can see a possible reason for the blank page: it can occur when attempting to load up a module that no longer exists. I'll add some better error handling in 3.0.13 to improve that.

Also, I have to ask: after you uploaded your files via FTP, did it remove your old global/config.php file & modules folders? (the content of the modules/ folder)? It almost sounds like your FTP client was removing all the old files then replacing them with the new ones. That happens on Mac when copying files over (they just wipe out old folders) but I've never seen that behaviour with an FTP client.

That would explain the errors you were seeing - both the blank page + installation screen.

[barrydollar]

I am using Filezilla for FTP and I am on a Mac.
I can't say that I noticed exactly how the FTP was moving files. I was following your instructions. I was prompted with the question to over write existing files and of course I said yes to all, and the files transferred.

I inherited this project and it seems that it has not been updated in a long time. So I am wondering if jumping through so many updates is it breaking something?

In choosing the updates, I chose 2.2.6 for the core and the latest for everything else due to the warning at the top of the page (see screenshot). Once I completed those updates, I planned to then come back and do the core update 3.0.12.

[benkeen]

Hey Barry, actually one thing does look wrong in that last screenshot you posted: the versions for the modules should reflect the selected Core version, but it looks like they're targeting FT3 versions. Possibly this is a bug on my end.

EDIT: yes the zipfile being generated is definitely incorrect.

I'm awfully sorry, but I'm going to need some time to solve this and I'm going to be away this weekend. But I'll look at this as soon as I can and post back here.

[barrydollar]

When I generated the update panel, the dashboard opened with all the updates needed, then I switched the core from 3.0.12 to 2.2.6 none of the others changed automatically but the API dropped off (see screenshot).

[benkeen]

Hey Barry, apologies for the long wait. I'm looking into the upgrade issue tonight & I'll keep you posted. Would you mind creating a separate ticket for the Swift Mailer problem?

Ben

[benkeen]

Hey Barry, so I think this problem may actually be moot in your case. You're running 2.2.5, so it's fine to upgrade from that version to the latest version of Form Tools 3: https://docs.formtools.org/upgrading/3_0_0/

If you'd like a hand upgrading, I'm happy to help out. Feel free to email me at ben.keen@gmail.com.

Ben

[barrydollar]

I can try to run the updates again. Are you saying I will avoid the blank screen issue by upgrading directly to 3.0 version?

I viewed the upgrade link information. It says, "After upgrading you will need to re-publish all of your Form Builder forms." How will this upgrade and republishing of forms impact my current users? We have over 1.400 users that have standing forms (orders) that they can log-in and update as needed.

[benkeen]

Are you saying I will avoid the blank screen issue by upgrading directly to 3.0 version?

I'm afraid not sure what caused the blank screen issue beyond what we already discussed - files not being uploaded properly or maybe corrupted en route. I don't recall encountered that with an upgrade before. But do install this version of the System Check module (if you're not already running it) first:
https://github.com/formtools/module-system_check/releases/tag/1.1.0
(installation instructions: https://docs.formtools.org/userdoc/modules/installing/)
And then inside the module pages, run the test to confirm your server is compatible with running Form Tools 3.

Since this is potentially problematic, of course be sure to back up the DB + files prior to upgrading. And pick a quiet time to attempt the upgrade.

How will this upgrade and republishing of forms impact my current users?

It shouldn't affect them at all. Form Tools 3 rewrote a lot of the code from Form Tools 2 and the form builder forms referenced old Form Tools 2 methods. Republishing them recreates the form code with the newer methods to enable them to work normally.

Let me know how it goes.

[barrydollar]

I do appreciate you help on this. Thanks.