Bug #73630
open
flexform data is not deleted when changing plugin
Added by Markus Klein over 8 years ago.
Updated over 5 years ago.
Category:
Backend User Interface
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.
this is a very old thing and is true for all other fields, too.
changing that behavior should imho be discussed with people like olly before.
Don't forget about the "clean flexform data" toggle which when enabled will analyse the DS and remove any data in the XML representation that is NOT also defined in the DS.
It has side effects but it is already there. I'm not sure it should become the default...
We run into this very problem every now and then. Wouldn't it be possible to just respect the flexform if it's actually defined for the plugin? If a plugin configuration has no FlexForm registered just don't parse it. It's registered if
the array keys of GLOBALS['TCA']['tt_content']['columns']['pi_flexform']['config']['ds'] contain the plugin signature and if the file actually exists. Just check for this before loading the Flexform and this ticket is solved, isn't it?
No need to clear the actual DB field content on CType/list_type change then.
- TYPO3 Version changed from 7 to 8
- Target version deleted (
Candidate for patchlevel)
- TYPO3 Version changed from 8 to 7
Resetting this to v7 since I reported it there. Of course v8 and v9 are affected too
- Related to Feature #88908: Add "migration wizard" when changing CType of content elements added
- Related to Bug #71569: FrontendConfigurationManager::overrideSwitchableControllerActionsFromFlexForm does not check if plugin has flexform added
- Related to Epic #88528: Remove switchable controller action functionality added
- Related to Bug #87617: Change of flexform definition leads to duplicate data added
- Related to Bug #94039: Change of the tt_content plugin can lead to corrupted FlexForm added
- Related to Task #97002: Simplify flexform behavior and stop saving old settings in flexforms (+ get rid of the then no more necessary flexform cli command + scheduler task) added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by