CMS Manager
v1.4.2
CMS Manager
- Updates and support included for 12 months
- License key delivered immediately by email
- 30-day money-back guarantee
- Full documentation included
- Compatible with Hyvä themes
- Composer-ready installation
Module Magento 2 de gestion avancee du contenu CMS multi-store. Permet de gerer des contenus differents (titre, contenu, URL, meta) par store view pour les pages et blocs CMS, sans dupliquer les entites.
Features
- Contenu par store view : surcharge du titre, contenu, heading, URL key et metadonnees (title, description, keywords) pour chaque store view, stocke dans des tables dediees (
wimakeit_cms_page_store_content,wimakeit_cms_block_store_content). - URLs multilingues (slugs) : chaque store view peut avoir son propre identifiant/URL key, avec resolution automatique du slug via plugin sur le routeur CMS.
- Store switcher intelligent : le changement de langue redirige automatiquement vers le slug correct de la page dans la store view cible.
- Integration admin native : onglets par store view dans les formulaires d'edition des pages et blocs CMS, via UI Component modifiers.
- API REST : endpoints pour consulter le contenu par store view (
GET /V1/wimakeit/cms/page/:pageId/store/:storeId, etc.) et recuperer toutes les traductions d'une page ou d'un bloc. - Export / Import CLI : commandes
bin/magento wimakeit:cms:exportetbin/magento wimakeit:cms:importpour exporter et importer les pages/blocs avec leurs traductions au format JSON ou CSV. - Migration des doublons et des traductions : commande
bin/magento wimakeit:cms:migrate-duplicatespour consolider les pages/blocs dupliques (une par store view) en une seule entite avec surcharges par store. Les traductions publiees sous un identifiant different par vue se regroupent avec--map:
``json {"pages": [{"fr": "conditions-generales-de-vente", "nl": "algemene-voorwaarden", "en": "terms"}], "blocks": [{"fr": "tous-nos-kits", "en": "all-our-kits"}]} ``
Cle = code de la vue, valeur = identifiant servi par cette vue, la premiere entree est conservee. Les vues d'origine sont gardees, les reecritures d'URL, la configuration (accueil, 404), les directives {{block}}/block_id/page_id et les etats du page builder sont reportes sur l'entite conservee.
- URL par vue partout : reecritures d'URL et sitemap XML generes avec la cle d'URL de chaque vue.
- Traductions : interface traduite en francais (fr_FR), neerlandais (nl_NL) et anglais (en_US).
Install this module via Composer. Make sure your auth.json is configured with your Wimakeit credentials.
$ composer require wimakeit/module-cms-manager:^1.4.2
$ bin/magento setup:upgrade
$ bin/magento setup:di:compile
- Version
- v1.4.2
- License
- Annual Subscription
- Support
- 12 months
- Last updated
- Oct 16, 2026
- Magento
- Magento 2.4.4 Magento 2.4.5 Magento 2.4.6 Magento 2.4.7 Mage-OS 2.0 Mage-OS 2.1
- PHP
- PHP 8.1 PHP 8.2 PHP 8.3
- Hyvä
- Compatible
- Package
-
wimakeit/module-cms-manager
Compatibility checker
Pick your stack to see if this module fits.
Compatibility 4
Pricing & licensing 4
vendor/wimakeit/ once you composer require the package, so you can read it, audit it, and patch it locally for your own Magento install. You may NOT redistribute it, sublicense it, publish it on a public package registry, or sell it on. One licence = one production domain + one staging/dev domain (see terms for the full EULA). Wimakeit modules are NOT part of Magento's open-source repository on packagist.org — they are distributed exclusively via the private Composer registry packages.wimakeit.be. Installation & updates 6
composer require wimakeit/module-cmsmanager:^1.0.0, then bin/magento setup:upgrade, bin/magento setup:di:compile, and finally bin/magento cache:flush. The Installation tab on this page lists every configuration step (ACLs, cron jobs, default values) so a deploy takes minutes, not hours. If you need a hand, Wimakeit offers Magento installation services from our Wallonian office (Presles, between Charleroi and Namur). auth.json: {"http-basic": {"packages.wimakeit.be": {"username": "YOUR-EMAIL", "password": "YOUR-TOKEN"}}}. Step 3: register the repo: composer config repositories.wimakeit composer https://packages.wimakeit.be. Step 4: composer require wimakeit/module-cmsmanager:^1.0.0. In CI/CD pipelines, inject COMPOSER_AUTH as a JSON env var instead of committing auth.json. composer require, same module code, same database schema — no fork to maintain, no licence change. composer update is safe within a major. app/design/frontend/{YourVendor}/{theme}/Wimakeit_{Module}/templates/ keeping the same relative path. Blocks, ViewModels and Helpers are overridable via DI preference in your own custom module — declare <preference for="Wimakeit\…\OriginalClass" type="YourVendor\Override\Class" /> in etc/di.xml. Layout XML is extended (preferred) or overridden the standard Magento way. Wimakeit modules never use the final keyword on classes you might reasonably want to override — overriding is a first-class scenario, not a hack. Support & security 3
contact@wimakeit.com with the module name, version, Magento/Mage-OS version and the steps to reproduce. Fixes ship in the next patch release. Wimakeit support is staffed in French, English and Dutch on business days (CET working hours). contact@wimakeit.com with a clear [SECURITY] subject prefix — please include the module name, version and the steps to reproduce. We acknowledge promptly on business days and credit reporters in the Changelog if they wish. Wimakeit is a Belgian SRL (société à responsabilité limitée) bound by Belgian and EU privacy and disclosure law. About Wimakeit 1
Found something not covered by the FAQ?
Report a bug or ask a question — the form is prefilled with this module.
v1.4.2
- Saving a page or block wrote an empty content over a store view's translation when no
- Requires Wimakeit_PageBuilder 1.21.2, which posts per-store builder states; before it,
v1.4.1
- StateRenderGateway depends on the Page Builder state contract (Api\StateSerializerInterface)
v1.4.0
- every merged page went live on the store views that never had it, in the
- the URL rewrites of the deleted copies still targeted them, so their
- home, 404 and cookie pages configured as identifier|id on a copy resolved
- {{block id}}, block_id and page_id pointing at a copy rendered an
- a copy that left a field empty (a meta title, a description) inherited the
Added — store URL keys reach URL rewrites and sitemaps
- URL rewrites are generated from each store view's URL key, on save and
- wimakeit:cms:regenerate-url-rewrites [--id=…] rebuilds them for pages
- The XML sitemap lists each page under the store view's URL key instead of
Fixed — the language switcher kept the URL key of the current store
Found a bug? Tell us about it.
A short form opens in a new tab — the module name and your language are already filled in. Share what you tried, what went wrong, and we will get back to you within one business day.
Report a bug for CMS ManagerNeed help?
Our team is available to assist with integration.