Upgrading to 1.1.26
Version 1.1.26 includes a Mobile Safari workaround and backported features from 1.3.2 and 1.3.3.
Important: When upgrading the Hyvä Theme to 1.1.26, always update the hyva-themes/magento2-theme-module package to its latest version simultaneously. It is generally safe to update the Hyva_Theme module (hyva-themes/magento2-theme-module) to the latest version, even if you are not updating the Default Theme to 1.1.26.
Backward incompatible changes
There are no backward incompatible changes in release 1.1.26.
Noteworthy changes
Updated reset-theme to 1.1.5
The hyva-themes/magento2-reset-theme version constraint is now >=1.1.5. If reset-theme is a dependency in your root composer.json, ensure you include it in your update.
Composable header customer-account menu
(Originally released in 1.3.2) This update introduces a composable customer account menu, addressing previous limitations where adding links to Magento_Customer/templates/header/customer-menu.phtml required template overrides, often causing conflicts with third-party extensions.
Existing customer-menu.phtml templates from previous Hyvä Theme releases will still function, but they will not render new menu links added via Layout XML. Consider migrating customized customer-menu.phtml templates to the new approach to leverage this functionality.
You can now add links by declaring child blocks within the header.customer.logged.in.links or header.customer.logged.out.links blocks in your layout XML.
For example:
<referenceBlock name="header.customer.logged.in.links">
<block name="customer.header.orders.link"
class="Hyva\Theme\Block\SortableItemInterface">
<arguments>
<argument name="label" xsi:type="string" translate="true">My Orders</argument>
<argument name="path" xsi:type="string">sales/order/history</argument>
<argument name="sort_order" xsi:type="number">30</argument>
</arguments>
</block>
</referenceBlock>
For more details on adding links, headings, and delimiters to the customer header menu, refer to the documentation.
Changelogs
Access changelogs in the CHANGELOG.md file within the codebase, or via these links:
Tooling
For general upgrade guidance, please refer to the Hyvä Theme upgrade documentation.