Capture additional fields in JSON objects with hidden input fields for each table or tabular construct.
Currently each repeated field name is appended with a tab/row suffix in order to ensure all rows/tabs are submitted properly in the backend.
This gives rise to 2 inconvenient issues,
1- rows are added/removed in FILO order, while a number of users have requested random order, allowing for a delete button on each row and possibly an add button on each row.
2- consolidation of data in the backend while preserving the CF7 field tag integrity has been a challenge and requires complex manipulations.
Separating the initial field in each row from subsequent rows using a JSON object construct would also ease retaining the row relation of each data field values. Each table would have a single hidden input field with an encoded JSON object updated dynamically on each field change.
Submission would allow data to be handled by the plugin in a simpler way, allowing for simplified consolidation and validation process.
Tables within tabs would need to be stored with nested JSON objects.
Capture additional fields in JSON objects with hidden input fields for each table or tabular construct.
Currently each repeated field name is appended with a tab/row suffix in order to ensure all rows/tabs are submitted properly in the backend.
This gives rise to 2 inconvenient issues, 1- rows are added/removed in FILO order, while a number of users have requested random order, allowing for a delete button on each row and possibly an add button on each row. 2- consolidation of data in the backend while preserving the CF7 field tag integrity has been a challenge and requires complex manipulations.
Separating the initial field in each row from subsequent rows using a JSON object construct would also ease retaining the row relation of each data field values. Each table would have a single hidden input field with an encoded JSON object updated dynamically on each field change.
Submission would allow data to be handled by the plugin in a simpler way, allowing for simplified consolidation and validation process.
Tables within tabs would need to be stored with nested JSON objects.