Token导航 LogoToken导航

Agent Skill · 研究检索

typo3-update(错别字 3 更新)

typo3-update 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

typo3-update 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 39,790。

总安装 1,364周安装 58GitHub Stars 26下载 478核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:typo3-update(错别字 3 更新)
来源仓库:https://github.com/dirnbauer/webconsulting-skills
仓库路径:skills/typo3-update
安装命令:
npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-update
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-update

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

typo3-update 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。当前无原始 SKILL.md 内容可参考,功能描述基于通用检索场景推断。

来源仓库内路径:skills/typo3-update

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-u…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

typo3-update 怎么安装?

在终端执行 npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-update。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

typo3-update 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

typo3-update 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

typo3-update 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

typo3-update 用的人多吗?

公开数据是累计安装 1,364 次,近一周安装 58 次,下载 478 次,GitHub 26 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

typo3-update 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
typo3-update

错别字 3 更新 · 本页

1,36426需要联网MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

TYPO3 v14 development

Strategy: This collection targets TYPO3 v14.x only. Patterns here assume a v14 codebase. For migrating from older majors, use typo3-rector, typo3-extension-upgrade, Fractor, and the official upgrade guide first.
TYPO3 API First: Always use TYPO3's built-in APIs, core features, and established conventions before creating custom implementations. Do not reinvent what TYPO3 already provides. Always verify that the APIs and methods you use exist and are not deprecated in TYPO3 v14 by checking the official TYPO3 documentation.

1. Version Strategy

Target: TYPO3 v14.x only

VersionRole for this collection
v14.xSupported target — examples and constraints assume TYPO3 v14
Older majorsNot targeted — complete a core upgrade, then use these patterns

Best Practice: Declare TYPO3 v14-only constraints in composer.json and ext_emconf.php for new work.

Version Constraints

<?php
// ext_emconf.php — TYPO3 v14
$EM_CONF[$_EXTKEY] = [
    'title' => 'My Extension',
    'version' => '2.0.0',
    'state' => 'stable',
    'constraints' => [
        'depends' => [
            'typo3' => '14.0.0-14.99.99',
            'php' => '8.2.0-8.5.99',
        ],
        'conflicts' => [],
        'suggests' => [],
    ],
];
// composer.json — TYPO3 v14
{
    "name": "vendor/my-extension",
    "type": "typo3-cms-extension",
    "require": {
        "php": "^8.2",
        "typo3/cms-core": "^14.0"
    },
    "extra": {
        "typo3/cms": {
            "extension-key": "my_extension"
        }
    }
}
Content Blocks: friendsoftypo3/content-blocks may require typo3/cms-core ^14.1 or higher — match the Packagist constraint before pinning ^14.0 only.

2. PHP Requirements

Minimum PHP Version: 8.2

TYPO3 v14 requires PHP 8.2+. Use modern PHP features:

<?php
declare(strict_types=1);

namespace Vendor\Extension\Service;

// ✅ Constructor property promotion (PHP 8.0+)
final class MyService
{
    public function __construct(
        private readonly SomeDependency $dependency,
        private readonly AnotherService $anotherService,
    ) {}
}

// ✅ Named arguments (PHP 8.0+)
$result = $this->doSomething(
    name: 'value',
    options: ['key' => 'value'],
);

// ✅ Match expressions (PHP 8.0+)
$type = match ($input) {
    'a' => 'Type A',
    'b' => 'Type B',
    default => 'Unknown',
};

// ✅ Enums (PHP 8.1+)
enum Status: string
{
    case Draft = 'draft';
    case Published = 'published';
}

3. Controller Patterns (TYPO3 v14)

Extbase Action Controller

<?php
declare(strict_types=1);

namespace Vendor\Extension\Controller;

use Psr\Http\Message\ResponseInterface;
use TYPO3\CMS\Extbase\Mvc\Controller\ActionController;
use Vendor\Extension\Domain\Repository\ItemRepository;

final class ItemController extends ActionController
{
    public function __construct(
        private readonly ItemRepository $itemRepository,
    ) {}

    // ✅ Must return ResponseInterface (required in TYPO3 v14)
    public function listAction(): ResponseInterface
    {
        $items = $this->itemRepository->findAll();
        $this->view->assign('items', $items);
        return $this->htmlResponse();
    }

    public function showAction(int $item): ResponseInterface
    {
        $item = $this->itemRepository->findByUid($item);
        $this->view->assign('item', $item);
        return $this->htmlResponse();
    }

    // ✅ JSON response
    public function apiAction(): ResponseInterface
    {
        $data = ['success' => true, 'items' => []];
        return $this->jsonResponse(json_encode($data));
    }

    // ✅ Redirect
    public function createAction(): ResponseInterface
    {
        // Process creation...
        $this->addFlashMessage('Item created');
        return $this->redirect('list');
    }
}

Backend Module Controller

<?php
declare(strict_types=1);

namespace Vendor\Extension\Controller;

use Psr\Http\Message\ResponseInterface;
use Psr\Http\Message\ServerRequestInterface;
use TYPO3\CMS\Backend\Attribute\AsController;
use TYPO3\CMS\Backend\Template\ModuleTemplateFactory;

#[AsController]
final class BackendModuleController
{
    public function __construct(
        private readonly ModuleTemplateFactory $moduleTemplateFactory,
    ) {}

    public function indexAction(ServerRequestInterface $request): ResponseInterface
    {
        $moduleTemplate = $this->moduleTemplateFactory->create($request);
        $moduleTemplate->assign('items', []);

        return $moduleTemplate->renderResponse('Backend/Index');
    }
}

4. View & Templating (TYPO3 v14)

ViewFactory (Preferred Pattern)

<?php
declare(strict_types=1);

namespace Vendor\Extension\Service;

use Psr\Http\Message\ServerRequestInterface;
use TYPO3\CMS\Core\View\ViewFactoryData;
use TYPO3\CMS\Core\View\ViewFactoryInterface;

final class RenderingService
{
    public function __construct(
        private readonly ViewFactoryInterface $viewFactory,
    ) {}

    public function renderEmail(ServerRequestInterface $request, array $data): string
    {
        $viewFactoryData = new ViewFactoryData(
            templateRootPaths: ['EXT:my_extension/Resources/Private/Templates/Email'],
            partialRootPaths: ['EXT:my_extension/Resources/Private/Partials'],
            layoutRootPaths: ['EXT:my_extension/Resources/Private/Layouts'],
            request: $request,
        );

        $view = $this->viewFactory->create($viewFactoryData);
        $view->assignMultiple($data);

        return $view->render('Notification');
    }
}

Fluid Template Best Practices

<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers"
      xmlns:core="http://typo3.org/ns/TYPO3/CMS/Core/ViewHelpers"
      data-namespace-typo3-fluid="true">

<f:layout name="Default" />

<f:section name="Main">
    <div class="content">
        <!-- ✅ Auto-escaped output -->
        <h1>{item.title}</h1>

        <!-- ✅ Explicit HTML (use with caution) -->
        <f:format.html>{item.bodytext}</f:format.html>

        <!-- ✅ Conditional rendering -->
        <f:if condition="{items}">
            <f:then>
                <f:for each="{items}" as="item">
                    <f:render partial="Item" arguments="{item: item}" />
                </f:for>
            </f:then>
            <f:else>
                <p>No items found.</p>
            </f:else>
        </f:if>

        <!-- ✅ Link building -->
        <f:link.action action="show" arguments="{item: item.uid}">
            View Details
        </f:link.action>
    </div>
</f:section>

</html>

5. Event System (TYPO3 v14)

PSR-14 Event Listeners

PSR-14 events are the standard in TYPO3 v14. Always prefer events over hooks.

<?php
declare(strict_types=1);

namespace Vendor\Extension\EventListener;

use TYPO3\CMS\Core\Attribute\AsEventListener;
use TYPO3\CMS\Frontend\Event\ModifyCacheLifetimeForPageEvent;

#[AsEventListener(identifier: 'vendor-extension/modify-cache-lifetime')]
final class ModifyCacheLifetimeListener
{
    public function __invoke(ModifyCacheLifetimeForPageEvent $event): void
    {
        // Reduce cache lifetime for certain pages
        if ($event->getPageId() === 123) {
            $event->setCacheLifetime(300); // 5 minutes
        }
    }
}

Common Events (TYPO3 v14)

EventPurpose
ModifyPageLinkConfigurationEventModify link building
ModifyCacheLifetimeForPageEventAdjust page cache
BeforeStdWrapFunctionsInitializedEventModify stdWrap
*(DataHandler)*Core ships no generic BeforeRecordOperationEvent / AfterRecordOperationEvent; use SC_OPTIONS DataHandler hooks or documented TYPO3\CMS\Core\DataHandling\Event\* only (list)

Services.yaml Registration

# Configuration/Services.yaml
services:
  _defaults:
    autowire: true
    autoconfigure: true
    public: false

  Vendor\Extension\:
    resource: '../Classes/*'
    exclude:
      - '../Classes/Domain/Model/*'

  # Event listener (alternative to #[AsEventListener] attribute)
  Vendor\Extension\EventListener\MyListener:
    tags:
      - name: event.listener
        identifier: 'vendor-extension/my-listener'

6. Backend Module Registration (TYPO3 v14)

Configuration/Backend/Modules.php

<?php
// Configuration/Backend/Modules.php
return [
    'web_myextension' => [
        'parent' => 'content',
        'position' => ['after' => 'records'],
        'access' => 'user,group',
        'iconIdentifier' => 'myextension-module',
        'path' => '/module/content/myextension',
        'labels' => 'LLL:EXT:my_extension/Resources/Private/Language/locallang_mod.xlf',
        'extensionName' => 'MyExtension',
        'controllerActions' => [
            \Vendor\MyExtension\Controller\BackendController::class => [
                'index',
                'list',
                'show',
            ],
        ],
    ],
];

Icon Registration

<?php
// Configuration/Icons.php
return [
    'myextension-module' => [
        'provider' => \TYPO3\CMS\Core\Imaging\IconProvider\SvgIconProvider::class,
        'source' => 'EXT:my_extension/Resources/Public/Icons/module.svg',
    ],
];

7. TCA Configuration (TYPO3 v14)

Static TCA Only

In v14, runtime TCA modifications are forbidden. Always use static files:

<?php
// Configuration/TCA/tx_myext_domain_model_item.php
return [
    'ctrl' => [
        'title' => 'LLL:EXT:my_extension/Resources/Private/Language/locallang_db.xlf:tx_myext_domain_model_item',
        'label' => 'title',
        'tstamp' => 'tstamp',
        'crdate' => 'crdate',
        'delete' => 'deleted',
        'enablecolumns' => [
            'disabled' => 'hidden',
            'starttime' => 'starttime',
            'endtime' => 'endtime',
        ],
        // v14: ctrl `searchFields` removed (Breaking #106972) — mark searchable columns in `columns` instead.
        'iconIdentifier' => 'myextension-item',
    ],
    'palettes' => [
        'visibility' => [
            'showitem' => 'hidden',
        ],
        'access' => [
            'showitem' => 'starttime, endtime',
        ],
    ],
    'types' => [
        '1' => [
            'showitem' => '
                --div--;LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:general,
                    title, description,
                --div--;LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:access,
                    --palette--;;visibility,
                    --palette--;;access,
            ',
        ],
    ],
    'columns' => [
        'title' => [
            'label' => 'LLL:EXT:my_extension/Resources/Private/Language/locallang_db.xlf:tx_myext_domain_model_item.title',
            'config' => [
                'type' => 'input',
                'size' => 50,
                'max' => 255,
                'required' => true,
                'searchable' => true,
            ],
        ],
        'description' => [
            'label' => 'LLL:EXT:my_extension/Resources/Private/Language/locallang_db.xlf:tx_myext_domain_model_item.description',
            'config' => [
                'type' => 'text',
                'cols' => 40,
                'rows' => 5,
                'enableRichtext' => true,
                'searchable' => true,
            ],
        ],
    ],
];

Auto-Created Columns from ctrl

Since TYPO3 v13.3+, column definitions for fields referenced in ctrl are auto-created by the Core. You no longer need explicit 'columns' entries for:

  • enablecolumns fields: hidden/disabled, starttime, endtime, fe_group
  • Language fields: sys_language_uid, l10n_parent, l10n_diffsource
  • editlock, description (if set as descriptionColumn)

Convention fields don't need ext_tables.sql -- all fields referenced by ctrl properties (deleted, hidden, starttime, endtime, fe_group, sorting, tstamp, crdate, sys_language_uid, l10n_parent, l10n_diffsource) are added to the database automatically. Defining them in ext_tables.sql may cause problems.

Fields that never need columns definitions:

  • deleted -- handled by DataHandler, not shown in forms
  • tstamp, crdate, t3_origuid -- managed by DataHandler, never displayed
  • sorting -- managed by DataHandler, should NOT be in columns

Still required:

  • The ctrl properties themselves (tstamp, crdate, delete, enablecolumns, etc.)
  • References in showitem / palettes (auto-created columns must still be added to types manually)
  • Use dedicated palettes: visibility for hidden, access for starttime, endtime
  • Your own custom column definitions

Override auto-created columns in Configuration/TCA/Overrides/ if needed:

<?php
// Configuration/TCA/Overrides/pages.php
// New pages are disabled by default
$GLOBALS['TCA']['pages']['columns']['disabled']['config']['default'] = 1;
Important: Auto-creation only works for ctrl properties in base Configuration/TCA/ files, NOT in Configuration/TCA/Overrides/. See: Common fields | Auto-created columns

TCA Overrides

<?php
// Configuration/TCA/Overrides/tt_content.php
defined('TYPO3') or die();

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTcaSelectItem(
    'tt_content',
    'CType',
    [
        'label' => 'LLL:EXT:my_extension/Resources/Private/Language/locallang.xlf:ctype.title',
        'value' => 'myextension_element',
        'icon' => 'content-text',
        'group' => 'default',
    ]
);

$GLOBALS['TCA']['tt_content']['types']['myextension_element'] = [
    'showitem' => '
        --div--;LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:general,
            --palette--;;general,
            header,
            bodytext,
        --div--;LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:access,
            --palette--;;hidden,
    ',
];

8. Database Operations (TYPO3 v14)

QueryBuilder

<?php
declare(strict_types=1);

namespace Vendor\Extension\Repository;

use TYPO3\CMS\Core\Database\Connection;
use TYPO3\CMS\Core\Database\ConnectionPool;
use TYPO3\CMS\Core\Database\Query\QueryBuilder;

final class CustomRepository
{
    public function __construct(
        private readonly ConnectionPool $connectionPool,
    ) {}

    public function findByStatus(string $status): array
    {
        $queryBuilder = $this->connectionPool->getQueryBuilderForTable('tx_myext_items');

        return $queryBuilder
            ->select('*')
            ->from('tx_myext_items')
            ->where(
                $queryBuilder->expr()->eq(
                    'status',
                    $queryBuilder->createNamedParameter($status)
                )
            )
            ->orderBy('title', 'ASC')
            ->executeQuery()
            ->fetchAllAssociative();
    }

    public function countByPid(int $pid): int
    {
        $queryBuilder = $this->connectionPool->getQueryBuilderForTable('tx_myext_items');

        return (int)$queryBuilder
            ->count('uid')
            ->from('tx_myext_items')
            ->where(
                $queryBuilder->expr()->eq(
                    'pid',
                    $queryBuilder->createNamedParameter($pid, Connection::PARAM_INT)
                )
            )
            ->executeQuery()
            ->fetchOne();
    }
}

Extbase Repository

<?php
declare(strict_types=1);

namespace Vendor\Extension\Domain\Repository;

use TYPO3\CMS\Extbase\Persistence\QueryInterface;
use TYPO3\CMS\Extbase\Persistence\Repository;

final class ItemRepository extends Repository
{
    protected $defaultOrderings = [
        'sorting' => QueryInterface::ORDER_ASCENDING,
    ];

    public function findPublished(): array
    {
        $query = $this->createQuery();
        $query->matching(
            $query->logicalAnd(
                $query->equals('hidden', false),
                $query->lessThanOrEqual('starttime', time()),
                $query->logicalOr(
                    $query->equals('endtime', 0),
                    $query->greaterThan('endtime', time())
                )
            )
        );

        return $query->execute()->toArray();
    }
}

9. CLI Commands (TYPO3 v14)

<?php
declare(strict_types=1);

namespace Vendor\Extension\Command;

use Symfony\Component\Console\Attribute\AsCommand;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputArgument;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Input\InputOption;
use Symfony\Component\Console\Output\OutputInterface;
use Symfony\Component\Console\Style\SymfonyStyle;
use TYPO3\CMS\Core\Core\Bootstrap;

#[AsCommand(
    name: 'myext:process',
    description: 'Process items in the extension',
)]
final class ProcessCommand extends Command
{
    protected function configure(): void
    {
        $this
            ->addArgument('type', InputArgument::REQUIRED, 'The type to process')
            ->addOption('force', 'f', InputOption::VALUE_NONE, 'Force processing');
    }

    protected function execute(InputInterface $input, OutputInterface $output): int
    {
        $io = new SymfonyStyle($input, $output);

        // Initialize backend for DataHandler operations
        Bootstrap::initializeBackendAuthentication();

        $type = $input->getArgument('type');
        $force = $input->getOption('force');

        $io->title('Processing: ' . $type);

        // Your logic here...

        $io->success('Processing completed successfully');

        return Command::SUCCESS;
    }
}

Command Registration

With autoconfigure: true in Services.yaml defaults, #[AsCommand] is enough — you do not need the console.command tag unless autoconfigure is disabled for that service.

# Optional — only when not using #[AsCommand] + autoconfigure
services:
  Vendor\Extension\Command\ProcessCommand:
    tags:
      - name: console.command

10. Testing

PHPUnit Setup

<!-- phpunit.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:noNamespaceSchemaLocation="vendor/phpunit/phpunit/phpunit.xsd"
         bootstrap="vendor/typo3/testing-framework/Resources/Core/Build/UnitTestsBootstrap.php"
         colors="true">
    <testsuites>
        <testsuite name="Unit">
            <directory>Tests/Unit</directory>
        </testsuite>
        <testsuite name="Functional">
            <directory>Tests/Functional</directory>
        </testsuite>
    </testsuites>
</phpunit>

CI matrix (TYPO3 v14)

# .github/workflows/ci.yaml
name: CI

on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        typo3: ['^14.0']
        php: ['8.2', '8.3', '8.4']

    steps:
      - uses: actions/checkout@v4

      - name: Setup PHP
        uses: shivammathur/setup-php@v2
        with:
          php-version: ${{ matrix.php }}
          extensions: intl, pdo_mysql

      - name: Install dependencies
        run: |
          composer require typo3/cms-core:${{ matrix.typo3 }} --no-update
          composer install --prefer-dist --no-progress

      - name: Run tests
        run: vendor/bin/phpunit

11. Upgrade Process

From older majors to v14

# 1. Create backup
ddev snapshot --name=before-upgrade

# 2. Update composer constraints
ddev composer require "typo3/cms-core:^14.0" --no-update
ddev composer update "typo3/*" --with-all-dependencies

# 3. Run upgrade wizards
ddev typo3 upgrade:list
ddev typo3 upgrade:run

# 4. Clear caches
ddev typo3 cache:flush

# 5. Register extensions and align database schema
ddev typo3 extension:setup
# Schema compare/apply (CLI entry point depends on your project: `typo3`, `vendor/bin/typo3`, typo3-console, etc.)
# `database:updateschema` is from **helhum/typo3-console**, not plain Core — omit if you only have `vendor/bin/typo3`.
ddev typo3 database:updateschema

# 6. Test thoroughly

12. Resources

13. v14-Only Changes (Manual — Not Handled by Rector)

The following changes apply exclusively to TYPO3 v14 and require manual migration. They are NOT fully covered by ssch/typo3-rector (check your installed version; the TYPO3 14 rule set counts tens of rules and changes between releases). For automated migrations, run Typo3LevelSetList::UP_TO_TYPO3_14 first, then address these manually.

Fluid 5.0 Template Changes [v14 only]

Rector handles PHP-side ViewHelper declarations (UseStrictTypesInFluidViewHelpersRector), but Fluid template changes require manual review:

  • ViewHelper arguments in .html templates must match strict types (e.g., tabindex must be int, not string).
  • Fluid variable names with underscore prefix (_myVar) are disallowed — rename in all templates.
  • CDATA sections in Fluid templates are no longer removed automatically.
  • Use {variable as type} casting for ambiguous ViewHelper arguments.

TypoScriptFrontendController Removed [v14 only]

Not covered by Rector — context-dependent migration requiring manual analysis:

  • $GLOBALS['TSFE'] and TypoScriptFrontendController are fully removed.
  • Each usage needs different request attribute replacements: // ❌ Removed in v14 $tsfe = $GLOBALS['TSFE']; // ✅ TYPO3 v14 pattern $pageInformation = $request->getAttribute('frontend.page.information'); $language = $request->getAttribute('language'); $typoscript = $request->getAttribute('frontend.typoscript');

Backend Module Renaming [v14 only]

Not a PHP migration — requires manual update to Configuration/Backend/Modules.php:

Old ParentNew Parent
webcontent
filemedia
toolsadmin or system (Core split tools into multiple parents — map each module to its new parent in Configuration/Backend/Modules.php)

Runtime TCA Modifications Forbidden [v14 only]

$GLOBALS['TCA'] is read-only after boot in TYPO3 v14 — stricter than older majors. Static TCA under Configuration/TCA/ has been the supported approach since v12; extensions still mutating TCA from ext_tables.php, middleware, or event listeners must be refactored (architectural change, not a one-line replace).

Plugin Subtypes Removed [v14 only]

  • switchableControllerActions: deprecated in TYPO3 v10.3 (#89463) and removed later — not a v14-only topic, but legacy FlexForm/plugins may still reference it until you split plugins.
  • list_type subtypes / plugin list types: further tightened in v14 (#105538) — each variant needs its own configurePlugin() / registration and TypoScript/FlexForm split.

EXT:form Hooks → PSR-14 Events [v14 only]

Hook-to-event migration requires manual rewrite of hook implementations:

  • EXT:form hooks removed across multiple breaking changes (e.g., #107566 for afterInitializeCurrentPage, #107518, #107528, #107568, #107569, #107343, #107380, #107382, #107388, #98239): beforeRendering, afterSubmit, initializeFormElement, beforeFormSave, beforeFormDelete, beforeFormDuplicate, beforeFormCreate, afterBuildingFinished, beforeRemoveFromParentRenderable, afterInitializeCurrentPage.
  • Replace with corresponding PSR-14 events (e.g., BeforeFormIsSavedEvent, BeforeRenderableIsRenderedEvent).

Frontend Asset Pipeline [v14 only]

Rector removes PHP configuration (RemoveConcatenateAndCompressHandlerRector), but the infrastructure replacement is manual:

  • CSS/JS concatenation and compression removed from TYPO3 Core entirely.
  • Must configure web server compression (nginx gzip, Apache mod_deflate) or use build tools (Vite, webpack).
  • TypoScript config.concatenateCss, config.compressCss, config.concatenateJs, config.compressJs must be removed (handled by Fractor, not Rector).

New TCA Features [v14 only]

New features to adopt (not migrations):

  • New TCA type country (#99911) for country selection fields.
  • New itemsProcessors option (#107889) for dynamic item generation.
  • Type-specific title (and previewRenderer) in TCA types — Feature #108027 (not “arbitrary ctrl copies” per type — see changelog).
  • Type-specific TCA defaults (#107281).

New Fluid ViewHelpers [v14 only]

  • <f:page.meta> — set page meta tags from Fluid templates.
  • <f:page.title> — set page title from Fluid templates.
  • <f:page.headerData> / <f:page.footerData> — inject raw HTML into head/footer (Feature #107056).

Localization System [v14 only]

Rector handles parser class replacement (ReplaceLocalizationParsersWithLoaders) and label syntax (MigrateLabelReferenceToDomainSyntaxRector), but these features are new:

  • XLIFF 2.x translation files supported alongside XLIFF 1.2.
  • Translation domain mapping (#93334) for flexible XLIFF file resolution.

New DataHandler Features [v14 only]

  • discard command (#107519) — discard workspace changes programmatically.
  • ISO8601 date handling improved — qualified and unqualified ISO8601 dates supported.

v14.1 Features [v14.1+ only]

Verify each item in the official v14.1 changelog for your minor (entries change over time). Examples that have appeared in v14.1 discussions include default theme “Camino”, per-column content restrictions, Fluid Components tuning, and PHP 8.5 support — confirm before documenting them for a specific project.

v14.2 Features [v14.2+ only]

  • Backend search by frontend URL — find pages by their frontend URL in page tree and live search.
  • Workspace selector moved to sidebar with color and description.
  • Extbase identity map language-aware — identity map now considers language when resolving objects.
  • XLIFF xml:space attribute — whitespace handling respects the attribute.
  • QR Code for frontend preview — downloadable QR codes (PNG/SVG) for frontend URLs.

New v14 Deprecations (removed in v15) — Not Yet Handled by Rector

v14.0 (examples):

  • ExtensionManagementUtility::addPiFlexFormValue() (#107047) — use direct FlexForm TCA.

v14.2+ examples:

  • ExtensionManagementUtility::addFieldsToUserSettings (#108843) — use TCA for user settings.
  • PageRenderer->addInlineLanguageDomain() (#108963).
  • FormEngine "additionalHiddenFields" key (#109102).

Credits & Attribution

Source: https://github.com/dirnbauer/webconsulting-skills

平台分布

Claude Code

26.62%
按下载量换算127

OpenCode

20.6%
按下载量换算98

Gemini CLI

19.04%
按下载量换算91

windsurf

13.51%
按下载量换算65

Cursor

7.22%
按下载量换算35

Codex

3.39%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills