Typo3 无法确定扩展和插件的默认控制器
下午好,亲爱的朋友们!好吧,我放弃。尝试得很好,这一切都是可能的。类型3 7.6.16 ext_tables.php:Typo3 无法确定扩展和插件的默认控制器,typo3,extbase,typo3-7.6.x,Typo3,Extbase,Typo3 7.6.x,下午好,亲爱的朋友们!好吧,我放弃。尝试得很好,这一切都是可能的。类型3 7.6.16 ext_tables.php: <?php if (!defined('TYPO3_MODE')) die ('Access denied.'); \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin( 'MyVendor.' . $_EXTKEY, 'Pi1', 'The inventory list' );
<?php
if (!defined('TYPO3_MODE')) die ('Access denied.');
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
'MyVendor.' . $_EXTKEY,
'Pi1',
'The inventory list'
);
<?php
defined('TYPO3_MODE') || die('Access denied.');
call_user_func(
function($extKey)
{
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
'VENDOR.Extensionkey',
'Pi1',
'Extension Display Name'
);
},
$_EXTKEY
);
首先,对这两个文件使用正确的语法。示例:
ext_tables.php:
<?php
if (!defined('TYPO3_MODE')) die ('Access denied.');
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
'MyVendor.' . $_EXTKEY,
'Pi1',
'The inventory list'
);
<?php
defined('TYPO3_MODE') || die('Access denied.');
call_user_func(
function($extKey)
{
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
'VENDOR.Extensionkey',
'Pi1',
'Extension Display Name'
);
},
$_EXTKEY
);
清除所有缓存。有时,进入ExtensionManager并禁用/启用整个扩展会有所帮助。如果更改了类名或更改了表/localconf文件,这将刷新所有缓存。Mikael提供的解决方案目前不可用
当前处于脱机状态的外部网站的简短版本:
尝试删除并重新创建页面上的内容元素以删除旧的flexform值您的CommentController是否存在?可能是名称空间或类名中的某些键入错误?应避免使用$\u EXTKEY,因为出于好奇,正在讨论将来将其删除@KevinDitscheid:文档中声明$\u EXTKEY的用法已被弃用,但是我将来如何确定配置文件中的扩展密钥呢?因为配置文件只存在于扩展中,所以您可以简单地写出配置文件的静态名称extension@KevinDitscheid…噢!
/***
*
* This file is part of the "extensionkey" Extension for TYPO3 CMS.
*
* For the full copyright and license information, please read the
* LICENSE.txt file that was distributed with this source code.
*
* (c) 2017
*
***/
use TYPO3\CMS\Extbase\Mvc\Controller\ActionController;
/**
* FilecollectorController
*/
class FirstController extends ActionController
{
/**
* action1
*
* @return void
*/
public function action1Action()
{
}
/**
* action1
*
* @return void
*/
public function action2Action()
{
}
}