Lately I've noticed that saving actions in the backend keep failing. The page stays grayed out and there are some errors... with e in the console... When I reload the page, the last changes are no longer saved or individual fields are removed. My day's work today is rubbish! First attempts to back up the data (I export the CF8 table every 5 minutes) failed. I can see my last fields in the table, but not in the backend. I'll have to check more closely later. That reminds me, tables/forms LOCK when opening in the backend! Now and again I've opened forms multiple times by mistake. Save temporarily and only then save productively?
does this happen when you use "Quick Save" or "Save" ? maybe your forms have so many fields and you are hitting the maximum post size limit, the "Save" button will not be affected by this problem but the Quick Save will have a problem
How many elements do you have in the form and what is the max post size in your PHP settings ?
I usually use quick save. Scrolling up all the way always confuses me... I can't find my position again! I'd always liked the option to collapse form fields, groups for example, or a separate field for that.
yes, what are the max_input_vars ?
I think you are hitting the max limit, if your save keeps failing now with "Quick save" then please give "save" a try, does it work ? we are just checking if it works in your case
does the "save" button work or not ?
Yes, of course... But the problem has occurred 3-4 times so far, in different forms... sporadically and so far incomprehensible to me. The last error occurred when I inserted several SVG images with complex PHP actions within a loop.
but saving the form with the "Save" button does not produce the same problem with "Quick Save", correct ?
I can't say/write that. It definitely happened during the quick save. And also 3 or 4 times in the last few days... I've been using the quick save button for hours in a small form and I haven't had any problems. Although I think I had the problem once yesterday in this form. I only lost a few fields. I was able to restore them quickly. In the larger form, the lost fields are still missing. I can see them in the SQL table, but not in the form.
Ok... I mean that the element with the parent ID is missing! Therefore I still see my "lost" elements in the SQL, but no longer in the form.
I've now laboriously restored most things manually from the SQL table. It worked so far. Finally, I wanted to adjust the fill colors in an SVG, switched to RGB and used Quich Save a few times. Now I'm getting the error again that the form isn't saved. I'm fed up... Maybe tomorrow. I'm not even going to look at what data I'm missing now...
Please take a copy of the large form, then add more fields to the copy, then quick save, does it save or error ?
I need you to test on the error point if "Save" works while "Quick save" does not or both do not work ?
Hi rbock
A new setting in v8.0.34 should overcome the limit on fields, you need to enable it first under the Chronoforms Settings page, it's called "Increase max fields",
but make sure to have a backup of your forms before saving them with the new setting enabled, just in case something gets broken, I tested some forms here and it works fine but maybe I missed something, this is still considered experimental
