Skip to content

Upgrading to 1.1.15

When updating the Hyvä Theme to version 1.1.15, please note to always update the hyva-themes/magento2-theme-module to the latest version as well.

Even if not updating the Default Theme to 1.1.15, it should always be safe to update Hyva_Theme module to the latest version (package hyva-themes/magento2-theme-module).

Backward incompatible changes

New Cart Page

Release 1.1.15 replaces the previous GraphQL based cart with a server side rendered cart page.

To keep using the GraphQL cart, the hyva-themes/magento2-graphql-cart extension can be installed. Once installed, the GraphQL cart will be restored. The extension also adds the option to switch between the two carts in the system configuration at

Hyva Themes > Cart Page > General Settings > Cart Selection.

All other changes besides the cart are expected to be backward compatible and can be merged into existing themes as needed, once the theme-module is updated to 1.1.15.

Noteworthy changes

Automatic hyva-themes.json updates

With this release, any time one of the following commands enables or disables a module, the file app/etc/hyva-themes.json is automatically regenerated.

  • bin/magento module:enable
  • bin/magento module:disable
  • bin/magento setup:upgrade

This means it is no longer required to manually run bin/magento hyva:config:generate.

Automatic inclusion of the theme-module in the tailwind content path

After hyva-themes/magento2-theme-module is upgraded, it will use the tailwind.config.js merging feature introduced in the previous release 1.1.14 to automatically register itself to be included in the theme CSS generation.

After upgrading the magento2-theme-module, run bin/magento hyva:config:generate once, and then the hardcoded path to the theme module can be removed from your themes tailwind content configurations.
This is optional though, it is not required to take this step.

For more information on the tailwind config merging, please refer to the compatibility module documentation for tailwind config and tailwind css merging.


Changelogs are available from the in the codebase, or here:

Known Issues

  • None so far