Release: QUIQQER 2.21
Executive Summary
QUIQQER 2.21 is a maintenance-focused release round for active CMS projects. After filtering out housekeeping repositories that do not belong to the public module set, the relevant updates concentrate on the CMS Core, Bricks, Backendsearch, Menu, Slider, Cron, Translator, OAuth Server, and the test tooling around the platform.
The main direction is clear: the platform work continues the DBAL migration, improves permission and account-related handling, and cleans up module APIs and maintenance paths. For project teams, this is less about a visible front-end change and more about keeping long-running installations predictable, easier to maintain, and ready for the next compatibility steps.
What changed
Core 2.21.5 is the central update in this round. Several Core releases landed close together, including work on conditional setting visibility, permission-manager database handling, edit.php database interactions, DBAL migration details, reserved-column quoting, DBAL 4.2 primary-key support, and legacy or unsupported site-query conditions. In practical terms, this reduces friction in the deeper CMS layer where permissions, site queries, and database compatibility meet.
Bricks 2.28.1 continues the steady improvement of structured content workflows. Custom fields in site-area bricks are handled more reliably, and the CustomerReviewsFlow now uses the newer ScrollingStrip speed and resume settings. Editors may not see a dramatic new surface, but reusable content areas should behave more consistently in day-to-day work.
Backendsearch 2.1.2, Translator 2.3.3, and Cron 2.7.1 show the operational side of this release window. Their changes are mainly about database access, composer and database configuration, phar updates, permission defaults, and removing unnecessary service handling. These are the kind of updates that make maintenance calmer rather than more visible.
Menu 3.8.0 adds menu MCP tooling and improves the technical documentation and test setup around the package. It also corrects level-variable handling in the SidebarDropDownMenu. That combination matters for both interface reliability and automation: menus remain an editorial feature, but they are increasingly part of connected CMS workflows.
Slider 2.5.0 introduces a generic Embla carousel control and migrates ScrollingStrip to it. This is a compact foundation change for front-end components that depend on reliable, reusable motion behavior.
OAuth Server 3.2.1 improves OAuth scope matching for optional REST route segments and updates phar versions. For integrations, this means route permissions can be matched more accurately where REST paths contain optional parts.
What this means for projects
- The DBAL migration continues across Core and supporting modules, reducing compatibility risk for maintained installations.
- Permission, account, OAuth, and route-handling details receive practical reliability work.
- Editors benefit indirectly from more consistent Bricks, Menu, Slider, and content-component behavior.
- Teams using automation or MCP tooling get cleaner integration points around Menu and related maintenance workflows.
Operational notes
This overview is based on the available release information. Some package notes are brief, so the article should be used as orientation, not as a replacement for a project-specific update decision. Projects with custom database queries, permission extensions, OAuth integrations, or heavily customized content components should review the relevant packages before updating.
Looking ahead
QUIQQER 2.21 continues the current pattern of incremental platform work. The value is cumulative: database compatibility, permission handling, content components, and integration tooling are being tightened in small steps so live projects can stay maintainable without unnecessary disruption.