Project

General

Profile

Actions

Bug #88513

closed

Non-FQCN controllers should still be usable in Extbase

Added by Oliver Hader almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Start date:
2019-06-06
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

(1/1) #1316104317 TYPO3\CMS\Extbase\Mvc\Exception
The default controller for extension "News" and plugin "Pi1" can not be determined.
Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php.

configured as

    \TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
        'GeorgRinger.News',
        'Pi1',
        [
            'News' => 'list,detail,selectedList,dateMenu,searchForm,searchResult',
            'Category' => 'list',
            'Tag' => 'list',
        ],
        [
            'News' => 'searchForm,searchResult',
        ]
    );

Which does not seem to be possible anymore since https://review.typo3.org/c/Packages/TYPO3.CMS/+/59566

Since the referenced issue is about "deprecation", it should provide a backward compatibility path without forcing users to upgrade. Otherwise it would be a "breaking" change.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #87550: Use controller classes when registering plugins/modulesClosedAlexander Schnitzler2019-01-25

Actions
Actions

Also available in: Atom PDF