Hello,
We now have a live environment with ChronoForms v3 and we plan to move to Joomla 2.5 with Chrono Form v4. How can I backup and restore forms into v4.
Backup an form into V3 and restore into V4 doesn't work, i'm getting the following error: "The file uploaded was not a ChronoForms forms V4 backup file."
Hopefully someone can help me.
Thanx
We now have a live environment with ChronoForms v3 and we plan to move to Joomla 2.5 with Chrono Form v4. How can I backup and restore forms into v4.
Backup an form into V3 and restore into V4 doesn't work, i'm getting the following error: "The file uploaded was not a ChronoForms forms V4 backup file."
Hopefully someone can help me.
Thanx
mgdejong,
The lack of a migration path from v3 to v4 is (in my humble opinion) a serious issue. Certainly for paying customers (which I'm not by the way).
Just like you, I've developed a multi forms (+20) application using v3 and I'm supposed to redo all those forms in v4. This is not good news ... to put it mildly.
However when looking into the migration (technically speaking) I must admit it is a nightmare (if not totally impossible). Largely due to the customizations in the HTML code. But also because of fundamental differences between v3 and v4.
HOWEVER I do believe there should be a possibillity to AT LEAST migrate the form layout. So the bottom line is that I'm seriously considering writing code for an additional "Backup to v4" toolbar button in v3. It will migrate/convert the code generated by the v3 Form wizard to v4 format !! However this means customizations will NOT be migrated. Those will have to be redone just like ALL the other fancy stuff. Remember this is FORM
LAYOUT migration ONLY.
I admit it's not perfect but believe me this strategy will probably save you a lot of clicking in the v4 Form Wizard !!
There is one caveat. For this method to work you MUST have build your form(s) using the Form Wizard in v3. These are the ONLY forms that will migrate the layout 100% to v4 using "my" migration methodology.
If you have initially build the form using the v3 Form Wizard and then customized the HTML code (let's call this a hybrid form) then the customizations will be lost during migration. Only the Form Wizard code will be migrated. You will have to redo customizations in v4. So the layout of hybrid forms is migrated less than 100%.
The layout of forms build WITHOUT using the v3 Form Wizard (simply copy/past HTML code ) will NOT be able to migrate. (Unless you reverse engineer the Form Wizard code ... but if you do that you might just as well rebuild the form in v4).
I've already started writing the necessary code. However writing code takes time. And time is money. Due to other work that needs to be done as well I've temporarily halted my Form layout migration project.
If you (or anyone else) think(s) the above explained migration adds value to v3 please let me know. The more votes the better. I even may get inspired. With approval from Max I may even make this a little bit commercial. Thinking of a small fee, implemented just like Bob did with his documents.
So speak out and tell me ... Do you like the form layout migration idea and do you think it is worth paying a small fee for (Again with Max's approval which by the way I don't have yet. Max when you read this, send me a pm and we'll work something out ... assuming there is a reasonable demand that justifies spending time on writing the necessary code).
Hmm ... tea cold again. Oh well, let's make another one ... and get the hell out of this forum !
PolderGuy
The lack of a migration path from v3 to v4 is (in my humble opinion) a serious issue. Certainly for paying customers (which I'm not by the way).
Just like you, I've developed a multi forms (+20) application using v3 and I'm supposed to redo all those forms in v4. This is not good news ... to put it mildly.
However when looking into the migration (technically speaking) I must admit it is a nightmare (if not totally impossible). Largely due to the customizations in the HTML code. But also because of fundamental differences between v3 and v4.
HOWEVER I do believe there should be a possibillity to AT LEAST migrate the form layout. So the bottom line is that I'm seriously considering writing code for an additional "Backup to v4" toolbar button in v3. It will migrate/convert the code generated by the v3 Form wizard to v4 format !! However this means customizations will NOT be migrated. Those will have to be redone just like ALL the other fancy stuff. Remember this is FORM
LAYOUT migration ONLY.
I admit it's not perfect but believe me this strategy will probably save you a lot of clicking in the v4 Form Wizard !!
There is one caveat. For this method to work you MUST have build your form(s) using the Form Wizard in v3. These are the ONLY forms that will migrate the layout 100% to v4 using "my" migration methodology.
If you have initially build the form using the v3 Form Wizard and then customized the HTML code (let's call this a hybrid form) then the customizations will be lost during migration. Only the Form Wizard code will be migrated. You will have to redo customizations in v4. So the layout of hybrid forms is migrated less than 100%.
The layout of forms build WITHOUT using the v3 Form Wizard (simply copy/past HTML code ) will NOT be able to migrate. (Unless you reverse engineer the Form Wizard code ... but if you do that you might just as well rebuild the form in v4).
I've already started writing the necessary code. However writing code takes time. And time is money. Due to other work that needs to be done as well I've temporarily halted my Form layout migration project.
If you (or anyone else) think(s) the above explained migration adds value to v3 please let me know. The more votes the better. I even may get inspired. With approval from Max I may even make this a little bit commercial. Thinking of a small fee, implemented just like Bob did with his documents.
So speak out and tell me ... Do you like the form layout migration idea and do you think it is worth paying a small fee for (Again with Max's approval which by the way I don't have yet. Max when you read this, send me a pm and we'll work something out ... assuming there is a reasonable demand that justifies spending time on writing the necessary code).
Hmm ... tea cold again. Oh well, let's make another one ... and get the hell out of this forum !
PolderGuy
This topic is locked and no more replies can be posted.
