#73630flexform data is not deleted when changing plugin
Description
Changing the selected plugin in a content element, where the former plugin had a flexform configuration, but the new plugin does not have one must remove the existing configuration, otherwise the old configuration is still applied to the new plugin.
Another option would be to simply ignore the existing flexform data if the current plugin does not require them.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[BUGFIX] flexform data is not deleted when changing plugin Resolves: #73630 Releases: main
Related issues 9
- Bug #20493flexform ds remains even if the plugin changes
- Bug #71569FrontendConfigurationManager::overrideSwitchableControllerActionsFromFlexForm does not check if plugin has flexform
- Bug #73795Bug when switching a extbase plugin with flexforms "switchableControllerActions" to a plugin without flexform
- Feature #76925Switching from one content type to another should clear fields not usable anymore
- Bug #87617Change of flexform definition leads to duplicate data
- Epic #88528Remove switchable controller action functionality
- Feature #88908Add "migration wizard" when changing CType of content elements
- Bug #94039Change of the tt_content plugin can lead to corrupted FlexForm
- Task #97002Simplify flexform behavior and stop saving old settings in flexforms (+ get rid of the then no more necessary flexform cli command + scheduler task)