Executive summary
QUIQQER 2.37 brings together ten coordinated releases across the platform. The main work strengthens mobile upload security, adds project-level control over frontend loading, improves cache correctness in different rendering contexts, and moves more content types to JSON-LD structured data.
The release is primarily an operational update: it reduces ambiguity in caches and uploads while giving administrators clearer controls for live projects.
Safer uploads and clearer project controls
Core 2.37.0 adds project settings for frontend loader types and colours. Projects can now tune this part of the frontend without relying on a single global presentation.
Mobile uploads now require device approval and rotating codes. A dedicated administration grid lists permitted devices, making the upload path easier to control and review. QR-based media uploads can also be configured per project.
More predictable caching
Cache 3.6.4 separates cached output by effective WebP mode and avoids shared temporary files during CSS generation. The QJO worker also runs with a restricted open_basedir. Menu 3.13.4 and Bricks 2.41.1 also vary cached HTML by rendering context. GDPR 2.12.1 separates cookie caches by language while allowing consent to be shared across language versions. Together, these changes reduce the risk of one request reusing output created for a different context.
Structured data for lists and news
Sitetypes 2.10.0 moves children lists from microdata to JSON-LD and adds support for pinned entries in brick lists. News 2.6.1 follows the same JSON-LD direction, while Blog 2.5.1 registers blog-list data in the page graph. This creates a more consistent structured-data foundation across editorial list views.
Smaller operational refinements
Template Cologne 2.7.3 handles anchor links with menu-aware scroll offsets. Feed 3.5.2 handles orphaned feeds more safely and cleans up feeds when projects are deleted.
Update guidance
Projects using mobile uploads, custom frontend loaders, WebP variants, cached menus, or structured editorial lists should review the corresponding settings and output after updating. As usual, the package release notes remain the source for project-specific compatibility checks.