QUIQQER 2.41
Executive summary
QUIQQER 2.41 combines a visible design-system improvement with a series of operational changes across the CMS. Core 2.41.0 introduces central project colour palettes with light and dark variants and provides shared CSS output for those colours. At the same time, authentication, mail upgrades, tag searches and queue processing received changes intended to make maintained installations more predictable.
This report focuses on the changes with a practical effect on projects. It is based on the available release notes and is intended as orientation; the appropriate update path still depends on each installation, its modules and its deployment process.
What changed
Shared project colours and safer Core operations
Projects can now define central colour palettes with light and dark variants instead of repeating colour values in separate places. Core also emits shared CSS for these colours and uses the colour field for automatic colour-input imports. This creates a more consistent base for templates and extensions while reducing duplicated styling work.
Core now warns when a system is running a PHP version below 8.3. In authentication flows, a personal factor is confirmed before two-factor authentication is enforced, which should make the transition into protected sign-in flows more deliberate. Mail queue upgrades add missing columns where necessary and order queued messages by the existing ID column, reducing avoidable uncertainty during upgrades and processing.
Faster tag lookups and cleaner frontend output
Tags 2.3.4 caches tag searches, reuses stable cache entries until invalidation and avoids queries that are not needed. It also applies the configured result limit and reuses cached site assignments across tag combinations. On content-heavy projects, these changes should reduce repeated database work without changing the editorial model.
Cache 3.6.7 preserves escaped attributes when lazy loading is added and removes unused frontend dependencies. The practical effect is modest but important: generated markup remains intact while the package carries less unused code.
Queues, authors and business workflows
RabbitMQ Server 3.0.1 adds TTL delay queues, reliable publishing and checks for QUIQQER queue processing. The worker now initializes its current job before execution, and the diagnostic command was renamed to test_task_system. QueueServer 2.2.0 complements this work with a diagnostic command, DBAL-based queue queries and additional job-state guards.
Blog 2.6.0 adds responsive author layouts and guest-author profiles, completes author translations with locale contexts and suppresses unnecessary logging for missing authors. ERP 4.5.1 supports PDF.js 6 alongside version 4 and preserves displayed VAT rates when articles are saved. Products 2.17.1 keeps text-product images when products are converted to unique products; both ERP and Products expose shared backend grid extension hooks for variants.
Smaller presentation changes round out the release: Plugin Animate 2.2.2 starts scroll animations for tall elements as soon as their top edge becomes visible, while Template Cologne 2.8.0 adds a CSRF token to the frontend profile form and separates desktop and mobile basket navigation settings.
What this means for projects
The central colour palette is the most visible platform change in this release because it gives templates and extensions a common source for project colours. The performance work in Tags and the queue changes are less visible, but they address repeated work and operational diagnostics that matter on long-running installations. Teams using Blog, ERP, Products or Template Cologne should review the module-specific behaviour during their normal staging checks.
Operational notes
- Core reaches 2.41.0; the same release window also included Core 2.40.1 and 2.40.2.
- The reviewed module versions are ERP 4.5.1, Tags 2.3.4, Cache 3.6.7, RabbitMQ Server 3.0.1, Blog 2.6.0, Plugin Animate 2.2.2, Products 2.17.1, Template Cologne 2.8.0 and QueueServer 2.2.0.
- Installations below PHP 8.3 will now receive a Core warning. This is an operational signal, not by itself a complete compatibility assessment.
Looking ahead
QUIQQER 2.41 strengthens shared project configuration and several background workflows without presenting every change as a headline feature. Before updating a production system, test the relevant modules, authentication path, mail queue and asynchronous jobs in the project’s own staging environment.