Bug #73795

Bug when switching a extbase plugin with flexforms "switchableControllerActions" to a plugin without flexform

Added by Markus Hölzle over 4 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2016-03-01
Due date:
% Done:

0%

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

Description

Hi there,

I found a bug in the TYPO3 core:
Way to reproduce the error
  1. Insert a extbase plugin, the news plugin for example, which uses the flexforms "switchableControllerActions" and save the record
  2. Switch the value in the TYPO3 Backend "Selected plugin" to a extbase plugin without a flexform

No you will see an error message.

#1316104317: The default controller for extension "YourExtensionName" and plugin "YourPluginName" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php

The reason is, that the function "\TYPO3\CMS\Extbase\Configuration\FrontendConfigurationManager::getContextSpecificFrameworkConfiguration" will always call the method "overrideConfigurationFromFlexForm".

The clean way to solve this issue will be remove all context from the database field "tt_content.pi_flexform" if you change the value of the field "tt_content.list_type".

What do you think about this solution?


Related issues

Related to TYPO3 Core - Bug #73630: flexform data is not deleted when changing pluginAccepted2016-02-23

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

Actions
#1

Updated by Susanne Moog almost 3 years ago

  • Category set to Extbase
#2

Updated by Christian Eßl 9 months ago

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

Also available in: Atom PDF