Skip to content
MAGENTO

Common Magento Issues and How to Fix Them

The failures we see most across 800+ supported stores: what causes them, how to fix them, and which ones mean stop and call someone.

Shane Blandford
Shane Blandford · FOUNDERPUBLISHED · 2 MIN READ

After supporting Magento stores since 2008, the surprise isn't how many things can go wrong - it's how often it's the same short list. Here are the issues we see most, what actually causes them, and the fix.

500 errors and the white screen

Usually one of: PHP memory exhaustion, corrupted generated code, or file permissions after a bad deploy. Check the exception log first (var/log/exception.log), clear var/generated on staging and re-deploy compiled code properly. If it appeared right after a deploy, the deploy is the cause - roll back first, diagnose second.

Checkout or payment failures

The most expensive failure mode, and usually a conflict: a payment gateway module update, an extension patching the checkout, or an expired API credential. Reproduce it in an incognito session with a test card before touching anything - half of reported checkout bugs are actually a single payment method failing quietly.

Cron stopped running

When emails stop sending, indexers pile up, and scheduled prices never apply, check cron before anything else. It fails silently and takes half the platform's plumbing with it. Verify the crontab exists, then look for a stuck job holding the queue.

Extension conflicts after an update

Two modules patching the same class, or one module built for an older core. The tell is a feature that broke the same day something else was updated. The fix is isolating the pair on staging - which is also the argument for having staging at all.

Cache and Redis trouble

Stale prices, phantom content, sessions dropping: usually a cache that isn't flushing correctly or a Redis instance out of memory. Check Redis eviction settings - a session store evicting keys logs customers out mid-checkout.

Signs the store is compromised

Unfamiliar admin accounts, JavaScript you didn't add on the checkout, or customers reporting card fraud. Stop and treat it as an incident: malware scan, patch the entry point, restore from a clean backup. Speed matters more than tidiness here.

If an issue on this list is costing you sales right now, that's what our Magento bug fix service and emergency support exist for - a developer on it within 3 hours. And most of these are preventable: the same failures come up again and again on stores without routine patching and monitoring.

FAQ

Why is my Magento site showing a white screen?+
PHP is failing before it can render an error page - memory limits, broken generated code, or permissions. The exception log will name it.
Why did my Magento checkout stop working?+
Most often a payment module update or expired gateway credentials. Test each payment method separately - it's frequently just one.
Why is Magento not sending emails?+
Check cron first. Magento queues mail and cron sends it; a dead cron looks exactly like a broken email server.
Can these issues be prevented?+
Mostly, yes. Nearly every emergency we take on was preventable with routine patching, monitoring, and a staging environment.
Shane Blandford

Shane Blandford

FOUNDER

Founder of Orange Collar Media, a Denver ecommerce agency behind 800+ Magento and Shopify builds. In Magento since version 1.x - building, rescuing, and supporting revenue-critical stores since 2008.

All posts by Shane Blandford

KEEP READING

Related from the Journal.

Your store can sell more. Let's find out how much.

Start a project