To find WooCommerce logs, open WooCommerce > Status > Logs in WordPress. Select the source and date that match the failed event, then search the message fields for an order number, gateway, endpoint, plugin slug, or distinctive error. If the WooCommerce logger does not contain the PHP failure, enable WordPress debug logging with display disabled and inspect wp-content/debug.log.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This guide explains how to turn logging on, choose file or database storage, reproduce and isolate checkout failures, interpret every severity level, protect customer data, and escalate server-level problems safely.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What WooCommerce logging covers
WooCommerce’s logger records diagnostic messages generated by WooCommerce and by extensions that use its logging system. Payment gateways, checkout processes, webhooks, scheduled actions, imports, exports, REST requests, and other background jobs may all leave entries. A log entry is evidence about what a component reported at a particular time; it is not necessarily the original cause of a failure.
There are two related but separate layers of diagnostics:
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
- WooCommerce Logs in the WordPress dashboard contain messages written through WooCommerce’s logger. They are the first place to look for an order, gateway, webhook, or extension event.
- WordPress’s PHP debug log contains PHP notices, warnings, fatal errors, and plugin or theme errors that occur outside WooCommerce’s logger. Its normal location is
wp-content/debug.log.
A checkout can therefore fail with no useful WooCommerce entry if the problem occurs before WooCommerce initializes, in a PHP extension, in the web server, or in a payment provider’s remote response. Use the layer that covers the failing component rather than assuming every error will appear in one screen.
Open, select, and search a WooCommerce log
- Sign in to WordPress with an account that can manage WooCommerce.
- Go to WooCommerce > Status > Logs. The official interface lists available log files or database-backed entries by source and date.
- Choose the source associated with the event. Typical source names identify WooCommerce, a payment gateway, an integration, or an extension. Choose the date closest to the failure rather than opening the newest file automatically.
- Open the entry and use the search control for message fields. Search for a stable value: the order number, payment gateway name, REST route, webhook identifier, extension slug, or a distinctive phrase from the customer-facing error.
- Read the timestamp, source, severity, message, and context together. Do not diagnose from a single word such as “warning” without checking what operation was running.
Before reproducing a problem, write down the exact time in the site’s local timezone and in UTC if possible. Also record the affected order, customer action, checkout or account endpoint, browser or device if relevant, and the extension that should have handled the request. Reproduce the problem once, not repeatedly, so the resulting entries can be matched to one event instead of a noisy series of retries.
How to match an entry to a customer action
Compare the log timestamp with the moment the customer clicked Place order, the gateway returned, a webhook arrived, or a scheduled task ran. Then verify at least one identifier in the message or context. An order number is usually stronger evidence than a general phrase such as “request failed.” If several entries share a timestamp, follow the sequence from the initial request through validation, gateway communication, webhook handling, and order status changes.
Enable and configure WooCommerce logging
- Open WooCommerce > Status > Logs.
- Open Logs > Settings from the logs interface.
- Confirm that the WooCommerce logger is enabled.
- Choose a storage handler: File system or Database.
- Set a retention period appropriate for the store’s disk space, database size, privacy policy, and incident-response needs.
- Choose the minimum severity threshold. Selecting None records all severities, which is useful for a short diagnostic capture but can create substantial volume on an active store.
- Save the settings, reproduce the issue once, and return to the log list to locate the new source/date entry.
The threshold is a filter on what gets recorded; it does not repair a failing request. For a narrowly scoped investigation, begin with the normal threshold and temporarily select None only when the relevant component is not producing enough detail. Restore the normal threshold after collecting the evidence.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Understand WooCommerce’s severity levels
WooCommerce defines eight levels. The level describes the urgency assigned by the component that wrote the message, while the message and context explain the actual event.
| Level | How to use it while investigating |
|---|---|
| emergency | A condition requiring immediate attention because the system or a core function may be unusable. |
| alert | A serious condition that should be acted on promptly to prevent continued impact. |
| critical | A major failure affecting an important operation, such as order processing or a required integration. |
| error | An operation failed. Check the surrounding entries and the request context to identify whether it caused the customer-visible symptom. |
| warning | An abnormal condition that may not stop the request but can explain intermittent or future failures. |
| notice | A notable state change or condition that is not necessarily a failure. |
| info | Normal informational activity, such as a request, status transition, or completed task. |
| debug | Detailed diagnostic information intended for troubleshooting rather than routine monitoring. |
Severity is not a substitute for correlation. A recurring warning from the same source immediately before every failed payment is more useful than an isolated critical-looking message from an unrelated scheduled task.
File system versus database storage
WooCommerce provides two storage methods. Select one based on access, retention, backup, and security requirements; changing the handler does not combine histories.
| Characteristic | File system | Database |
|---|---|---|
| Where entries are kept | Log files in the site’s uploads/wc-logs directory by default. |
Rows in the {$wpdb->prefix}woocommerce_log table. |
| Dashboard access | Listed by source and date in WooCommerce > Status > Logs. | Listed through the same WooCommerce logs interface. |
| Retention behavior | Old files beyond the retention period are deleted as whole files. | Individual old entries are deleted when they exceed the retention period. |
| Rotation | A file can rotate at approximately 5 MB before a new file is used. | No equivalent per-file rotation applies; growth is in table rows and database storage. |
| Operational concern | WordPress must be able to create and write files; backups and filesystem permissions must include the log directory. | Database backups must include the WooCommerce log table; large volumes can add database storage and maintenance work. |
| History after switching | Existing entries are not migrated to the new handler and are not deleted by the switch. Investigate the previous location for incidents that predate the change. | |
File-system security and permissions
WooCommerce adds an .htaccess file intended to protect the wc-logs directory. The documentation warns that not every web server recognizes that file, so it is not a universal access-control boundary. When the hosting architecture permits it, place logs outside the public web root and retain permissions that allow WordPress to write them. Verify the result with your host rather than assuming a browser cannot request a log file.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Do not expose a log directory merely to make troubleshooting easier. Log messages can contain order data, email addresses, request payloads, stack traces, API responses, or other sensitive values.
How to read an entry without misdiagnosing it
Start with five fields: timestamp, source, severity, message, and context. Ask what request or job was active at that moment and which component wrote the line.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use stable identifiers
- Order number: ties the entry to one checkout and prevents mixing customers’ failures.
- Gateway name: separates a payment-provider response from cart, tax, or stock validation.
- REST endpoint or webhook route: identifies asynchronous calls that may occur after the browser has shown an error.
- Plugin or extension slug: points to the code path that generated the message.
- Distinctive error text: lets you find repeated occurrences across a source/date range.
Read several nearby messages when possible. The first error can be the cause, while a later “order failed” or “payment declined” entry is only the symptom. Conversely, a gateway’s rejection may be the primary event and a later order-status warning merely the consequence.
Interpret a fatal error carefully
If a source named for fatal errors appears in the WooCommerce log list, inspect it like any other entry: match its timestamp to the customer action, read the complete message and context, and note the file, function, or extension named. A PHP fatal error that occurs outside WooCommerce’s logger may not appear there at all; enable WordPress debug logging as described below and compare the same timestamp in wp-content/debug.log.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
When a payment or checkout failure has no useful entry
- Confirm the reproduction time and check all source names around that minute, not only the source you expected.
- Open the payment extension’s own settings and look for a separate logging or debug switch. WooCommerce’s logger is used by many extensions, but an extension may expose an independent enable control.
- Enable that extension-level logging for the shortest practical test window.
- Reproduce one checkout or webhook event and search by order number, gateway name, endpoint, and exact time.
- Disable the temporary verbose setting after collecting the evidence, then review the entry for secrets or personal data before sharing it.
A browser message such as “There was an error processing your order” is not a diagnosis. The log may show a declined transaction, a timeout, a malformed webhook, a stock or tax exception, or a PHP failure. The distinction determines whether the next contact should be the payment provider, the extension developer, or the hosting company.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Enable WordPress PHP debug logging for errors outside WooCommerce
WooCommerce-maintained debugging guidance recommends enabling the WordPress debug log while hiding errors from visitors. In wp-config.php, add or update these constants before the line that says WordPress has stopped editing:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchdefine( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );This configuration writes PHP diagnostics to wp-content/debug.log while keeping error output out of the storefront. The setting should be used in a controlled diagnostic window, preferably on staging or during a maintenance period for a busy store. Reproduce the problem once, note the timestamp, and inspect only the new lines associated with that request.
After the incident, restore the site’s normal production configuration. Leaving debug logging enabled indefinitely can consume disk space and retain sensitive request details. Never publish a raw debug file: remove customer information, payment data, authentication tokens, API keys, email addresses, and any personal data before sending a redacted excerpt to a developer or host.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Use Query Monitor and host logs when the dashboard is not enough
WooCommerce’s debugging resources recommend Query Monitor for deeper inspection in a staging or development context. It can expose database queries, PHP errors, AJAX and REST requests, hooks and actions, enqueued scripts and styles, and HTTP API calls. Use it to determine whether a checkout request reached the expected hook, whether a query failed or became unusually slow, and which HTTP call returned an unexpected response.
Do not treat a development diagnostic tool as a permanent public-facing feature on a production checkout. Restrict access, capture the evidence, and remove or disable it when finished.
Recommended Free Tools
For failures below WordPress—web-server errors, PHP-FPM crashes, request-size limits, TLS problems, process exhaustion, or blocked outbound connections—ask the host for PHP and web-server logs covering the same timestamp. Give the host the site timezone, UTC time, request path, order number if available, and the exact symptom. Matching timestamps across WooCommerce, debug.log, and server logs is often what separates an application bug from an infrastructure failure.
Troubleshooting by symptom
| Symptom | Most useful next check |
|---|---|
| No logs appear after reproducing a failure | Confirm the logger is enabled, verify the selected storage handler, check the source/date filter, and ensure WordPress can write the file directory or database table. If the extension has its own logging switch, enable it briefly. |
| The log list stops before the incident | Check whether storage was changed. Existing entries remain in the old handler, so inspect the former file location or database table. Also check retention and file rotation. |
| A payment fails but WooCommerce shows only a generic message | Search by order number and gateway, inspect webhook entries, and check the gateway extension’s separate logger. Compare the event with the provider’s dashboard using the same timestamp. |
| A fatal error breaks checkout or the admin | Compare WooCommerce entries with wp-content/debug.log. Identify the extension, theme, or PHP file named in the stack trace, then reproduce on staging before changing production code. |
| Logs contain no application entry at all | Ask the host for PHP and web-server records at the exact time. The request may have been rejected before WordPress loaded. |
| Logs are consuming too much space | Shorten retention, return the severity threshold from None to the normal minimum, remove old data according to the selected storage behavior, and check file rotation or database growth. |
Retention, rotation, and incident hygiene
Retention is an operational control, not a permanent archive. File storage deletes whole files older than the configured period, while database storage deletes individual old entries. Choose a period long enough to cover your support and reconciliation cycle, then verify that backups and privacy policies account for the retained data.
File logs can rotate at 5 MB. Rotation prevents one file from growing without bound, but it also means an investigation may span multiple files for a busy store. Preserve the relevant files before changing settings or allowing automated cleanup to run.
For every incident, keep a small, redacted record containing the reproduction time, affected order or endpoint, source/date selected, relevant severity and message, storage handler, and the configuration changes made. Do not attach a complete log to a ticket when a short excerpt proves the issue.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsA safe incident runbook
- Record the customer-visible symptom and exact local/UTC time.
- Note the order number, endpoint, gateway, extension, and whether the event was a browser request, webhook, scheduled task, or import/export job.
- Check WooCommerce > Status > Logs and select the matching source/date.
- Search for the stable identifier and inspect neighboring entries for the same event.
- If detail is missing, verify Logs > Settings, temporarily choose a broader threshold, and check the extension’s own logging option.
- If the error is PHP-level or absent from WooCommerce, enable
WP_DEBUG_LOGwithWP_DEBUG_DISPLAYdisabled and comparewp-content/debug.log. - For database, AJAX, REST, hook, or HTTP-call detail, reproduce in staging with Query Monitor.
- For requests that never reach WordPress, obtain host PHP and web-server logs for the same timestamp.
- Redact personal, payment, credential, and API-key data before sharing excerpts.
- Restore normal severity, extension, and WordPress debug settings, then confirm that the storefront still writes only the intended level of diagnostics.
What a useful log-based diagnosis looks like
A strong diagnosis connects a customer action to a repeatable sequence: an order or endpoint at a known time, an entry from the responsible source, a severity that reflects the condition, and context that explains the failed operation. It also states what the log cannot prove. For example, a gateway timeout entry establishes that WooCommerce did not receive a timely response; it does not by itself prove whether the provider, network, or server caused the timeout. Confirm that boundary with the gateway record or host-level evidence before changing checkout code.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
