Forums

1. Maximum input of formname is 50 character, this is a very big limitation.
2. If we use upload component, mother form need to have data in File upload tabs as child forms have. This is a bit confuse to the workflow

Hope they could be fix soon 🙂 🙂

Best regard

Hi maxxoros,

1) How is 50 characters a big limitation on the form name - I can't imagine a useful form name that long??

2) Thanks, didn't know about the file uploads - I'll check it out later.

Bob

1. Not a form only, this is the form list, I have a very long form that need to be split into 5 child form: recruitpolicy1,recruitpolicy2,recruitpolicy3,recruitpolicy4,recruitpolicy5. So that is over 50 character and can not be type in.

Another issue with file upload. Eg: the upload component in 2nd form, if we choose wrong file extension, the validate wrong and it will push form back to the first form, with all data clear out.

Hi maxxoros,

I couldn't repeat this.

I found that the error message showed - but I stayed on the same step. And, if I have 'Try to Republish' set to 'Yes' the previous data is re-displayed.

I also found that it was sufficient to put the form upload settings in the Child form (not in the mother).

Bob

I install a new site in home and issue gone out...There must be a broken connection some where with hidden code in database. I will look into issue and report more detail. Also, the file upload also some kind of "broken data".

I will try to isolate all the issue soon.

Hi maxxoros,

Thanks - very helpful.

Bob

Now I have isolate all issue and point out what cause problem

1. I think you should extend more character here, 255 may be better 😀
2. Upload setting: we *MUST* set the file component and file setting with file:{} in LAST form so database could be updated. In some simple example, we usually create only 2 form, with 2nd contain these setting so evthing run okie. But if there are 3 step, and 2nd contain upload component, if mother form does not contain upload setting, we have *NOTHING* in database. However, this will lead to another issue, that is return to 1st form if fail upload. It is because the file validating is now belong to mother form so If fail, mother form is reload and display as page 1. I have tried the trick to enable upload setting in last child form and keep upload component in 2nd form, but fail. So, solution is your upload component MUST BE in last child form if you want to reload that page if upload fails.

3. I find out there is a very severe with current workflow we forget to mention, It is updating mother form after child form is updated, this thing cause many issue like: missing new field in child form to DB... The solution, is deactivate and then activate Multi-page plugin in mother form to re-generate new code. So I think we should make a button like: Update mother form to end all these kind of issue and add this to the instruction. So, if we only test and make them in multi step, nothing will be wrong, but in a real workflow we must back to edit many time.

Now we have solution for all issue and I am looking for a new hot-fix 😀 😀 .
4. I make sure if we by mistake select database for child form, even if we disable Enable Data storage, the data still be save in DB. This seem the auto-generate code of child form is activate and store in database. So the only solution now is delete the DB name by phpmyadmin. And if that is the last form, we also need to clear out Auto-generate code after remove DB name, or we will get the duplicate table.

Above list, is confirmed and hope they could be fix soon 😀

Hi Maxxoros,

There is something not quite right about your set-up here.

1) as I posted elsewhere the field length is 180 in the latest release - this is enough for twenty 8 character form names

2) I agree that file handling could be better. I'll test this some more, it is correct that the file name will only save correctly from the last step. (Unless you save each step as I posted earlier.)

2a) I can't replicate your problem with the uploda error messages, I get the current step re-shown. I will test again.

3) Makes no sense to me at all, activating and deactivating the plugin in the mother form doesn't change anything at all as far as I know. When you say "missing new field in child form to DB" do you mean that you have to add the new field to the database table. If so that's correct, ChronoForms won't automatically add new fields to the database table for you.

4) I don't understand 4 either. Or is it that you have created a different table for the child and have that set in the child. That makes sense but it's not a bug with ChronoForms.

Thans for all the hard work.

Bob

2a) I can't replicate your problem with the uploda error messages, I get the current step re-shown. I will test again.

Just enable file upload for mother form and you will be back to first form if upload fail. The reason we must enable it here is as I have explain: if upload component in 2nd form, and we have 3 steps, then data from upload component can not be inserted to DB. All my test show this result. To solve this we need upload enable in mother form.

3) Makes no sense to me at all, activating and deactivating the plugin in the mother form doesn't change anything at all as far as I know. When you say "missing new field in child form to DB" do you mean that you have to add the new field to the database table. If so that's correct, ChronoForms won't automatically add new fields to the database table for you.

I will explain in detail. In dbclasses field of mother form in #_chrono_contact, we have auto-generate code for field insert. However, if we have a new field in child form, dbclasses is not updated. So de-activate and activate plugin help re-generate code in dbclasses make mother form update to what s new in child form. Field in database must be added by hand is not what I mention here.

4) I don't understand 4 either. Or is it that you have created a different table for the child and have that set in the child. That makes sense but it's not a bug with ChronoForms.

For example you have 3 steps form. In 1st child form, if you have a DB selected, mean that tablenames=A_TABLE_NAME value in paramsall field of #_chrono_contact. Even if we have no data storage for this child form, the data still be inserted in DB after 1st step finish. I give solution is delete A_TABLE_NAME in database.

And now in 3rd child form (mean last child form in my example). Even it has NO tablenames, if there is auto-generate code, data still be inserted for this child form. And then, mother form, mean duplicating data.

You could test and see what I mean 😀

Hi Maxxoros,

I fixed #3,4 in the next release and then tested 2 and it seems to work fine, its just like any error message and I tested them before and all was fine, so get RC5.2 when its available and let me know!

Cheers
Max