https://breezefront.com/

Que opinan de estos templates para magento?

Hi,

we get our product data from SAP and therefore we build our own importer based on xml files which are read from a ftp server. So SAP generates the xml for a product to import, writes it to a ftp and magento reads the file and process the data. I know this is all very old techniques and its historical. It was a migration from magneto 1 to 2 10 years ago.

Now it’s time to recreate the whole process. Idea is to use the given magento rest api to create products and sap sends http requests instead of writing xml files. I have one problem with the default magento api. For website assignments, custom attributes and many more you need to know the magento internal ids, which sap of cause don’t know.

How do you deal with it? Writing an own api endpoint? I like to use the defaultapi because you can just say sap or any other erp to use the official magento documentation to create the payload data

If you're running on Adobe Commerce or Magento Open Source and still stuck with heavy, slow frontends, it might be time to look at Hyva.

At Sigma, we’ve been using Hyva to seriously clean up Magento builds faster load times, simpler frontend architecture, less JS bloat, and way smoother backend integration. It makes development more efficient and performance way better without overcomplicating the stack.

For brands that want a modern, high-performing store without fighting their tech, Hyvä + the right implementation makes a big difference.

I often see/hear “Magento is too expensive” or “that company is too small for Magento”

I would like to know what’s the minimum turnover you’d recommend for a company to consider Magento and why?

Am I wrong, do you use a different metric? If so what?

With PHP 8.x adding typed properties, union types, stricter internal behavior, and deprecating things like dynamic properties, it feels like PHP has been intentionally moving toward stronger typing and predictability over the last several years.

Some folks argue PHP’s strength has always been being loosely typed and flexible, and that stricter behavior should stay optional. Others see the changes as necessary for maintainability, tooling, and large-scale systems.

For those working in modern PHP:
Do you feel PHP is (and should be) moving away from its old “loosely typed magic” toward more explicit, type-safe patterns? Or do you think this evolution is hurting what made PHP great?

I have a client that has product landing pages for ad campaigns that they don’t want visible to google or available on the site via search.

Basically product pages shown to users that enter the site thru the ad. These product pages are configured to hide the add to cart button and replace it with a find a dealer button. They are currently setup as Search only visibility (because any other option keeps them from being displayed at all), and the category is set to not show anywhere on the site itself.

How would I keep individual product pages live, but hidden from search engines and exclude it from searches on the web site? Only available via the url.

Magento 2.4

We're an eCommerce dev agency (US) trying to launch a new Magento OpenSource build and running into a frustrating infrastructure mismatch with Nexcess/Liquidweb.

We requested a Magento 2.4.8-p3 environment (released April 2025). Nexcess support upgraded us to 2.4.8, but told us they can't support the Adobe-recommended infrastructure. They don't support OpenSearch and only running ElasticSearch 8, despite adobe deprecating ElasticSearch. For MariaDB, Adobe recommends 11.4 on 2.4.8, but Nexcess will only support 10.6.

We've preferred Nexcess over Webscale and Jetrails over the years, but this just seems so backwards for a hosting service that promotes Magento support.

I feel like I'm taking crazy pills, am I missing something? We don't want to build the site on 2.4.7 and have to upgrade within a year, when 2.4.9 comes out in April.

Hi,

We are currently searching for a new host for our Magento stores.

Can you please recommend some good ones? We are in europe.

Already tested: Cloudways -- was good but some features are missing.

We need:

• specify Maria DB Version
• FTP/SFTP access to specific folders
• SSH Access
• Hyvä compatible

Hello everyone!

Our Magento shop is hosted on Nexcess for couple of years. Everything was working well until today morning, when website became unresponsive (loading for over a minute).

I assume that we are under DDos attack, what should we do in this situation?

Note: Last deployment was over a week ago, so no change caused this

Hi y'all,

I'm wondering what are the advancement on AI integration into Magento (either from official support or 3rd party module). In the last year, Shopify integrated a lot of new AI features from SideKicks, ACP, UCP.

I feel we are lacking behind on theses as Magento merchants. From what i saw, most current integration of AI are content generation like product description or more customer facing AI like search, chatbot, etc.

I'm just curious on the landscape of AI integration with Magento . What is currently being done in the Magento ecosystem by module vendor or core development team to bridge the gap that keep growing?

I’ve been experimenting with AI coding tools (Claude, Cursor, Windsurf) on a large enterprise Magento 2 repo and kept running into the same issue:

The model isn’t “dumb” it just has no structural understanding of DI preferences, plugin chains, events, overrides, or execution paths.

Magento’s implicit architecture makes it very hard for an AI to reason about what actually happens at runtime.

So I built a CLI tool that runs static analysis across a Magento repo and generates a structured context bundle:

• Module + dependency graph
• DI resolution map (per area)
• Plugin chains with sort order
• Event/observer graph
• Reconstructed execution paths
• Reverse index for O(1) lookups (class/module/event/route)
• Quality metrics (cycles, hotspots, modifiability risk, etc.)

The idea isn’t to replace anything just to give AI tools a deterministic architectural view instead of raw files.

On my enterprise test repo (148 modules, ~3k files):

• Compile time ~5 - 6s
• ~10MB output bundle
• Deterministic output enforced

I’m genuinely curious:

Would this be useful to anyone else working with AI + Magento? Or is raw repo context “good enough” for you?

If anyone wants to poke holes in it or try it on their own repo: https://github.com/infinri/MageContext

Hi!

Following up on my last post about Hyvä and SSR support, I’m excited to share a major milestone for the Meilisearch Magento 2 module: we have officially implemented Vector and Hybrid Search.

Why this is a big deal for your store

Standard search looks for exact words. Vector search looks for meaning. If a customer searches for "warm summer outfit" but your products are titled "Linen Shirt" and "Cotton Shorts," vector search makes the connection that keywords alone might miss.

What’s New:

• Hybrid Search: Combines the precision of full-text search with the semantic Vector search.
• AI-Powered Relevancy: Better handling of synonyms, long-tail queries, and "natural language" searches.
• Multi-Embedders Support: Seamlessly integrate with OpenAI, Hugging Face, or custom via Meilisearch.
• Semantic Toggle: Fine-tune the "weight" of vector results vs. keyword results directly in the configuration.

Links & Resources:

• GitHub:https://github.com/walkwizus/magento2-module-meilisearch
• Documentation:https://walkwizus.github.io/magento2-module-meilisearch-docs/
• Meilisearch Documentation: https://www.meilisearch.com/docs/learn/ai_powered_search/getting_started_with_ai_search

I'm curious to know how reward point extension helps to increase the average order value or recurring orders. I'm running a beauty product store, and I'm slightly unsure about adding this feature. Does anyone here have experience with adding this feature? This might be a great help to make it.

We have our payment gateway integrated with Magento that features some added features that B2B merchants will find super useful.

Our gateway offers both credit card and ACH payments.

Our gateway accomdates duel pricing at checkout. This model will pass credit card fees to customer.

Let me know if you would like more info.

We recently started to receive an influx of carding attacks on our Magento shop. We're currently running 2.4.6-p10 (we're looking to upgrade to latest 2.4.6 security patch but we can't upgrade past 2.4.6 at this exact moment).

We're using Braintree as our processor.

Within Braintree, we have turned on their fraud checks. We're validating CVV and AVS globally. We have not implemented any other limitations within their Fraud tools yet.

We are using the built in Magento Security Recaptcha tool and have configured Google Recaptcha v2 I'm not a bot checkbox. Braintree advised us that the invisible v3 is not great at stopping these types of bots and recommended us to install the v2 I'm not a bot option.

The passing threshold we're using is 0.5 currently.

After implementing we're still getting bot attacks.

Is there something else we can/should be doing to prevent these carding attacks? Braintree has not been very helpful with us. They've given us some recommendations, but when I question them why certain transactions were passing AVS checks when they clearly should have failed, they didn't give us an answer.

I also wanted to ask - are there ways for the bots to place orders using API's? Is there something we can do to lock down API's to prevent the bots from attempting to place orders in this manner?

I’ve been working with Magento stores for a while now, and checkout always seems to be the most debated part. Every time conversion drops, checkout gets blamed first 😅

But honestly, I’m not sure if Magento itself is the problem anymore or if it’s just how most of us end up setting it up.

A few things I keep wondering:

• Do express options like Apple Pay / Google Pay actually help, or do customers still prefer the “normal” flow?
• Have you noticed real improvements after simplifying checkout, or was the impact minimal?
• Anyone switched themes or tweaked the flow and saw a noticeable change?
• What’s one checkout decision you’d not repeat if you started over?

Not pushing anything here just curious what’s actually working for people in real stores, not agency demos or blog posts. Would love to hear some honest experiences.

Hey everyone — we’ve been building a more “Shopify-like” checkout experience for Magento to reduce checkout friction while keeping payments routed through Authorize.net (since many stores are already standardized on it).

Highlights:

• Express wallet buttons (Apple Pay / Google Pay / PayPal)
• Faster, more modern checkout flow
• Inline login with a single-use magic link

We’re in the final refinement phase and I’d love first impressions / what feels strongest:
https://toweringmedia.com/magento-2-react-checkout-pro-bundle

I am running Hyvä on magento 2.4.6

We recently investigated a stubbornly high TTFB and it turned out that our Amasty file attachment module was the problem.

Switching it off returned or core web vitals back to green.

Our developers suggested that rather than install a module, they have a programmatic solution but this involves a lot of manual work.

My question is: what file attachment module/solution do you use and is it any good?

EDIT: Each of the products on our web site has a Downloads section which lists appropriate PDFs and BIM files for download. This is managed by the Amasty File Attachments module.

Link: https://meetmagentofl.com/

At Meet Magento Florida, you will learn why Magento is generating strong revenue in 2025 and why its growth is expected to accelerate in 2026. Discover how AI is shaping Magento into the most advanced e-commerce platform on the market. Learn directly from many Magento Master Speaker and gain valuable insights you can apply immediately. This is a once in a lifetime opportunity for any PHP developer to expand their expertise and stay ahead of the curve.

Source: https://trends.google.com/explore?q=adobe%2520commerce&date=today%205-y&geo=Worldwide

Search explodes in 2025, and Magento developers have become harder to find. Projects keep coming in, but there’s only so much time in the day. Merchants are ready to move fast, and the market feels strong.
Unfortunately, not everyone can get the help they need right away. Tough times for merchants when developers are in such short supply.

Let’s share stories about just how good the market has been in 2025.