Parent and child field values not being stored in database
-
Possible bug report:
In a registration form, I have a hidden parent field (dynamically populated) and a child field that is dynamically populated based on the value of the parent field.
When the user clicks submit, all form field values are submitted / sent to the server. However, the parent and child field values are not stored in the database.
If I check the value of $submitted at the um_before_save_registration_details hook, these two values (and array keys) are missing. However, if I check the value of $form_data[‘submitted’] at the um_registration_complete hook, the parent and child values are present.
I’m currently using this latter hook as a workaround to manually save those two values to the database since they aren’t being saved during the normal form submission process.
I can’t think of why this would be and it seems to only complicate the issue, but the problem has been intermittent in the past, and with the recent release of 2.0.46, the problem is consistent with each form submission.
The workaround I’m using is okay enough for now, but it does break the notification emails, because those two fields are missing in the report of submitted data. Perhaps I’m missing something about these types of fields, but I suspect this is a bug.
I appreciate any help or fix for this!
- The topic ‘Parent and child field values not being stored in database’ is closed to new replies.