Update from v3.0 STABLE to v3.1

Hi

I've tried to find out how to update to the new v3.1 RC5 from v3.0 but couldn't find any helping info... I just read this note how to update from previous v3.1 versions. Would be great if you could provide me with some simple instructions!

Cheers!
*Miki

Hi schickimiki,

There is no automated upgrade :-(

For security I'd suggest that you do the following on a test site, install the old version of ChronoForms, backup all the jos_chrono... tables from the live site and restore them on the test site (this is not necessary but could save you from some problems).

[list]

Backup your forms from the old version and all the jos_chrono... tables from the database.

Uninstall the old version of ChronoForms

Reinstall the new version

For each form, create a new form in CF, open the cfbak file in a text editor and copy and paste over the Form HTML and any other code box contents from the old form into the new one

Add other configuration settings as necessary

Test the new form

Restore any corresponding data table to the new site.

Repeat for other forms.

[/list]
If you did this on a test site then backup all the forms from the test site and restore them and the corresponding data files on the live site.

This all sounds complicated but in practice it isn't too difficult and should take you 10-20 minutes for the first form and 5-10 minutes for each form after that.

Bob

Thanks GreyHead,

I've done what you suggested and upgraded to the latest version of chronoform.

I have 2 problems:
1) trying to validate I keep getting the message:
We couldn't validate your key because of some wrong data used
while I have entered the licence code in the parameters and saved and entered the instant code.
2) I've tested 3 forms, and I found a fundamental difference, while before the length of the field was fixed, now is variable making the form all mixed up. In addition, each field goes to the next line, while before I could keep several field in line simply not adding div class clear.

Can you help me please

Thanks

Raffaele

Hi Raffaele,

For any question about licensing or validation of any of the ChronoEngine products please contact Max directly by using the Contact Us form from the link above. I don't know how Max has the product validation set up.

I think that the input length is still the same, but I'm not certain. Do you have "Load ChronoForms JS/CSS" set to 'Yes' on the form General Tab? Please can you post or PM a link to one of the forms so that I can take a quick look.

Bob

Hi GreyHead,

I've resolved the validation problem, but I've still the problem with the form layout...

Hi GreyHead,

I've managed to migrate to 3.1 RC5.5, and validate. I've also migrated the first form, discovered that div class "clear" is now "cfclear" and that /div doesn't work anymore and to have multiple fields in the same line I have to use tables - the multiholder wizard doesn't appear to work for some reason....
Now I'm confronted with another problem: in the form I have a PHP tag with the following lines:

$menus = &JSite::getMenu();
$menu  = $menus->getActive();
$itemid = $menu->id;

in order to save the form I had to cancel these lines as I get an error otherwise. Any idea why it happens and a workaround?

Thanks for your help
Raffaele

Hi Raffaele,

/div should work OK - any valid HTML should be fine. There may be a CSS problem - I htink Max changed it between the releases. (cf_clear was added because 'clear' was used by many templates).

The multi-holder is quirky, but does work. The numbers you have to add relate to the order the elements were added to the Wizard box - not to any visible number.

There's also a 'feature' in this version that attempts to evaluate the Form HTML when you save the form in the administrator to extract the input info. Unfortunately this fails if there is any PHP in the Form HTML. The workaround is to add this snippet at the beginning of the first PHP block you add.

<?php
if ( !$mainframe->isSite() ) { return; }
. . .

Bob