webform_submission_log is able to log information about a submission post-save. However, webform does not provide the form submission data, which limits what can be done with the log information. One can only know who did what when on which submission, but cannot really know what actually changed on the submission.
1. Enable webform and webform_submission_log.
2. Create a form and enable logging.
3. Create submissions on that form.
4. View /admin/structure/webform/submissions/log
5. Look at webform_submission_log table in the DB.
On Step 4, you can see that the submissions created in Step 3 are logged.
On Step 5, the data column of those rows are empty.
- Allow \Drupal\webform\WebformSubmissionStorage::doPostSave() to pass the saved form's data into the log context so that loggers like webform_submission_log can operate on that data. In webform_submission_log's case, it will store it in the data column of the webform_submission_log table.
- Goal of this ticket is to get the data in there. Rendering the log lines, especially in a pretty way, is out of scope.
- Patch
- Review
- Merge
None
None
Form data is serialized into the data column of webform_submission_log upon submission creation or update.
Closed: won't fix
6.1
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This feature should be handled via custom code or dedicated contrib module.
Looks like there is no hooks or eventDispatcher to change the data write into the table: webform_submission_log.
So what's the best practise? using hook_entity_CRUD?
In my scenario, I want to log the info like this:
{FIELD1} change FROM {A} to {B}
{FIELD2} change FROM {1} to {2}
Any advice will be appreciated