Skip to content

Upgrading to 1.3.1000-beta1

Beta release - not for production use

Hyvä Checkout 1.3.1000-beta1 is a beta intended for testing and evaluation only. Do not run it on a production store. Install it in a development or staging environment so you can validate the new EAV attribute behavior ahead of a stable release.

Hyvä Checkout 1.3.1000-beta1 focuses on expanded EAV attribute support in the checkout address forms, together with a redesigned admin configuration experience for address fields.

Additional customer and customer address attributes are now rendered and validated in the billing and shipping address forms. These frontend input types are supported:

  • Text Field
  • Text Area
  • Date
  • Dropdown
  • Yes/No (boolean)
  • Multiple Select
  • Multiline

File and Image input types are not supported. For a full walkthrough of creating an attribute and assigning it to the checkout address forms, see Adding Custom Address Attributes.

The changelog has the full list of changes in this release.

Installing Hyvä Checkout 1.3.1000-beta1

Check the upgrade process overview for Hyvä Checkout first. Then run:

composer update --with-dependencies hyva-themes/magento2-hyva-checkout:1.3.1000-beta1

Composer only installs pre-release packages when your project's stability settings allow it. If the beta refuses to install, check the minimum-stability and prefer-stable settings in your composer.json, or require the beta version explicitly.

Why beta versions use the 1000 patch range

Beta releases of Hyvä Checkout use the 1000 patch range (for example, 1.3.1000-beta1) so we can keep shipping regular 1.3.x maintenance versions while a beta is in progress. It's intentional, and it keeps betas clear of the normal maintenance release cycle.

Saving Custom EAV Attribute Values

Hyvä Checkout renders and validates the additional EAV attributes in the address forms, but where those submitted values end up depends on which Magento edition you run.

Custom attribute values are validated but not persisted on Magento Open Source

On Magento Open Source, Hyvä Checkout does not persist the submitted values of custom EAV attributes out of the box. There is no save service for these attributes in Open Source, so their values are not stored against the customer or address without further integration work.

On Adobe Commerce, these values are saved automatically through the Magento_CustomerCustomAttributes module, giving parity with the native Luma checkout.

Address Form Configuration Data Migration

When you enable Hyvä Checkout 1.3.1000-beta1, two data patches run automatically to update your existing billing and shipping address form configuration:

  • MigrateAddressConfig backs up your current billing and shipping address form configuration (to a ..._legacy config path) and migrates the legacy enabled/required field flags into their own dedicated configuration values.
  • RemoveCustomerAttributesFromAddressConfig removes customer-entity attributes (such as dob, taxvat and gender) from the address form configuration, since these cannot be saved against an address entity.

To roll the migration back, this console command restores the backed-up address form configuration:

bin/magento hyva:checkout-attributes:restore

Add the --dry-run (-d) option to preview what the restore would change without applying anything:

bin/magento hyva:checkout-attributes:restore --dry-run

Backward Incompatible Changes

  • No Backward Incompatible Changes.

Deprecations

  • The Enabled and Required columns in the admin address field configuration grid are no longer configurable. Both values are now derived from the underlying EAV attribute definition.

Template changes

Hyvä Checkout 1.3.1000-beta1 adds form field templates for the newly supported input types:

  • src/view/frontend/templates/form/field/date.phtml
  • src/view/frontend/templates/form/field/textarea.phtml
  • src/view/frontend/templates/form/field/multiline.phtml
  • src/view/frontend/templates/form/field/multiselect.phtml
  • src/view/frontend/templates/page/js/magewire/directive/multiselect.phtml

These existing templates were updated:

  • src/view/frontend/templates/form/field/select.phtml
  • src/view/frontend/templates/form/field/text.phtml

If you override any of these templates in a child theme, review your overrides against the new versions.

Changelogs

Changelogs are available from the CHANGELOG.md in the codebase, or here in the docs.