Release: QUIQQER 2.25
Executive summary
QUIQQER 2.25 consolidates a substantial week of platform work. Across 47 package updates, the clearest themes are the transition to ERP 4, continued migration of data access to DBAL, tighter session and permission handling in Core, and practical improvements to operational modules such as Masterlogin, Search, Order, and Watcher.
This report is based on the available release notes and is intended as orientation for project teams. Several entries describe internal contracts or migrations rather than visible features, so rollout decisions should still be based on the packages installed in a specific project and on testing in a staging environment.
What changed
ERP 4 becomes the shared integration line
ERP 4.0.5 makes its interfaces more explicit: article implementations now provide user, currency, VAT, and calculation data, while native types and provider implementations clarify how connected modules exchange information. Products, Payment Transactions, Order Cancellation Policy, and ERP Accounting Templates all add ERP 4 support in the same release window.
The practical value is consistency. Instead of each business module adapting independently, the release aligns product, transaction, cancellation, and document workflows around the same ERP generation. That should reduce ambiguity for integrations, but custom implementations of the affected interfaces need to be checked carefully.
DBAL migration moves through business-critical storage
Several modules continue replacing older database access paths with DBAL. Products migrates product storage and number-range handling; Payment Transactions updates transaction reset and table introspection; Order migrates persistence; Search covers full-text queries, quick search, and site cleanup; and Masterlogin moves its persistence while joining user addresses by UUID.
These changes are mostly below the editor surface, but they are important for maintainability and predictable database behaviour. Because they touch stored business data and maintenance scripts, they deserve focused migration tests rather than being treated as routine interface updates.
Core tightens sessions, events, and permissions
Core 2.25.2 protects internal session keys from AJAX access and adds a dedicated session-user reset function. A new media-replace event gives extensions a clearer point to react when media is exchanged, while support for multiple demo data sets broadens setup and testing scenarios. The release also adds a specific permission for deleting Stripe subscriptions.
Taken together, these are small but consequential changes: sensitive session state is better contained, integrations receive a more precise media lifecycle signal, and privileged subscription actions can be controlled more explicitly.
Operational workflows receive targeted improvements
Masterlogin 2.6.0 adds an audit overview, scheduled cleanup for old logs, modernized dialogs, and more careful CSRF behaviour that avoids session writes while rendering. Watcher migrates user references to UUIDs and validates AJAX parameters. Order Cancellation Policy escapes dynamic output, removes duplicate CAPTCHA markup, uses the project language for request emails, and restores missing page content.
ERP Accounting Templates adds configurable CSS, document and logo styling, footer extensions, and layout options. These changes give teams more control over generated documents without turning template adjustments into one-off code changes.
What this means for projects
- Projects preparing for ERP 4 should review custom article interfaces and test product, transaction, cancellation, and accounting-document flows together.
- Installations with large or long-lived data sets should validate DBAL migrations against backups, scheduled jobs, search indexes, and reset or cleanup scripts.
- Teams using Masterlogin gain clearer auditability and log maintenance, but should verify permissions, session behaviour, and retention expectations.
- Editors and administrators should see incremental improvements rather than a redesigned CMS; most of the value is in safer foundations and more predictable operations.
Operational notes
Payment Transactions now requires PHP 8.2, which should be included in environment checks before rollout. ERP interface changes may require updates in project-specific implementations. Database migrations should be tested with representative data, and the language used by cancellation-request emails should be verified in multilingual projects. As always, take a current backup and review package-level changelogs for the modules actually installed.
Looking ahead
QUIQQER 2.25 is primarily a coordination release: business modules converge on ERP 4, database access becomes more uniform, and Core exposes clearer security and integration boundaries. The result is not one headline feature, but a more coherent base for the next round of project and module work.