CPalius CMF 2.2.7
Released: 2026-09-24 · Channel: stable · Critical: yes
Applying 2.2.6 (and earlier releases carrying the same bug) could leave a module's migration marked "applied" without actually creating everything it promised, and could compile frontend assets against a stale, pre-update container. Both are fixed, and both self-heal on sites that were already bitten.
What's fixed
A dropped SQL statement no longer gets lost silently. The module migration runner decided a chunk of a .sql file was "just a comment" by checking whether the whole chunk started with --, which also discarded the statement that comment explained. Two shipped migrations hit this: the Whitepaper module's document table was never created, and a Forum column-add silently no-opped. The parser is fixed, and a one-time update hook re-queues just those two files so an already-updated site heals on its next cp:update run — no manual database work required.
cp:update's asset compile no longer reads a stale container. The kernel cache purge that follows a code deploy was deferred to the end of the HTTP request, but the asset compiler is spawned as its own process moments earlier — it could still see the container compiled before the update landed, and fail to find a brand-new module asset. The purge now happens before that process starts.
A module wiring itself directly onto a Symfony kernel event (not the module hook system) is now isolated too. Several built-in modules do this for request/controller/exception handling. Previously, an exception there could take the whole site down, admin panel included. It is now caught and logged the same way a module hook failure already was — this is a real gap that predates 2.2.7, closed here.
cp:doctor gained a new check. module_sql_integrity verifies that a migration marked "applied" actually produced the table or column it claims to, instead of only trusting the bookkeeping.
A pre-existing Forum crash is fixed. The forum index page could throw a fatal error while building its category tree (unrelated to the update mechanism — this bug predates 2.2.6).
Upgrade notes
Nothing manual is required. If your site already ran an affected release, the update hook repairs it automatically the first time you run the updater after installing 2.2.7.