CPalius CMF 2.2.13

Released: 2026-09-25 · Channel: stable · Critical: yes

2.2.12 fixed container rebuilding during an automated update, but left the same gap open on AACP's manual "Clear Symfony Cache" button. This release closes that, and explains a one-time catch worth knowing about if you're updating from before 2.2.12.

What's fixed#

AACP's manual cache-clear action emptied the compiled container without rebuilding it, the same gap 2.2.12 closed for the automated update pipeline — an operator clicking "Clear Symfony Cache" by hand got the same "left to whichever request compiles it next" risk. It now rebuilds the container the same way an update does, in its own dedicated process, before reporting done.

A one-time catch if you're updating from before 2.2.12#

PHP does not reload a class mid-request just because an update overwrote its file on disk — the request applying an update keeps running whatever code was already loaded into memory when that request started. Concretely: the request that installs 2.2.12 is itself still running the pre-2.2.12 cache-rebuild code, because that code was already in memory before the new files landed. If you updated directly from an older version, you may have seen the same container error one more time during that specific transition, even though the new files were written successfully. This is not a new bug and 2.2.13 does not change it — it is an inherent limit of updating a live PHP process from within itself, and it only affects the exact request that installs a fix to the update mechanism, never anything after it.

If you hit this: your installation's files are already correct (file writing happens before the cache step, and isn't affected by this). Clear cp-core/var/cache/prod/ by hand once over FTP to get a clean slate — the very next page load compiles a fresh container inline, which is ordinary, expected behavior for any Symfony application after a cache clear, not a failure. From that point on, every future cache clear (manual or automatic) uses the fixed code and rebuilds the container properly on its own.

Upgrade notes#

No schema changes. No other manual steps.