Release: QUIQQER 2.30
Executive summary
QUIQQER 2.30 combines a Core release with practical updates to search, multilingual content delivery, commerce, security, and installation. Core 2.30.0 extends the platform’s structured-data foundation and adds localized website names. Backendsearch 2.2.1 makes large result sets easier to navigate, while Info Popup 2.2.0 gives editors more control over design, timing, alignment, media, and language-specific delivery.
Commerce packages concentrate on cleaner state handling and more consistent analytics. Order and Products align their ecommerce events, Payments handles fees and unavailable payment methods more defensively, and Accounting Export clarifies provider and capability boundaries. This report is based on the available release notes and is intended as orientation; the packages and integrations installed in each project remain decisive for rollout planning.
What changed
Core strengthens structured data and multilingual project identity
Core 2.30.0 adds default JSON-LD data to templates, validates page dates, and normalizes encoded page URLs. Projects can now define a localized website name, and the site interface can carry query parameters without integrations rebuilding URLs independently.
For public websites, this creates a more consistent basis for machine-readable page information and localized branding. Projects with custom templates or structured-data extensions should compare the generated output before and after the update to avoid duplicate or conflicting JSON-LD.
Search becomes more focused in everyday backend work
Backendsearch 2.2.1 can search selected media types by ID, limit results per group, preserve hidden search state, and open a media result in a single panel. The result layout has also been modernized, while recoverable profile HTML warnings no longer interrupt builder workflows.
The practical benefit is less noise when searches span several content groups and fewer clicks when a known media item needs to be inspected. Teams with custom search providers should verify grouping and result limits against their usual backend workflows.
Info popups gain a fuller editorial model
Info Popup 2.2.0 adds design preview cards, media layouts, horizontal and vertical alignment controls, configurable delay, adaptive media, and MCP-managed popups. Per-language targeting makes delivery aware of the current project language instead of treating one popup as universal content.
This turns the module from a simple overlay into a more deliberate publishing tool. Editors can prepare language-specific messages and preview presentation choices, while project teams should check timing, alignment, and mobile media behavior across representative pages.
Commerce tracking and order state are aligned
Order 2.15.0 adds a configurable finished-order status and normalizes GA4 ecommerce payloads. It records order interactions and product-list impressions while keeping product tracking out of the order domain itself. Products 2.11.0 exposes matching list and product interaction events, corrects price and tax calculations, and invalidates product and price caches when underlying data changes.
Together, these changes create cleaner boundaries between order processing, catalogue data, and analytics. Commerce projects should test the complete measurement path—from list impression and product interaction to checkout completion—alongside price, tax, and cache behavior.
Security and integration boundaries become more explicit
CSRF 1.0.6 adds tokens to backend request headers, avoids exposing them in GET forms, binds form tokens to internal actions, and limits session-token storage. AI MCP 1.11.0 accepts a scoped upload token alongside MCP authentication and declares the server capability used by connected clients.
Install 1.9.0 complements this work with safer password input, repeated confirmation of database and user passwords, and an ownership check for the installation directory. These are operational safeguards rather than visible CMS features, but they reduce ambiguity at points where credentials and trusted automation cross system boundaries.
Payments and exports receive focused reliability work
Payments 4.2.0 preserves numeric payment fees, rejects unavailable order payment methods, and creates provider payments during installation. Accounting Export 2.4.0 centralizes required package configuration, handles missing export domain objects, rejects unknown providers, and explicitly declares the accounting-export capability.
The changes should make configuration and failure states easier to reason about. Projects with custom payment or accounting providers should verify provider discovery, fee calculations, installation setup, and missing-data behavior before production rollout.
What this means for projects
- Validate generated JSON-LD and localized website names on projects with custom templates or SEO extensions.
- Test grouped backend searches, media-ID lookup, and custom search providers with realistic result volumes.
- Review language targeting, delay, alignment, and responsive media for existing info popups.
- Run commerce tests across prices, taxes, cache invalidation, GA4 payloads, list impressions, and finished-order status.
- Check custom forms, backend requests, upload automations, payment providers, and accounting exports against the revised security and capability boundaries.
Operational notes
Apply the update first in staging with a current backup. Structured data, multilingual presentation, analytics, and provider integrations all depend on project-specific configuration, so generated output and end-to-end workflows matter more than package versions alone. Where release notes are brief, package changelogs and representative project tests remain the authoritative basis for deployment decisions.
Looking ahead
QUIQQER 2.30 is not centered on one headline feature. Its direction is broader: public page data becomes more consistent, editors gain more precise controls, commerce events are separated more cleanly, and security-sensitive integrations state their expectations more explicitly. For maintained projects, that coordination is the main value of this release.