Issue Bug Resolved

#111032Importing TER extension list fails with "Data too long for column 'title'" and leaves an incomplete list behind

Sven Wappler 10/12/26, 22:03 updated 10/13/26, 08:30

Description

Problem

Since 2026-10-12 the import of the TER extension list fails on every installation that runs it (scheduler task “Update extension list”, or “Update now” in the Extension Manager):

[ERROR] An exception occurred while executing a query: Data too long for column 'title' at row 7
Exception in scheduler task #5 (TYPO3\CMS\Extensionmanager\Task\UpdateExtensionListTask - Update extension list)
File: vendor/doctrine/dbal/src/Driver/API/MySQL/ExceptionConverter.php:102

Trigger

si_llms_txt version 1.0.1 (uploaded 2026-10-12) has a title of 191 characters in extensions.xml.gz:

Serves llms.txt, llms-full.txt and a Markdown version of every page per language for AI agents and crawlers generated from the rendered page or written by editors. Optional EXT:news support.

tx_extensionmanager_domain_model_extension.title is declared as varchar(150). BulkExtensionRepositoryWriter::loadIntoDatabase() passes $subject->getTitle() unchanged, so with a strict sql_mode the bulk insert of that chunk fails.

Why this is worse than a single skipped record

BulkExtensionRepositoryWriter::import() first deletes all rows of the remote, then inserts in chunks without a transaction. When a chunk fails:

  • all rows of the failing chunk and all following chunks are missing
  • markExtensionWithMaximumVersionAsCurrent() is never reached, so current_version stays 0 for every row

Observed on 14.3.2 after the failed run: 29,450 of 69,490 versions in the table, SUM(current_version) = 0. In classic mode the Extension Manager therefore shows an incomplete list and offers no updates.

The situation does not heal by itself: the downloaded var/extensionmanager/ter.extensions.xml.gz matches the remote MD5, so needsUpdate() returns false and no re-import happens until the next TER upload. That re-import fails again, because the offending version stays in the extension list permanently.

Steps to reproduce

  1. Run vendor/bin/typo3 scheduler:run with a scheduled “Update extension list” task, or click “Update now” in the Extension Manager (classic mode)
  2. Check SELECT COUNT(*), SUM(current_version) FROM tx_extensionmanager_domain_model_extension

Expected

A single oversized value from the remote must not break the import for everyone. This is the same class of problem as #96209, where an over-long version string was fixed by validating the incoming data in the core.

Suggested fix

  1. Truncate title to the column length in loadIntoDatabase() (multibyte-safe, mb_substr($title, 0, 150)), or skip and log the record. Other varchar fields filled from the XML (author_name, author_email, authorcompany, ownerusername, documentation_link …) should get the same protection.
  2. Run delete + insert + markExtensionWithMaximumVersionAsCurrent() inside one transaction, so a failing import keeps the previous list instead of leaving a half-filled table.
  3. Optionally: on import failure, remove the local ter.extensions.xml.gz, so the next run retries instead of trusting the matching MD5.

Environment

TYPO3 14.3.2, PHP 8.5, MySQL with strict mode. The code is identical on 13.4 and main.

Reviews 3

History 14

  1. Georg Ringer commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-13T08:30:12+00:00" > 10/13/26, 08:30 </span>

    Applied in changeset commit:0769865dcbbfaa1b005077ef0b2fcd123bb7d4ec.