WooCommerce Cart Page Not Loading
After a Malware Infection
A live fashion store where customers could browse products but never buy them. The symptom was a WooCommerce cart page not loading at all, with the account page dead alongside it. The cause was not a WooCommerce setting. Here is what we found on ahfcollection.com and how we brought it back.
A Shop That Browsed Fine and Sold Nothing
The homepage worked. Category pages worked. Individual product pages loaded normally, complete with images and prices. From the outside, ahfcollection.com looked like a functioning store. A WooCommerce cart page not loading rarely announces itself on the front page.
Then a customer clicked through to check out, and nothing happened. A WooCommerce cart page not loading is a particularly expensive fault precisely because the rest of the site keeps behaving, so nothing looks obviously wrong from the admin dashboard. Traffic still arrives, product pages still get views, and analytics keeps reporting sessions. The only signal is that orders have stopped completely.
The My Account page was down as well. That detail mattered more than it first appeared, because two separate pages failing at once usually rules out the easy explanations.
Why two dead pages narrows it fast: with only a WooCommerce cart page not loading, the likely cause is that page’s own shortcode or block. When the cart and the account page fail together, the fault is in something they share — session handling, or the core files both depend on.
Why the WooCommerce Cart Page Not Loading Was a Security Problem
The site was infected. Malware had been injected into the WordPress installation, and it had taken the transactional pages down with it — the WooCommerce cart page not loading was a downstream symptom, not the fault itself.
That pattern is not a coincidence. Injected code tends to concentrate on the pages that handle payment data and logged-in sessions, because those are the pages worth compromising. A storefront that still browses while checkout is dead is a recognisable fingerprint of an infection rather than a configuration mistake, and it is why we treat a WooCommerce cart page not loading as a security question before a plugin question.
We checked the site manually rather than trusting a scanner’s summary. Automated scanners are useful for the first pass, but they report what they recognise, and a clean scan on a site that is visibly broken tells you very little.
Two Fixes That Brought the Store Back
Two pieces of work resolved it. Neither was a WooCommerce setting, which is worth stating plainly, because a WooCommerce cart page not loading sends most people straight into the plugin settings first.
- 01Full malware cleanupWe removed the injected code across the installation — not only from the two pages that were visibly broken. Cleaning the symptom and leaving the rest of the infection in place means the site reinfects itself within days, which is the most common reason a “fixed” site breaks again a week later.
- 02Clean core file restoreCompromised WordPress core files were replaced with clean official copies, rather than rolled back from a backup. A backup restore is faster, but only safe if you know it predates the infection — and most site owners genuinely do not. Replacing core files with known-good versions removes that guesswork.
With clean files in place, the WooCommerce cart page not loading resolved on its own and the account page rendered again. We then walked the entire purchase flow by hand — add to cart, view cart, checkout, account login, order confirmation — because the only meaningful test of a restored shop is completing a real order in it.
If Your WooCommerce Cart Page Is Not Loading Right Now
Work through these in order before assuming the worst. Most cases of a WooCommerce cart page not loading turn out to be one of the first three, and those are ordinary faults, far more common than an infection.
A 5-step triage for a dead cart page
Run these on a staging copy if you have one. If you reach step 5 and the pages are still dead, stop guessing and get the site looked at.
- Confirm the page still holds its shortcode. WooCommerce needs the cart block or the cart shortcode present on the assigned page. Page builders sometimes strip it during an edit.
- Check WooCommerce’s page assignments. Under WooCommerce settings, verify Cart and My Account point at the pages you expect and not at a deleted draft.
- Test for a plugin or theme conflict. Switch to a default theme and deactivate plugins one at a time. If the cart returns, you have isolated it.
- Turn on debug logging. A silent white page is almost always a PHP fatal error. The log names the file causing it.
- Compare core files against a clean install. Download the matching WordPress version from the official release archive and diff it. Unexpected files or modified core files mean you are dealing with an infection.
The official WooCommerce pages documentation covers the configuration side of this properly. If your setup checks out there and the cart is still dead, the problem is not configuration.
Cleanup Is Not the Same as Prevention
Removing an infection does nothing about the weakness that allowed it in. Once ahfcollection.com was trading again, we put the same protections in place that we apply after every cleanup: two-factor authentication and strong passwords on every admin account, a real backup schedule rather than whatever the host does by default, automatic updates for core and trusted plugins, and a file-integrity check so a fresh infection surfaces in days instead of months.
Malware is not a sign of a badly run business. It usually arrives through a single outdated plugin on an otherwise well-maintained site. What separates a bad outcome from a manageable one is how quickly it is caught — and a WooCommerce cart page not loading is often the first symptom an owner actually notices, long after the entry point was created.
WooCommerce Cart Page Not Loading: Common Questions
The common causes are a missing or damaged cart shortcode on the page, a plugin or theme conflict, a PHP error stopping the page from rendering, or corrupted core files. When the cart and the account page fail together while the rest of the shop works, the cause is usually something shared by both, which points at core files or the session handling rather than at the individual pages.
Yes, and it is more common than people expect. Injected code frequently targets the transactional pages, because those are where payment data and logged-in sessions live. The result is a storefront that still browses normally while checkout is completely dead, which is why site owners often do not realise the cause is an infection.
Only if you are certain the backup predates the infection. Restoring a backup that already contains the malicious files simply reinstates the problem, and most site owners cannot pinpoint the infection date. On this project we replaced core files with clean official copies rather than rolling back, so we knew exactly what was being restored.
The cleanup itself is usually the quick part. The slow part is verification, because you have to confirm every template, plugin, and core file is clean before you can trust the checkout again. We manually walked the full purchase flow end to end rather than relying only on an automated scanner.
Cleanup does not address the vulnerability that allowed entry. After recovery we put the same basics in place: strong passwords with two-factor authentication on every admin account, a genuine backup schedule, automatic updates for core and trusted plugins, and a file-integrity check so any new infection is caught in days rather than months.
Is Your Checkout Down
Right Now?
If you have a WooCommerce cart page not loading and you are losing orders while you read this, message us. We will tell you whether it looks like a configuration fault or something worse — before you commit to anything.