44
78
Events
fixed issues with unintentional value changes when using the built-in form
This fixes issues with unintentional value changes when using the built-in form to manage settings.
When a new setting is added between rendering and submitting the form, values might be wrongly assigned to other settings. This happens because the settings used to be added as a collection whose fields are usually ordered by the settings' names. Now, if a setting is added in the database, the order of fields could change (depending on the new setting's name) but the submitted values are assigned to fields corresponding to the original order.
Additionally, values of settings not submitted by the form (i.e. not present in the request) used to be effectively set to null.
To illustrate both issues:
- given settings (and values): name1 (value1), name2 (value2)
- render the form
- add new setting name11 (value11) into the database
- submit the previously rendered form unchanged
- persisted settings: name1 (value1), name11 (value2), name2 (null)
Now with these fixes, the last step would correctly be:
- persisted settings: name1 (value1), name11 (value11), name2 (value2)
In order to fix these issues, form field names are now name-based (instead of previously index-based). Thus, form or template customizations need to be revised to reflect these changes.
fixed issues with unintentional value changes when using the built-in form
updated copyright year range
dropped support for Symfony 5.3, 6.0, 6.1
removed outdated information from the README file
migrated from Travis CI to GitHub Actions
dropped support for Symfony 5.3, 6.0, 6.1
removed outdated information from the README file
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
fixes issues with unintentional value changes when using the built-in form to manage settings
fixes issues with unintentional value changes when using the built-in form to manage settings
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
removed outdated information from the README file
migrated from Travis CI to GitHub Actions
dropped support for Symfony 5.3, 6.0, 6.1
migrated from Travis CI to GitHub Actions
dropped support for Symfony 5.3, 6.0, 6.1
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
migrated from Travis CI to GitHub Actions
