Automatically versions CMS Pages and Blocks, shows field-level diffs between versions, and lets you restore snapshots from the admin with configurable retention.
Details how APSB26-146 closes three issues—unsafe object instantiation reachable from CMS/email templates, untyped preview inputs, and writable error reports—and outlines patching steps plus checks to catch similar instantiate-then-check anti-patterns.
MCP with commands and prompts to manage Hyvä CMS content: list components, validate and edit JSON, create/update/publish pages, preview and render-check, and clone pages. Includes in-tool guidance/resources and a recommended editing workflow.
Automatically versions CMS pages and blocks, capturing admin metadata (user, IP, timestamp) and displaying a history grid with one‑click restore. Includes ACL-controlled access and store-aware handling.
Highlights rendered CMS blocks on the storefront, showing ID, identifier, and title, with one-click open in Admin. Includes installation, usage, and configuration details.
Adds attributes to products, categories, and CMS pages to control robots meta (noindex, nofollow, noarchive). When a flag is enabled, that directive is forced to "no" for the entity; otherwise the store’s design setting is used.
Provides versioned backups with restore and cleanup for CMS pages and blocks, plus XML-defined content updates via a versioned upgrade command. Includes admin and CLI tools to import/export JSON/XML (with media), multistore support, and cron-based history pruning.
This module allows the use of custom Tailwind CSS configurations in CMS pages and blocks by saving their content in a specific folder for purging. It serves as an alternative to the existing CMS Tailwind JIT module, ensuring that whenever content is updated, it is replicated for purging by Tailwind CSS. It simplifies the management of custom variables defined in the Tailwind configuration within a Hyvä theme.
Just changed something on the admin panel or on the database and now you need to replicate it again in staging and production? No worries, we got you covered. Probably you already heard about data patches, but what if I say that it can be really, really simplified?
This module shows how to make a repeatable param for a CMS Widget