I have a very large multi/wizard-form in a CF5. I was able to edit it and update it fine until a recent update, but I am not sure which one as I don't always have to modify this form in particular. I do test my forms and we use a staging area so I did check and make sure I could load/edit forms... I just think I missed testing the big one...
What's strange is that it isn't affecting all the forms I have in CF5, only this big wizard form.
In the fields section I get sometimes get an error about an unknown render_type index on line 1323 of /administrator/components/com_chronoforms5/chronoforms/views/edit.php when I try to update it.
Saving it toasts the form and then I have to recover it from backups or production.
I originally thought oh well I need this done so I started to re-create it since it only affect that form, but now I am having a similar issue on the version I just created. Whenever I save the new copy, it wipes out all the event actions of the form.
Has anyone seen this behavior before and any ideas on fixing it? This might have something to do with parse_str() limits as I am seeing some stuff about that in my error logs. How many fields is too many for CF5?
What's strange is that it isn't affecting all the forms I have in CF5, only this big wizard form.
In the fields section I get sometimes get an error about an unknown render_type index on line 1323 of /administrator/components/com_chronoforms5/chronoforms/views/edit.php when I try to update it.
Saving it toasts the form and then I have to recover it from backups or production.
I originally thought oh well I need this done so I started to re-create it since it only affect that form, but now I am having a similar issue on the version I just created. Whenever I save the new copy, it wipes out all the event actions of the form.
Has anyone seen this behavior before and any ideas on fixing it? This might have something to do with parse_str() limits as I am seeing some stuff about that in my error logs. How many fields is too many for CF5?
