Release: QUIQQER 2.24
Executive summary
QUIQQER 2.24 brings together a broad week of platform work. The most consequential changes are concentrated in four areas: authentication and permission handling in Core, safer generation and optimization in Cache, new integration options in Feed, and more flexible editorial lists in Sitetypes. Supporting packages add practical improvements for CRM work, master-login auditing, demo data, customer data, and maintenance quality.
This report is based on the available release notes from 41 package updates. It is intended as an orientation for project teams, not as a substitute for reviewing the installed package set and testing an update in the context of a specific project.
What changed
Passkeys and safer account handling
Core 2.24.2 adds WebAuthn and passkey authentication, giving projects a modern sign-in option beyond conventional passwords. The same release line corrects group validation, improves country-attribute handling, and adds a root-group fallback during setup. Together, these changes address both the visible login path and the less visible account and permission foundations behind it.
More predictable cache generation
Cache 3.2.5 now publishes generated files atomically, which reduces the risk of incomplete files being visible while assets are rebuilt. The optimizer command execution was hardened, missing-image handling was improved, and media-cache processing received additional attention. These are operational changes, but they matter directly for stable front-end delivery and safer maintenance runs.
Feeds as a stronger content and integration surface
Feed 3.2.0 adds CSV feed support, MCP integration, content-search settings, and an updated developer API. URL generation and feed listing were also refined. This makes the package more useful where content needs to be exported, searched, or connected to external tools without creating a separate integration for every workflow.
More flexible lists for editors
Sitetypes 2.8.1 expands ChildrenList with card and media-list templates, design settings, themable card surfaces, tags, and support for pinned news entries in sorting. Image containment and creator output were corrected as well. Editors and implementers gain more control over how collections are presented while retaining predictable layout behavior.
Business workflows and supporting packages
CRM 1.1.0 completes task-management workflows, adds due-task reminders, and exposes the company field in the task grid. Masterlogin 2.4.0 adds event handlers and session logging for master-login activity. Demodata can now manage multiple data sets per template, while Qui PHP, Customer, and Offers mainly tighten type handling, localization, permissions, and maintenance tooling.
What this means for projects
- Projects can evaluate passkeys as a stronger and more convenient authentication option, while paying attention to their existing account and permission setup.
- Sites with asset-heavy front ends benefit from safer cache publication and more defensive optimizer and media handling.
- Content teams gain broader options for feeds, pinned news, cards, media lists, and reusable list presentation.
- Projects using CRM or privileged master-login workflows should review the new task, reminder, event, and logging behavior.
Operational notes
Authentication, permissions, cache generation, and integration APIs are sensitive parts of a live installation. Test these paths in staging before production rollout, especially where custom login flows, optimizer commands, feed consumers, or ChildrenList templates are in use. Several supporting-package notes are brief, so package-level changelogs and project-specific checks remain important.
Looking ahead
QUIQQER 2.24 does not revolve around a single headline feature. Its value lies in the combination: a more current authentication foundation, safer operational behavior, clearer integration surfaces, and practical editorial controls. That is steady platform work aimed at making maintained projects easier to operate over time.