Great module, by the way.
Issue is that two of the webforms saves some fields, but not the first 5 components that are text area. I've looked in the database and not found any data difference in the webform_webform_submitted_data table.
Within the component descriptions and submitted data, I've checked for single quotes, double quotes, etc. based upon past components.
I haven't changed code in this module, nor use code in validation, etc. Pretty straight forward on thes e forms.
This webform module was upgraded from 5.x-1.
Here is the debug information cut down to my own observations. The submitted_tree has the values, but not the submitted arrays for form or post.
$form_values are:
Array
(
/*deleted for brevity*/
[submitted] => Array
(
[6] => care
/*deleted for brevity*/
[submitted_tree] => Array
(
[1a] => answer to component 2
[1b] => answer to component 3
[1d] => answer to component 5
[1c] => answer to component 4
[1e] => care
/*not included for brevity*/
$_POST is:
Array
(
[submitted] => Array
(
[1e] => care
/*not included for brevity*/
)
Submission updated.
Spending huge hours on this but not getting anywhere. Any insights? Want more of my testing or debug info?
Comments
Comment #1
quicksketchThere was a pretty serious bug with numeric form_keys in the 5.1.3 version, where forms that used numeric keys would loose information when submitted (very similar to what you're describing here). Could you try the 2.2 version and see if that fixes things?
See #306009: Data lost with numeric form keys
Comment #2
bboothby commentedYep, the upgrade to 5.x-2.2 fixed the problem even though the field names weren't numerical just starting with a number. This upgrade also fixed a download problem where some fields were blank.
The website is live, but with backups, I went ahead with the upgrade. I haven't had time to setup the development site yet. I'm glad I did this upgrade.
I really did spend hours searching for data loss when saving webform and partial save didn't come up with the issue mentioned. Hopefully this will help others.
Thanks,
-Brad
Comment #3
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.