Bug #73630

flexform data is not deleted when changing plugin

Added by Markus Klein almost 5 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Must have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2016-02-23
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

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.


Related issues

Related to TYPO3 Core - Bug #20493: flexform ds remains even if the plugin changesRejected2009-05-22

Actions
Related to TYPO3 Core - Feature #76925: Switching from one content type to another should clear fields not usable anymoreNewBenni Mack2016-07-04

Actions
Related to TYPO3 Core - Bug #73795: Bug when switching a extbase plugin with flexforms "switchableControllerActions" to a plugin without flexformNew2016-03-01

Actions
Related to TYPO3 Core - Feature #88908: Add "migration wizard" when changing CType of content elementsNew2019-08-03

Actions
Related to TYPO3 Core - Bug #71569: FrontendConfigurationManager::overrideSwitchableControllerActionsFromFlexForm does not check if plugin has flexformClosed2015-11-13

Actions
Related to TYPO3 Core - Epic #88528: Remove switchable controller action functionalityIn Progress2019-06-08

Actions
Related to TYPO3 Core - Bug #87617: Change of flexform definition leads to duplicate dataNew2019-02-01

Actions
Has duplicate TYPO3 Core - Bug #77414: Changing from a flexform plugin to a non-flexform plugin does not clear the flexform settings in tt_content, maybe leading to unexpected behaviourClosed2016-08-05

Actions
#1

Updated by Christian Kuhn almost 5 years ago

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.

#2

Updated by Christian Kuhn almost 5 years ago

ah, going on already ^^

#3

Updated by Claus Due over 4 years ago

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...

#4

Updated by Sybille Peters almost 4 years ago

Claus, can you please clarify what you mean by "clean flexform data" toggle? Is there an extra configuration option?

I could not find it. What is usually recommended on removing or changing flexform data is to use the lowlevel cleaner which internally uses the function cleanFlexFormXML in FlexFormTools.

#5

Updated by Stefan P over 1 year ago

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.

#6

Updated by Stefan P over 1 year ago

  • TYPO3 Version changed from 7 to 8
#7

Updated by Markus Klein over 1 year ago

  • 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

#8

Updated by Riccardo De Contardi about 1 year ago

  • Related to Feature #88908: Add "migration wizard" when changing CType of content elements added
#9

Updated by Riccardo De Contardi about 1 year ago

  • Related to Bug #71569: FrontendConfigurationManager::overrideSwitchableControllerActionsFromFlexForm does not check if plugin has flexform added
#10

Updated by Alexander Schnitzler about 1 year ago

  • Related to Epic #88528: Remove switchable controller action functionality added
#11

Updated by Riccardo De Contardi about 1 year ago

  • Related to Bug #87617: Change of flexform definition leads to duplicate data added

Also available in: Atom PDF