Issue Bug Closed

#103281Extension manager Shows old Version Numbers after Update from TER

Thomas Oliver Moll 03/05/24, 11:16 updated 11/15/26, 15:12

Description

Hi,
I’m here on TYPO3 v11 and not yet in Composer mode. So updates are installed “oldscool” via Extension Manager from TER.
Recently some of the local admins started to have the problem, that the extension update completed successfully but the Extension Manager still showed the old version number and the update button.

Clearing caches (red lightning and from maintenance module) and rebulding the autoload information did not help. So I solved it by deleting typo3temp/var/cache manually

I saw, that the outdated version number was cached in typo3temp/var/cache/code/core/PackageManager_754b0ea6278f28297f98ea95c02913d1.php

This does NOT occur when I deactivate-update-reactivate an Extension. And it can be corrected after the fact by “turning it off and on again”

So I wonder where the problem is:
  • Should this information be cached in the first place?
  • Should the offending file be deleted when I “Flush TYPO3 and PHP Cache”?
  • Or should I have done something differently to refresh the outdated version cache?

Also but much more gravely but more vaguely:
Since roughly the same time we saw an increase of failed Extension updates, old versions seemingly leaving behind garbage in cached php, so that TYPO3 encounters confusing PHP Errors after the update, that go away when disabling and enabling the extension again. This also only occurs when the Extension is active during update and can be avoided by turning it off beforehand.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 1

  1. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-15T15:12:46+00:00" > 11/15/26, 15:12 </span>

    Thank you for the detailed report, and sorry that it took so long to get a reply.

    Your observations helped a lot to narrow this down. The fact that it only happens when the extension is active during the update, and that deactivating/activating or deleting typo3temp/var/cache resolves it, points to an interplay between the package cache and PHP’s OPcache:

    When an active extension is updated, TYPO3 v11 flushes the system caches and then rebuilds the package information, which includes reading ext_emconf.php. The OPcache is only cleared afterwards. Depending on the OPcache settings (e.g. opcache.validate_timestamps = 0 or within opcache.revalidate_freq), the old, cached version of ext_emconf.php may be read at that moment, and the old version number ends up in the package cache again. Deactivating and activating the extension rewrites PackageStates.php, which creates a new package cache entry. That’s why this worked for you.

    In current TYPO3 versions this can no longer happen in this form:

    • Since TYPO3 v14.2 (#108345), ext_emconf.php is no longer evaluated if the composer.json of the extension declares version and providesPackages.
    • Since TYPO3 v15 (#109993), the package metadata is read only from composer.json, which is not affected by OPcache.

    I also checked the update of an active extension in classic mode on the current main branch: the new version is shown right away, in the same request and in the next one.

    For installations still running an older version, there are two workarounds: deactivate the extension before updating it, or reset the OPcache (e.g. by restarting PHP-FPM) and delete typo3temp/var/cache/code/core/ after the update.

    As TYPO3 v11 is no longer maintained and the cause is gone in current versions, I’m closing this issue. If you still see this behaviour with TYPO3 v14.2 or newer, please let us know here or open a new issue. We’ll be happy to look into it again.