Release: QUIQQER 2.40
Executive summary
QUIQQER 2.40 brings together practical improvements for commerce projects and the teams that maintain them. Product search becomes more responsive and useful on the desktop, catalog administration gains clearer product and image workflows, and order-related packages preserve business data more carefully. Core 2.40.0 complements those visible changes with better feedback during maintenance and cleaner administrative behaviour.
This report is based on the available notes for the included package releases. It is intended as orientation for maintained projects, not as a project-specific update recommendation. The notes vary in detail, so custom search layouts, checkout steps, product workflows, and integrations should still be tested against each installation before rollout.
What changed
Faster, more predictable product search
Productsearch 2.9.0 refines the complete suggestion cycle rather than one isolated result view. Desktop suggestions can use compact layouts and native links, remain available while the search field regains focus, and ignore stale responses when a newer query has already taken over. Punctuation can act as a single-character wildcard, while product selections and bestseller sorting broaden the available search behaviour.
The package also forwards display options into product suggestions and exposes working titles in search-field settings. Together with price display from Products 2.16.0, this gives projects more control over how useful information appears before a visitor opens a result page.
Safer catalog administration
Products 2.16.0 adds a shared confirmation flow for deletion and keeps the product panel visible while changes are saved. The extensible product panel and grid-result data have been modernised, giving project-specific extensions a clearer base without changing the purpose of the everyday catalog workflow.
Image handling receives several concrete options: images can be included when products are copied, and administrators can activate product images as part of product activation. A configurable product-quality cron adds a recurring operational check for teams that maintain larger catalogs.
Checkout flexibility and preserved order data
Order 2.20.1 supports custom button text for individual checkout steps and adds compatibility for Navigo 5 and 8. More importantly for existing business processes, complete sales-order transfers are preserved and delivery addresses remain intact even when shipping data is absent.
Salesorders 2.11.1 keeps articles when validation fails, while ERP 4.4.3 retains percentage discounts when an article is reopened in accounting. These are narrow changes, but they address costly failure boundaries: a validation message or reopened record should not silently discard information that staff have already entered.
Clearer maintenance and reusable interface controls
Core 2.40.0 describes active maintenance operations more clearly, handles a busy maintenance state without unnecessary console errors, and presents update details and module setup work in a more readable form. Group deletion now cleans up memberships, reducing the amount of residual administrative state left behind.
Qui 1.15.0 introduces reusable colour controls with palette and light/dark support and preserves colour drafts while projects load asynchronously. Controls 2.6.1 keeps the active page when pagination is rebuilt. Both changes are relevant to extension authors as well as administrators because they improve shared interface behaviour instead of solving the same problem separately in each module.
What this means for projects
- Product discovery can show more relevant information while handling focus changes and rapid queries more reliably.
- Catalog teams gain clearer deletion, image, activation, and quality-control workflows.
- Checkout and order processing preserve addresses, articles, transfers, and percentage discounts at important error or editing boundaries.
- Maintenance work becomes easier to understand, with less console noise and cleaner group administration.
Operational notes
Projects with customised product suggestions should test compact and standard layouts, native-link navigation, punctuation searches, stale-response handling, prices, selections, and bestseller sorting. Catalog workflows should be checked with copied and newly activated images, including the configured product-quality schedule.
For commerce projects, exercise every customised checkout step and test both complete and incomplete shipping data. Validate failed sales orders, reopened accounting articles, and sales-order transfers before production rollout. Booking 1.5.5 also refreshes capacity lists after generation, validates email syntax before notifications are sent, and resets the cancellation-mail flag when a booking is reactivated.
Cache 3.6.5 restricts public access to CSS optimizer files. Controls 2.6.1 also identifies the package as a QUIQQER module. These changes are mainly operational, but projects with custom asset delivery or package tooling should include them in staging checks.
Looking ahead
QUIQQER 2.40 is a maintenance-oriented release with a clear commerce focus. Its value lies in connecting small interface refinements with stronger data preservation and more transparent upkeep: search reacts more calmly, administrators retain context, and business records are less likely to lose information when a workflow is interrupted.