Release: QUIQQER 2.39
Executive summary
QUIQQER 2.39 concentrates on dependable day-to-day operation. Core 2.39.0 makes forwarding rules and media migrations more defensive, refreshes the shared login experience, and adds clearer information around package licences. Several companion releases improve recovery after a session expires, while Contracts, Template Presentation, and AI MCP refine document, navigation, and connection workflows.
This report is based on the available notes for nine package updates. It is intended as orientation for maintained projects, not as a project-specific update recommendation. Where the notes describe narrow implementation changes, the practical effect should be confirmed against the modules, customisations, and workflows used by each installation.
What changed
Safer forwarding rules and media migrations
Core 2.39.0 rejects malformed forwarding-rule INI headers on PHP 8.2 instead of allowing an invalid configuration to pass through. Global forwarding rules are now validated and written atomically, reducing the risk of a partially persisted ruleset when configuration is changed.
The media v2 migration normalises filenames and handles invalid source entries more defensively. These changes are primarily operational: they make upgrades and long-lived installations less dependent on perfectly clean historic data.
Login, sessions, and administrative continuity
Core redesigns the shared login dialog. Frontend Request Signing 1.2.3 renews signing tokens during reauthentication and asks for login when a signing token is invalid; CSRF 1.2.1 renews page tokens after session loss. Dashboard 2.4.3 complements this by reloading its iframe after reauthentication and reading iframe tooltips without relying on MooTools.
Together, these changes address a common operational boundary: an active browser session can expire while work is still in progress. Projects should see fewer dead ends around renewed authentication, although custom login and iframe integrations still need to be tested.
Contracts and signing details
Contracts 2.12.0 adds QR uploads for informational signing attachments, honours the invoice recipient and current address, and explains a missing signing provider beside the relevant action. The update therefore combines a new document hand-off with clearer guidance and more accurate recipient data.
For projects using customised contract templates or provider integrations, the important check is the complete path: recipient selection, attachment upload, provider availability, and the resulting document.
Navigation, layout semantics, and connected tools
Template Presentation 6.13.1 defines layout-specific main landmarks while excluding sidebars. It also adds dynamic anchor links, updates URL history during anchor navigation, and supports smooth scrolling for same-page URLs. This improves both page semantics and navigation on longer content pages.
AI MCP 1.16.0 introduces a guided connection dialog in the backend. Rather than changing the underlying integration model, it gives administrators a clearer route through initial connection setup.
What this means for projects
- Forwarding configuration and media migrations become more defensive around malformed or historic data.
- Login recovery, signing tokens, CSRF tokens, and dashboard iframes are handled more consistently after session loss.
- Contract signing gains a practical QR-based attachment hand-off and more accurate address handling.
- Long pages receive better landmarks and more predictable same-page navigation.
Operational notes
Test forwarding-rule changes on PHP 8.2, review migrated media filenames, and run the relevant migration against a staging copy before production rollout. Projects with custom authentication should exercise reauthentication in Frontend Request Signing, Dashboard, and normal page forms. Contract workflows should be checked with the configured provider, invoice recipient, current address, and QR-upload path.
The remaining releases are deliberately focused: Teampage 2.2.1 moves team-user settings to XML categories, Coupons 2.9.1 reports successful frontend redemption correctly, and Core adds an optional state or province field, adjusts grid-export generation, and presents package licence requirements in a dialog.
Looking ahead
QUIQQER 2.39 is not centred on one large feature. Its value lies in reducing friction at the boundaries between configuration, migration, authentication, and ongoing administration. That makes the release most relevant to teams maintaining active installations over time.