Release: QUIQQER 2.34
Executive summary
QUIQQER 2.34 strengthens the platform at several important integration points. Core 2.34.0 introduces a namespaced REST API, reorganizes locale data, and adds support for webserver-assisted file delivery. At the same time, Sign 1.1.0 establishes a provider-independent foundation for document signing, while DocuSign 3.0.1 moves onto that shared API.
The remaining updates focus on practical project work: clearer guarantee information in commerce, more dependable popup components, improved contact workflows, product translation fixes, and smaller operational corrections. This report is based on the available release notes and is intended as orientation; each installation should still be reviewed against its own modules, integrations, and update process.
What changed
Core APIs, localization, and file delivery
Core 2.34.0 adds REST endpoints under explicit namespaces. This gives connected applications and automation a clearer interface boundary and reduces the risk of unrelated endpoints colliding as integrations grow. Language catalogs are now split and translations completed, which makes locale resources easier to maintain.
The Core can also hand file delivery to the webserver where the environment supports it. That can reduce PHP application work for larger downloads and gives operators another option for efficient delivery. Core XML documents now use a standardized quiqqer root, and Composer constraints accept newer package versions beyond the public mirror.
A shared foundation for document signing
Sign 1.1.0 introduces a provider-independent signing layer and a reusable document-signing window. Review steps, manual document actions, and signer settings are separated more clearly, so future providers can use the same underlying workflow rather than implementing parallel concepts.
DocuSign 3.0.1 adopts this Sign API and removes the former Document API and callback site type for email signing. Existing legacy database rows are left in place, but installations must use QUIQQER Sign 1.x and Core 2.25.1 or newer within the 2.x line. Existing DocuSign connections require reauthorization after the migration.
Commerce information and editor-facing workflows
Product Guarantees 1.1.0 adds EU guarantee notices and GARAN labels, together with global defaults and links to guarantee documents. Manufacturer and EAN data can provide defaults, while the editor now aligns more closely with standard product fields. The storefront presents GARAN information as a compact badge with a fitted detail popup.
Components 1.6.1 improves brick popups with mobile modes, automatic height where supported, and a visible loading state that prevents duplicate windows. Contact 2.6.0 adds the new ContactHub, configurable notices, context in form-request emails, and per-opening start views; the older CtaAction is deprecated.
Operational corrections and integration details
Cron 2.10.2 includes database fixes, corrects the service-window dimensions, and displays the cron-service registration email. Products 2.14.3 handles partial translation updates by product ID and reads category filters from query parameters. Invoice 2.13.2 now reads the invoice address from the POST request.
AI MCP 1.14.2 adjusts protocol handling so modern transports can perform validation at the appropriate layer. This is a narrow change, but it matters for teams connecting QUIQQER to current MCP clients and external automation.
What this means for projects
For integration teams, the Core REST API and the updated MCP behavior provide cleaner boundaries for connected systems. For commerce and editorial teams, the release improves how guarantee details, contact entry points, popup components, and translated product data are handled. The signing changes are the most consequential operationally because they establish a common long-term architecture but require an explicit migration check.
Operational notes
- Review custom integrations before adopting the new Core REST endpoints and standardized XML root.
- For DocuSign, verify Core 2.25.1 or newer, install QUIQQER Sign 1.x, migrate consumers to
quiqqer/sign, and plan reauthorization. - Test webserver-assisted file delivery in the target hosting environment before enabling it for production traffic.
- Check Product Guarantees defaults and guarantee-document links for the applicable market and product catalog.
Looking ahead
QUIQQER 2.34 is primarily a foundation release: it makes APIs and document signing more systematic while removing several small sources of friction in daily project work. The practical value will depend on the modules in use, so the next step is a staged update with focused checks for integrations, signing, file delivery, and commerce data.