Release: QUIQQER 2.38
Executive summary
QUIQQER 2.38 is a broad operational release. Core 2.38.1 makes maintenance and site queries more predictable, while the commerce packages strengthen diagnostics, preserve business data more carefully, and expose additional workflows through MCP. Frontend Users, Cron, and AI MCP address the account, scheduling, and integration foundations around those changes.
This report is based on the available notes from 35 package updates. It provides orientation for maintained projects, but it is not a project-specific update recommendation. Several notes are concise, so installed package versions, custom integrations, and critical workflows should still be reviewed before rollout.
What changed
More predictable Core maintenance
Core 2.38.1 now expires local autosave drafts after 28 days, preventing abandoned browser drafts from accumulating indefinitely. Site and child queries align their active filters, and grouped searches retain their conditions more reliably. Setup and package maintenance are serialized, while legacy update runners can execute setup children, reducing overlap in sensitive maintenance operations.
User configuration also receives a smaller but relevant correction: merged XML category file lists are now loaded consistently. Together, these changes focus less on a visible feature and more on keeping long-lived installations easier to maintain.
Clearer payment diagnostics and safer transaction handling
Payment Paypal 3.7.1 separates live and sandbox connection tests, refreshes saved credentials for diagnostics, and selects the SDK configuration explicitly. It also guards missing billing-plan results and omits inconsistent basket details. Administrators receive a clearer way to diagnose payment configuration without mixing environments or relying on stale credentials.
Payment Transactions 2.4.0 adds MCP-based transaction search and payment workflows, labels statuses more clearly in transaction lists, and improves discovery of optional handlers. These changes make payment operations easier to inspect while preserving compatibility with project-specific extensions.
Business workflows through MCP
Salesorders 2.11.0 expands MCP support for creating and posting sales orders as well as producing PDFs and sending email. Partial invoices now preserve their descriptions, and shared ERP styles improve status and article tables. The result is a broader automation surface without losing the information staff need when reviewing partial billing.
Purchasing 2.14.0 adds electronic-invoice preview and draft import, grouped purchasing statistics, draft management, readiness checks, and process actions through MCP. Shipping 2.3.1 follows the same direction with validated management tools while preserving category restrictions, names, and prices during rule creation. Default price input is validated, localized defaults are used for empty names, and the matching price-factor index is tracked explicitly.
Account, scheduling, and integration foundations
Frontend Users 2.19.0 tightens activation and sign-in handling. Password proof is limited to web sessions, sessions rotate through the released Core API, activation proof survives normalized login errors, and account email addresses are no longer exposed in error redirects. Added translations complete the user-facing part of this work.
Cron 2.13.1 coordinates scheduled jobs with Core maintenance and safely encodes user names during service registration. AI MCP 1.15.1 makes its agentic integration optional and raises the minimum REST dependency to 3.3.1. ERP 4.4.2 complements the operational work by invalidating provider caches after setup and handling missing customer files and upload timestamps more defensively.
What this means for projects
- Long-running installations gain more orderly maintenance execution and more consistent site-search behavior.
- Payment teams can test Paypal environments independently and inspect transactions through clearer administrative and MCP workflows.
- Sales, purchasing, and shipping processes become more accessible to connected tools while retaining important descriptions, restrictions, and prices.
- Projects with custom activation, cron, or AI integrations should review the new session, maintenance-coordination, and dependency behavior before updating.
Operational notes
Test Core maintenance, scheduled jobs, account activation, and payment connections in a staging environment before production rollout. Projects using custom MCP clients should verify permissions and payload expectations for the new sales, purchasing, shipping, Paypal, and transaction tools. For Paypal in particular, test sandbox and live credentials separately rather than treating one successful diagnostic as evidence for both environments.
Looking ahead
QUIQQER 2.38 continues the shift from isolated administration screens toward validated, automatable business workflows. The release also reinforces the less visible platform work that makes those workflows dependable: serialized maintenance, safer sessions, explicit diagnostics, cache invalidation, and preserved business data.