Magento: Guides and Practical Know-how | Page 39 | mironsoft Blog
Magento
-
Jun 16, 2025
A cookie banner that enables Google Tag Manager through an inline script immediately violates the Content-Security-Policy in a Hyvä theme and gets silently blocked by the browser. This article shows how to build a cookie consent module in the Hyvä theme that satisfies both GDPR requirements and CSP restrictions at once, without nonce violations and without loading third-party scripts before consent is given.
-
Jun 15, 2025
The standard filters that ship with admin UI components cover most grids well, but they hit their limits fast once you need value ranges, dynamically populated option lists, or business-specific edge cases. Understanding how filter declaration, the frontend component, and the collection modifier interact lets you add any filter type cleanly instead of hacking around the grid with client-side JavaScript.
-
Jun 15, 2025
Whether Magento Cloud or Self Hosted is the right choice depends less on trends than on concrete numbers: total cost of ownership, traffic patterns, existing DevOps competence and how flexible a team needs to stay for deployment and scaling. This decision guide provides the criteria for a well founded choice.
-
Jun 14, 2025
Teams that only discover multi-store bugs in staging lose time and trust. A local multi-store development environment with its own domains, real store views and store-specific configuration values exposes bugs that a single-store instance would never surface.
-
-
-
Jun 8, 2025
Multipart uploads in GraphQL are technically possible, but in practice they cause more problems than they solve. Anyone uploading files through GraphQL ends up fighting proxies, body size limits, missing caching, and resolvers that are hard to test. This article explains where the real limits lie and how presigned URLs solve the problem more elegantly.
-
Jun 8, 2025
In most agency projects, attribute sets grow uncontrolled: every new product type gets its own set, naming conventions are missing, and after two years nobody can say which of the eighty sets are actually still used in production. Teams that instead align attribute sets with product types and business requirements before creation, generate them programmatically through Data Patches and keep them under a clear governance process, keep the EAV structure maintainable, performant and comprehensible for new developers.
-
Jun 8, 2025
An API-first architecture reverses the classic order of software development: instead of building a user interface first and treating data access as an afterthought, a stable, well documented API comes first, from which any number of frontends, from the classic storefront to a mobile app, can be served. For Magento 2 that means a deliberate break from the monolithic core architecture, in which frontend rendering and business logic are traditionally tightly interwoven. This article shows what an API-first architecture for Magento 2 looks like in practice, where sensible microservice boundaries run, and how an existing store can migrate there step by step.
-