Magento: Guides and Practical Know-how | Page 21 | mironsoft Blog
Magento
-
Dec 16, 2025
Without clean fixtures, integration tests are fragile: tests create test data that affects the next test, rollbacks fail and the fixture script sits at a different path than expected. The Magento Test Framework offers a sophisticated fixture system, provided you understand the mechanisms behind it.
-
Dec 16, 2025
Untested GraphQL resolvers are a ticking time bomb: schema changes silently break frontend contracts, and authentication bugs stay hidden until production. This article shows how to test Magento GraphQL on three levels, from unit tests for resolver logic to real HTTP requests against the endpoint.
-
Dec 13, 2025
Serving a generic error message with an HTTP status of 200 for a URL that does not exist quietly costs both search engine trust and real users. This article shows how to properly implement 404 and 500 error pages in the Hyvä theme, from the noroute controller through the correct HTTP status code to an Nginx fallback for when PHP-FPM itself stops responding.
-
-
Dec 10, 2025
A GraphQL resolver that combines database queries, validation, permission checks and transformation logic in a single class is no longer a resolver, it is an unbounded mini-service. This article shows how to keep resolvers thin, introduce clear layers, and move business logic to where it actually belongs.
-
Dec 9, 2025
Once ERP, PIM, CRM and a fulfillment provider are all connected to Magento at the same time, every additional direct connection becomes a risk. A well designed middleware layer with a canonical data model, clear orchestration and a message queue decouples Magento from its neighboring systems and keeps the integration landscape maintainable, instead of letting it grow into an unmanageable web.
-
Dec 9, 2025
Magento supports multiple websites, stores, and store views in a single database, but as the number of tenants grows, the question arises whether this multi-store schema still holds up or whether separate databases per tenant make a better architecture. The answer depends on attribute count, traffic distribution, and team structure, not on a blanket best practice.
-
Dec 8, 2025
How shipping methods in checkout are presented often decides between an abandoned cart and a completed order. In the Hyvä checkout, a lean Alpine.js component that loads its data through a GraphQL availableShippingMethods query replaces the Knockout shipping-rates component. Anyone customizing shipping methods in the Hyvä checkout works with shipping-methods.phtml, ViewModels and custom carrier models instead of uiComponents, observables and RequireJS modules, and gets card layouts, delivery estimates, free shipping thresholds and click and collect as reactive, maintainable building blocks in return.
-
Dec 8, 2025
CMS editors can't write Alpine.js, but they copy HTML from other sources, and attributes like x-show or x-data can be hidden inside foreign code. x-ignore disables Alpine parsing for an entire DOM area and makes CMS content safe.
-
Dec 7, 2025
MFTF automates exactly the class of bugs that unit tests systematically miss: broken checkout flows, faulty JavaScript interactions and admin forms that suddenly stop saving after an update. Whoever sets up MFTF properly gets a browser driven safety net that replays real click paths in storefront and backend automatically and catches regressions before customers do.