#Magewire

Checkout & Conversion Checkout

May 20

Conditional Checkout Fields in Magento 2: Show Field A Only When B Is True

Conditional checkout fields are the rule set that says "only show field A when condition B is true", and they look identical on Luma and Hyvä until you try to ship one. This is the production recipe for three real rules on both stacks: a Knockout subscribe on Luma, a Magewire $reactive plus Alpine x-show on Hyvä, plus the quote_extension_attributes wiring that keeps the value alive across page reload and 3DS redirect. The three rules ship together in roughly 38 hours on Magento 2.4.4-2.4.9 with Hyvä Checkout 1.1+.

Kishan Savaliya 12 min read

Hyvä Theme Checkout

May 20

Hyvä Checkout Customization: 5 Real Patterns from Production Stores

Five Hyvä Checkout customizations that actually shipped on production Magento 2.4.4-2.4.9 stores: what the merchant asked for, what was tricky, and the code shape. Google Places address autocomplete bound to the Magewire shipping component via an Alpine.js bridge. CPF for Brazil / VAT for the EU as reactive Magewire fields with wire:model.live. Runtime carrier filtering through a collectShippingRates plugin. A post-purchase upsell Magewire component on the success page with one-click PayPal Express. Locale-aware date pickers via the Hyvä i18n partial. For each: the trigger, the file shape, the gotcha.

Kishan Savaliya 12 min read

Checkout & Conversion Checkout

May 20

Magento Checkout Step Customization: Splitting Payment Into Multi-Step

Surfacing BNPL options (Klarna, Affirm, Sezzle) in Magento checkout is not just a payment-method toggle: those gateways need the shipping country and cart total to decide eligibility, which means payment must become its own step that boots only after shipping is set. Here is the full Luma path (Knockout subscribe on setShippingInformation) and the Hyvä path (Magewire listener on shipping.updated), with server-side guards via Magento\Quote\Model\QuoteValidator and the gateway-eligibility cache layer that keeps the step responsive.

Kishan Savaliya 12 min read

Hyvä Theme Checkout

May 20

Hyvä Checkout Custom Field: A Working Delivery-Date Example

Most Hyvä checkout customization tutorials stop at "render a field" and skip the backend plumbing that actually persists the value to the order. Here is a complete, copy-pasteable delivery_date field for Hyvä Checkout 1.2+ on Magento 2.4.4-2.4.9: the Magewire vs Alpine.js decision tree, the extension_attributes.xml declaration, the Magewire component class, the date input partial with HTML5 min/max constraints, the QuoteRepository save plugin, and the admin sales_order_view.xml display. Plus the gotcha that breaks guest checkouts: the date does not survive submitQuote without a second plugin.

Kishan Savaliya 12 min read

Hyvä Theme Hyvä

May 20

Magento Luma Module Not Working in Hyvä: The Diagnostic Order

Your Luma extension worked yesterday on Magento Blank. Today on Hyvä it renders nothing, or worse, breaks the page silently with no console error. The fix is not "reinstall the module" or "flush cache". There is a diagnostic order, four checks in sequence, each with a distinct DevTools signal, that resolves 95% of Luma-to-Hyvä incompatibilities. This guide walks the order using real modules we have debugged (Mageplaza, Amasty, MGS) on Magento 2.4.4-2.4.9 production sites. Each step has the actual symptom, the actual signal, and the actual fix, not a generic compatibility checklist.

Kishan Savaliya 12 min read

Checkout & Conversion Checkout

May 19

Add a Custom Field in Magento Checkout (Luma + Hyvä)

Adding a custom field to Magento 2 checkout (delivery date, VAT number, gift message) is well-documented for Luma, and a moving target on Hyvä. Here is the complete path for both stacks, with quote extension attribute wiring and admin order display.

Kishan Savaliya 11 min read

Hyvä Theme Hyvä

May 19

How to Make Any Magento 2 Extension Compatible With Hyvä

Most Magento 2 extensions ship for Luma only: Knockout bindings, RequireJS components, jQuery widgets. Hyvä replaces all three. The good news: a 4-step pattern handles 90% of ports. Here is the exact workflow with code for Klarna, Stripe, and Yotpo.

Kishan Savaliya 12 min read