I suppose that cc6 and cf6 lack atomicity when saving because I lost part of my work at least 2 or 3 times.
This is what happened:
- I make some modification on a cc connection
- I Apply or Save
- the network connection (wifi) stops working or it wasn't working when I pressed the button
- I reload the page or save again (I'm not sure, it's difficult to replicate the same conditions)
Now something could be lost in the connection. It can be a function or more than one, it could be views or events. If you do not notice the problem at once and the missing elements are not breaking the cc connection, a long time can go by.
Is it possible to add some kind of transaction mechanism when saving, so that something is saved entirely or it's not saved at all?
I saved and after waiting at least 2 or 3 minutes the hourglass was still turning.
I reopened that connection after restarting my pc and most of the content is missing. There's the list of events but no views, non functions. :-(
Some hours before I had made a phpmyadmin backup. I tried to restore the record of that connection to no avail. When I open the connection there are events, locales but views are missing, functions are missing and activating joomla error reporting the following error is displayed instead of the list of functions:
Warning: Invalid argument supplied for foreach() in /home/.../public_html/libraries/cegcore2/admin/extensions/chronofc/themes/default/views/list-item.php on line 5
Apart from my suggestion in my 1st post (make saving an atomic transaction), why restoring the record from a mysql backup is not working? What should I do to restore that record?
The Forms Manager pages create very large forms with many hundreds, sometimes thousands of form inputs to be saved. The most common causes of forms not saving are that the site has a max_input_vars() setting for PHP that is not large enough, or that the processor timeout does not allow enough time for the form data to be saved and processed.
If you temporarily set Site Admin > Error Reporting to Maximum you will hopefully see a more useful error message.
Bob
ChronoForms technical support If you'd like to buy me a coffee or two, thank you very much
The saving problems are not connected to max_input_vars or execution time. That same connection was saved without problem minutes before the last fatal save operation. After restoring from the mysql backup I set Error Reporting to Maximum and what I get when I load the connection is in my previous post. I don't undestand how is it possible that restoring a record from a file makes the connection data partially invalid. Perhaps the problem is the copy and paste of the record in the editor (I have to extract the INSERT command from a full database backup), something in the format of the command probably is messed up. I don't know. Thank you maxx
If you'd like to buy me a coffee or two, thank you very much
After restoring from the mysql backup I set Error Reporting to Maximum and what I get when I load the connection is in my previous post.
I don't undestand how is it possible that restoring a record from a file makes the connection data partially invalid.
Perhaps the problem is the copy and paste of the record in the editor (I have to extract the INSERT command from a full database backup), something in the format of the command probably is messed up. I don't know.
Thank you
maxx