Release: QUIQQER 2.23
Executive summary: QUIQQER 2.23 is a practical platform release. The strongest movement is in Core and maintenance tooling: update handling, MCP-supported automation, webserver settings, Composer execution, and small but useful editing improvements all received attention. For live projects, the release is less about one large feature and more about making the CMS easier to operate, integrate, and keep current.
This overview is based on the available release information. It is useful for orientation, but it is not a replacement for a project-specific update decision; with sparse details alone, no reliable rollout decision should be made.
What changed
Core and automation foundation
Core reaches 2.23.6 after several release steps in the 2.23 line. The visible work improves the operational foundation: a FrankenPHP configuration generator was added, an isolated update runner with MCP support is now available, webserver settings can handle www redirects, and the trash panel now carries deletion dates. These are the kinds of changes that reduce friction for teams running maintained installations rather than only changing the editor surface.
Maintenance and runtime reliability
Composer 1.10.5 focuses on how CLI execution is detected and normalized. PHP binary detection, composer.phar handling, path validation, and command normalization were all adjusted. In practical terms, this should make maintenance tasks more predictable across different hosting and deployment environments.
Integration points
AI MCP 1.5.0 improves server handling during maintenance and adds support for AI skills in MCP. Together with the Core update runner work, this points to a clearer path for connecting CMS data and operations with external tools and automation workflows.
Editor-facing and business modules
Presentation Bricks adds delayed poster-first loading for videos, a configurable counter brick, number add-ons for counter entries, and richer progressbar options. Pricetable Bricks adds configurable pricing cards with image, description, and button-only action settings. Payment Stripe, Accounting Core, Controls, Translator, and AI Integration received smaller quality and maintenance updates.
What this means for projects
Projects that rely on automated maintenance, custom deployment environments, or connected tooling should pay particular attention to Core, Composer, and AI MCP. Projects with active landing pages or pricing content may benefit from the brick updates, especially where video loading, counters, or pricing cards are already in use.
Operational notes
- Review Core update and webserver setting changes in a staging environment before applying them to production.
- Check Composer-related maintenance workflows if the project depends on custom PHP paths or CLI execution.
- For Stripe subscription handling, verify pause and suspension behaviour against the project’s billing process.
- Because several notes are compact, treat this post as a release orientation and not as a substitute for testing.
Looking ahead
The 2.23 line continues the steady work around operation, integration, and editor support. It does not change the public shape of QUIQQER dramatically, but it strengthens the day-to-day foundation that live CMS projects depend on.