QUIQQER 2.42

Executive summary

QUIQQER 2.42 focuses on the work that shapes everyday administration: clearer order and accounting grids, more reliable locale handling in Core, safer payment processing, and a more complete setup path for AI integrations. The changes are spread across several modules, but they share a practical aim: reduce friction in maintained projects without changing established workflows unnecessarily.

This report is based on the available release notes. It is intended as orientation rather than a project-specific update recommendation; checkout, payment, locale, and AI workflows should be tested with the configuration and integrations used by each installation.

What changed

Clearer order and accounting workspaces

Order 2.22.4 aligns action menus, currency selection, toolbar controls, hover feedback, and important grid columns. Totals can be loaded above the order grid when needed and no longer jump after a collapsed section is reopened. A simple-checkout fallback provides a safer path when the regular checkout flow is not available.

Invoice 2.16.1, Purchasing 2.15.1, and Salesorders 2.12.1 carry the same interface direction into their journals: totals appear above the relevant grids, status information is easier to scan, and toolbar and icon columns are more consistent. ERP 4.5.3 limits payment-date changes to invoices, keeping that accounting action within the records where it belongs.

Locale handling and navigation in Core

Core 2.42.1 loads JavaScript translations by context and waits for frontend translations before exposing the Locale object. Stable locale context paths give extensions a more predictable way to address translated resources, particularly where several modules contribute frontend code.

The rewrite layer now prevents recursive start-page resolution, addressing a failure mode that could otherwise loop through routing logic. Menu search receives focus directly, open menus can switch on hover, and form focus feedback is simplified to the red input glow.

Payment reconciliation and webhook security

Payment Stripe 3.8.0 requires signatures for all Stripe webhook events, supports stripe-php 23, and skips payment-intent states that have already been processed. Recurring payments can be reconciled against invoice drafts through the shared invoice payment-data accessor. These changes strengthen both the event boundary and the bookkeeping path behind recurring payments.

Payment PayPal 3.7.4 adopts the same shared accessor and adds reconciliation for PayPal payments associated with invoice drafts. Projects using recurring billing should test draft-to-payment transitions and webhook handling with their own provider configuration before rollout.

AI account and client management

AI Integration 2.4.0 adds account and client management with guided setup, connection checks, free prompt tests, and clearer model selection. The update turns several integration steps into a single administrative workflow, making it easier to validate an account before it is used by project features.

AI OpenAI 2.4.1 supports Guzzle 7 and 8, connects native OpenAI clients to managed agents, and updates the SDK and default model. The release notes describe integration work rather than a change to generated content itself; existing prompts and model-dependent behaviour should therefore be checked in staging.

What this means for projects

  • Commerce and accounting teams receive more consistent grids, controls, totals, and status presentation.
  • Frontend extensions gain more predictable locale contexts, while Core avoids recursive start-page resolution.
  • Stripe and PayPal integrations receive clearer reconciliation behaviour, with stricter Stripe webhook verification.
  • AI connections can be configured and tested through a more structured administrative flow.

Operational notes

The principal versions reviewed are Order 2.22.4, Core 2.42.1, Payment Stripe 3.8.0, ERP 4.5.3, Invoice 2.16.1, AI OpenAI 2.4.1, Purchasing 2.15.1, Payment PayPal 3.7.4, Salesorders 2.12.1, and AI Integration 2.4.0. Several modules also received earlier releases in the same window, so update planning should use the complete dependency set resolved for the project.

Staging checks should cover simple and regular checkout, order and accounting totals, invoice-draft reconciliation, signed Stripe events, PayPal recurring payments, frontend translation loading, start-page routing, and the AI connection and prompt-test flows.

Looking ahead

QUIQQER 2.42 is a maintenance release with visible improvements in administration and less visible work at integration boundaries. Its value is cumulative: the interfaces are more consistent, locale and routing behaviour is more defensive, and payment and AI connections provide clearer operational paths.


AI & MCP

Ready to connect your AI agent?

Connect AI clients to public QUIQQER skills, installation guidance and the capability catalog; machine-readable setup instructions are available in llms.txt.

https://www.quiqqer.com/mcp