Release: QUIQQER 2.22
Executive Summary
QUIQQER 2.22 is a broad maintenance and product-quality release for the CMS platform. The release window contains 18 relevant package updates, with the strongest signals in Core, template presentation, editing workflows, feed handling, portfolio/news presentation, tags, purchasing integrations, bricks, and site type configuration.
The practical message is straightforward: teams running maintained QUIQQER projects get a calmer Core foundation, more predictable integration points, and several improvements that make daily content work easier to configure and operate. The notes are still based on the available release information; they are useful for orientation, but they do not replace a project-specific update decision.
What changed
Core 2.22.2 combines the 2.22.0, 2.22.1, and 2.22.2 work into one visible release line. The most important changes are platform-facing: language links are now exposed through the MCP API, project-specific custom CSS and JavaScript received MCP tooling, and the user invite flow was added. At the same time, htaccess handling was cleaned up and older Apache support paths were removed, which reduces legacy surface area in maintained installations.
Template Presentation 3.1.3 and related content packages focus on the editing and presentation layer. The release adds a chip component, a neutral badge default, configurable footer and logo behavior, full-width brick areas, and more fluid typography. For editors and implementers, these changes are less about a single headline feature and more about making design systems easier to tune without custom workarounds.
News 2.3.0, Portfolio 2.1.0, and Sitetypes 2.7.0 add more configurable presentation options. News articles gain project-wide layout settings and an image-first option; portfolio references get stronger layout and logo controls; list templates gain a “Featured + Cards” variant. These are practical improvements for sites where content needs to be reused in different editorial contexts.
Tags 2.1.0 and Purchasing 2.3.0 continue the integration theme. Tags add MCP server interfaces and operation-based tools for site tags and tag groups, while Purchasing exposes a read-only MCP provider. Feed, Contact, and Bricks received smaller quality fixes around URL generation, CTA serialization, PHP compatibility, and editor visibility.
What this means for projects
- Projects with MCP-based automation get more useful surfaces for language links, custom assets, tags, tag groups, and purchasing data.
- Editorial teams gain more layout control in News, Portfolio, Sitetypes, Bricks, and Template Presentation without turning every change into a custom implementation task.
- Maintenance teams get a cleaner Core baseline through legacy htaccess cleanup, validation fixes, feed URL normalization, and small compatibility improvements.
Operational notes
As with every platform update, the right rollout depends on the installed package mix and project-specific customizations. The Core changes touch integration and infrastructure-related areas, so projects that rely on custom htaccess behavior, MCP tooling, or automated language-link handling should test those paths deliberately before updating production systems.
Looking ahead
The release does not read like a one-off feature drop. It is a steady step toward a CMS that is easier to connect, easier to configure, and less noisy to maintain. That is valuable work: not because every individual item is large, but because the combined effect reduces friction for teams who operate real QUIQQER projects over time.