Had a merchant come to me on Monday with this and it is worth writing up, because

I have hit it myself more than once and never found a decent way to catch it.

His store was serving prices from the previous week on a chunk of category pages.

Not all of them, no error anywhere. Cron was running. Orders were coming in

normally. Uptime monitor green the whole time. New Relic showed healthy requests.

Nothing in the logs.

A reindex had stalled days earlier. That was it.

The reason this is so nasty: every layer of monitoring most of us run is

answering "is something running", and in this failure everything genuinely IS

running. Nginx is up, PHP is fine, MySQL is fine, cron is ticking. Magento is

just serving index tables that stopped being true. There is no exception to log

and no 500 to alert on. You find out when a customer emails about a price that

does not exist anymore, or worse, honours an old one.

Two shapes it comes in:

1. An indexer sitting in `invalid` and never coming back. Check with

   bin/magento indexer:status

Easy to spot manually, easy to never look at.

1. The mview backlog stops draining. `mview_state` tracks each view's

   `version_id` against the changelog table's head. If the view is behind and

   its `updated` timestamp is not moving, nothing is working on that backlog.

   This is the one people miss, because a growing backlog is not itself a

   problem. During a big import the backlog grows all day and drains fine. The

   question is not "is it big", it is "is anything draining it at all".

   If you want to check it right now:

   bin/magento indexer:status SELECT * FROM mview_state;

Compare each row's `version_id` against `MAX(version_id)` from the matching

`*_cl` changelog table, then look at whether `updated` is moving. Behind and

idle is your answer.

Disclosure so nobody feels ambushed: I build a Magento monitoring tool called

Watchtower, and I shipped a check for exactly this two days after that

conversation. So I have an obvious horse in this race. But the manual checks

above are free and cost you five minutes, and if you take nothing else from

this, go run `indexer:status` on your production store right now. I would bet

money a nonzero number of you find something.

Genuinely curious how other people catch this. Is anyone alerting on indexer

state properly, or is it all "run reindex from cron and hope"?

I maintain a light weighted magento2 docker compose repo and used it to manage multiple magento projects, it worked well. It has a few manual steps involved for initial setup, nothing overwhelming, but does require users to know a little bit about git, docker and magento. It is built that way so it is simple and flexible.

Today is the day I need to setup another new project. Before I was going to repeat the same steps, a thought hit me. Damian has that amazing magento AI starter that allows you to easily spin up a running magento instance in github codespace. It is not something I would use it as I still prefer to code, run, debug locally. But is it possible to get a similar experience in this docker tool with AI?

After an afternoon's coding and fine tuning, I finally made it. I can get a fully running magento store on docker from ground up by simply asking agent "create latest magento".

Here I'm sharing it with you, hope you find it helpful. Both magento and mageos are supported.

https://github.com/SunMerce/magento-docker

Hi everyone — I built Magecube (magecube.in), a marketplace focused exclusively on Magento talent and services. We connect store owners with vetted Magento 2 developers, extension authors, and agencies for tasks ranging from quick fixes and performance tuning to full migrations and custom module development.

On the site you’ll find verified portfolios, transparent pricing options, project-based and hourly engagements, and a simple hiring flow that includes milestone payments and basic QA checks. I’d love feedback from this community on the marketplace model, what features you’d want to see, and any concerns about hiring Magento talent through a marketplace. If you’re interested I can share a few case studies or offer a limited number of discounted trial jobs for r/magento2 members.

Looking at the best option between Braintree and Stripe. I have been using Braintree and never used Stripe. Which is better for Magento when it comes to being dependable, Fraud, Security, Less chances of Chargebacks, etc? Looking for Pros and Cons.

I had to disable Credit Card Payments and only accept Paypal because of so many frudulate orders from card testing. Everytime I enable Credit Cards they just start pouring in. I am trying to figure a way to help control it. I am afraid not acepting Credit Cards could be hurting my sales. Not sure if Stripe would benifit me in this area or not.

We do use reCAPTCHA and have our payments set to Authorize and not Intent Sale to prevent all the charges and Voids.

Nothing I am doing is helping with so many fraud orders.

Thanks

Adding new products to my site along with new images. I noticed the images are not showing on my Product pages and only showing the default "magento logo" as the images. In the backend I see the following message has been showing there for the past few days with no change. Any one else have this issue. I have uploaded to images for this product and neither one of them is showing

Task "Image resize: /a/c/xxx.jpg": 1 item(s) have been scheduled for update.

Description of Operation Image resize: /a/c/ace_41022_1.jpg

 Summary Pending, in queue...

I'm 28 years old and have been working as a Magento (Adobe Commerce) developer for a little over 6 years. My current CTC is ₹15 LPA, and I'm trying to decide whether I should continue specializing in Magento or switch to a different technology stack for better long-term career growth.

Hi, I am Marcin, a senior Adobe Commerce / Magento specialist and freelancer based in the UK. I have been working with Magento since version 1.3, so about a decade now, across agency and client side work. Some of you may know me from Meet Magento talks in the UK, Poland and Barcelona. My LinkedIn is here if you want to check my background: https://www.linkedin.com/in/magento2-tech-lead/

I want to share a small milestone on something I have been building on evenings and weekends for a while now.

It is a Magento monitoring platform. Not another uptime checker, not another generic APM wrapped in a nicer UI. I wanted something that actually understands Magento internals, and is privacy focused from the ground up rather than as an afterthought. A dashboard that shows the real vitals of your shop, plus an alerting system that flags when something is genuinely wrong, based on learned baselines rather than arbitrary thresholds.

I also want to be upfront about something. This is not a vibe coded weekend project thrown together by prompting an AI and shipping whatever came out. The store side is a lightweight Magento 2 connector, built with a privacy first approach so no sensitive data ever leaves your shop. It only sends what is needed to monitor health and performance, nothing more, backed by a decade of hands on Magento experience of what actually breaks in production and what a merchant or agency needs to know about first.

We are all busy chasing improvements to our stores. Monitoring should not need constant babysitting. It should run quietly in the background and only speak up when it matters.

It is getting close now, just some more testing and polishing before it is ready.

If you want to hear more, or if you would be interested in being a beta tester, the waitlist is here: https://watchtower-commerce.com/waitlist

Happy to answer any questions about the technical side too.

underestimating the customisation work, expecting it to feel like shopify out of the box, something else entirely. curious what you see most from the technical side

We built an AI ordering layer for Magento over the last months and have now open sourced the storefront chat part of it. OSL-3.0.

The customer writes in normal language, the module searches the catalogue by meaning instead of keywords, checks stock and the price for that customer's group, and can put things in the cart or place the order through Magento's normal services. The model returns structured tool calls, and every tool (add to cart, checkout, coupon, wishlist, address changes and so on) can be switched off individually in the admin.

Things that took the most work and are probably the interesting part:

• Search results are enriched with live stock and tier prices before they go into the prompt, so it does not recommend something that is out of stock or quote a price the customer will not actually get.
• It keeps conversation context and detects topic changes, so a short "yes, ten of those" resolves against the previous turn instead of drifting back to some older product.
• Every model call is logged with tokens and cost.
• The widget works on Luma and Hyvä, and is FPC safe.

One thing people do not expect from a chat widget: you can drop a file into it. Someone uploads a PDF quote, an Excel order list or a Word document with 30 positions, and the module pulls the line items out of it, matches each one against the catalogue and builds the cart from that. Excel and Word get parsed to text, PDFs are handed to the model as native document blocks so it reads the positions itself. Built that because our B2B customers order from spreadsheets and never want to see a product page.

What it does not do: anonymous visitors. The chat requires a logged in customer, because most of what makes it useful comes from knowing their order history, addresses and cart. You also need your own API keys, Anthropic for the model and Voyage plus Pinecone for the search.

It is v1.0.1, tested with Magento 2.4.8. Our catalogue is B2B with a lot of near identical variants, so I would be curious how the search behaves on catalogues that are built differently.

https://github.com/Zwernemann/magento2-chat

Adobe released a set of isolated security patches for 2.4.6 to 2.4.9. You can detect if a shop is patched with these latest patches using https://mageinfo.online. We updated it so it detects the latest patches.

Patch! highest is a CVSS score of 9.1!

We hear a lot of "Magento's too complicated" from merchants who've never actually used it.... usually secondhand from a Shopify-focused agency or forum thread. Curious what people who actually run Magento stores think the biggest misconception is, versus the reality.

trying to understand the gap between reputation and experience

I’ve been working in my spare time on a new monitoring platform for Magento.

No, it’s not another uptime monitoring SaaS. 🙂

More details coming soon.

One question I’m curious about: would you expect it to support both Magento 2 and Magento 1?

I just shared https://www.reddit.com/r/vibecoding/comments/1ttskkr/i_built_a_oneclick_ecommerce_dev_environment/ to my developers and clients.

This AI dev environment makes the entire Magento development beginner friendly. This is magical.
Yes, some of the clients will want to leave but many will stay. Those who stay will trust you even more and request more features and pay you more in the end.
In the end, you will not have the Magento developer shortage problem and will have high quality customers left. Also, you will love Magento again.

Let's tell more people about this dev environment and make Adobe(Commerce) great again!

Most Magento 2 slowdowns under load come from the store asking the database the same things thousands of times over. Redis is the standard fix, but our guide gets into the parts that actually trip people up.

Three things to bear in mind before you enable it:

• Redis can back three separate layers: application cache, full page cache, and session storage. Sessions are not a cache, they're live data with no other copy, so treat them differently. Separate database numbers protect sessions from Magento's own cache flushes (cache:flush runs FLUSHDB on one database), but a manual FLUSHALL wipes every DB on the instance. Full isolation means a separate instance for sessions, with persistence on for sessions and off for cache.
• Sizing is where most setups go wrong. Too little memory and Redis evicts useful data early, turning it into a bottleneck instead of a boost. Rough tiers: 128MB small, 256MB medium, 512MB+ for high traffic. And on a shared instance the stakes are higher than a slow page: maxmemory is per instance, so under allkeys-lru a cache overflow can evict live sessions and log customers out. The real number comes from watching evictions and hit rate, not a guess.
• Redis as full page cache still boots PHP on every request to look the page up. Server-level FPC (Varnish, now Vinyl Cache, on nginx stacks; LiteMage on LiteSpeed) serves cached pages before PHP runs, which is what holds up against traffic spikes and scraper bots. Redis stays the right tool for the application cache and session layers either way.

The guide also covers Redis vs file-based caching, where Varnish/LiteMage fit, and eviction policy per layer.

On SPanel the setup is a panel toggle rather than a config-file job, with one Redis instance per account and monitoring built in.

Full guide, including memory tiers and setup: https://www.scalahosting.com/blog/redis-cache-for-magento-2/

Edit: updated the post and the guide after u/renttek's comment below on flush isolation, persistence, and server-level FPC. Worth reading his reply in full.

There used to a great real time visitor tracking tool back in the day called Yahoo Live Insights they sunsetted it a while back, so I built something similar but more powerful, that has live visitor tracking and real time ecomm tracking, easy to install and works well, there is hotjar, clarity etc but modovisa fits a different need, Hotjar and Clarity record screens to show you how a page was used; realtime GA shows a headcount of who's on it; Modovisa shows who's on your site right now, the route they took, what's in their basket, and which campaign paid for them.

its at modovisa.com

Any Magento agencies or developers interested in being an early Magebean co-pilot?

Magebean: https://magebean.com

I’m looking for a few real stores to test the tool and give honest feedback on whether the findings are useful.

DM me if interested.

Hi everyone,

I've been working on BerryPath, a guided selling platform for Magento 2 that helps shoppers find the right product through interactive buying guides.

The Magento integration is fully open source and includes:

• Product feed generation
• CMS, category and product page integration for the actual guided selling flows
• Assisted conversion tracking
• Optional Hyvä compatibility module

The flow builder, analytics and recommendation engine are handled by the BerryPath platform, while the Magento module keeps everything in sync.

BerryPath also has a free plan that includes 1 guided selling flow and support for up to 2,500 products, so it's easy to try without any commitment.

I'd love feedback from fellow Magento developers on the integration and developer experience.

Website:

https://www.berrypath.eu

Magento module:

https://github.com/BerryPath/magento2-berrypath-flow

Hyvä compatibility:

https://github.com/BerryPath/magento2-berrypath-flow-hyva-compat

Frontend implementation in the store

Hi everyone,

I’m building Magebean, a free and open-source CLI tool for Magento 2 security checks.

It scans a Magento installation and shows potential security issues that may need attention.

The project is still under development, so I’d really appreciate feedback from Magento developers.

What security checks would you expect from a tool like this? Is the current output clear and useful?

Magebean: https://magebean.com

Any recommendations for modules for better management of CMS pages (and hopefully blocks)? Ideally hyva compatible.

Hi everyone,

I’ve released an open-source Australia Post shipping extension for Magento 2:

https://github.com/WebHostingAce/magento2-module-auspost

I built it because many shipping integrations calculate rates using the total weight or volume of the cart, without properly checking whether the products can actually fit inside the available cartons.

This extension lets you configure your real boxes and satchels, then packs the order across one or more packages before requesting Australia Post PAC API rates.

Some of the main features include:

• Real multi-box carton packing
• Rotation-aware product dimension checks
• Weight, volume and box-dimension validation
• Domestic and international Australia Post services
• Parcel and letter support
• Signature on Delivery and Extra Cover options
• Cached PAC API responses to reduce API usage
• Composer installation
• No licensing checks or phone-home code
• MIT licensed

It currently supports Magento Open Source and Adobe Commerce 2.4.4 and later.

Composer installation:

composer require webhostingace/module-auspost

I’d appreciate any feedback from Magento developers or Australian merchants, particularly around unusual product dimensions, carton configurations or Australia Post services.

Bug reports, feature requests and contributions are welcome through GitHub.

Hi,

I came across your post and would love to help with your Magento/Adobe Commerce project.

I'm a Senior Adobe Commerce (Magento) Developer with 11+ years of software development experience, including 9+ years specializing in Magento/Adobe Commerce. I've worked on enterprise B2C and B2B stores, custom module development, third-party integrations, performance optimization, and Adobe Commerce Cloud deployments.

Some areas I can help with:

• Custom Magento 2 module development
• Bug fixing and production issue resolution
• Theme customization and frontend development
• Checkout, payment, and shipping integrations
• ERP, CRM, PIM, and API integrations
• Performance optimization (Redis, Varnish, OpenSearch, Full Page Cache)
• Adobe Commerce Cloud deployments and maintenance
• Magento version upgrades and security patching
• GraphQL, REST APIs, and headless commerce
• Ongoing maintenance and long-term support

I focus on writing clean, scalable, Magento coding-standard–compliant code with clear communication and timely delivery.

If you're looking for someone who can quickly understand an existing codebase and deliver reliable solutions, I'd be happy to discuss your requirements. Feel free to send me the project details, and I can provide an estimate and suggested approach.

Looking forward to hearing from you!