Understanding the WooCommerce System Status Report

The WooCommerce System Status report is useful for troubleshooting issues with your store. Containing a wide variety of information and tools, you can check software versions, server settings, and more from within.

System Status #

To view your System Status report:

1. Go to: WooCommerce > Status.
2. Troubleshoot using the info below, before opening a ticket at Woo Support.
3. Click Get System Report and then Copy for support to copy/paste it into your Support Request, if you’re still having issues. The information included will help our support team narrow down the issue much quicker.

WordPress Environment

This provides general information about your site and WordPress installation and features you have enabled.

Server Environment

This provides general information about your server.

Database

This tells you your current database version, and lists all database tables and whether or not they exist.

Post Type Counts

This shows what post types exist on your store and how many posts exist within each type. Varies according to what plugins you have installed.

Security

Displays whether your connection is protected. Errors should be hidden from untrusted visitors trying to view your information.

To hide error messages, inside your wp-config.php file, look for the following line: define('WP_DEBUG', true);

Then you can replace it with the following:ini_set('display_errors','Off');ini_set('error_reporting', E_ALL );define('WP_DEBUG', false);define('WP_DEBUG_DISPLAY', false);

Active Plugins

This displays all plugins installed and active on your site. You can view current version numbers of your software and if any extensions have updates available.

Inactive Plugins

This displays all plugins installed but inactive on your site. You can view current version numbers of your software and if any extensions have updates available.

Dropin Plugins

These are in the wp-content but only specific file names. They replace/augment very specific functionality within WordPress.

Settings

This shows general settings for your site.

WooCommerce Pages

This shows page IDs and Permalinks designated as WooCommerce pages.

For example: If your site is https://example.com, a user would get to the Cart page by going to https://example.com/cart/

Theme

This displays information about the current theme running on your installation.

This could be a more problematic area of a site, as there is no standard on what themes should and should not do, and non-Woo themes can cause conflicts with WooCommerce or one of its extensions.

If you’re experiencing issues with your site, we recommend temporarily switching to the free Storefront Theme. If your problem is resolved while the Storefront theme is active, then the issue is with the theme. To resolve, check for updates or contact the theme developer to see if there is a fix.

Templates

This section shows any files that are overriding the default WooCommerce template pages, and also notes if the templates are outdated.

If you are experiencing trouble with any of the pages displayed, switching to the Storefront theme will ensure that the original template files are used. For more information, see Fixing Outdated WooCommerce Template Files. For a long-term fix, you need to contact the theme developer.

Subscriptions

Action Scheduler

This shows scheduled action counts with previous and most recent dates. For more technical information about the Action Scheduler and FAQ, please see ActionScheduler.org.

Tools #

In the Tools tab are helpful buttons that can address items such as user capabilities and customer sessions.

With transients, you can clear both WooCommerce transients and all expired transients from WordPress with the Clear transients and the Clear expired transients buttons. Transients are a standardized way to store cached data temporarily in the database.

If you have a collection of variations that don’t have a parent you can remove those with one click using the Delete orphaned variations button. You can then order address indexes, which can help improve order search results.

Following that, you can recount terms and reset capabilities. Recounting terms can be useful if you change any settings that hide products from the catalog and have issues from that. And if you find any users that can’t access all of the WooCommerce admin pages, resetting capabilities can be used in that case.

Clear customer sessions will remove any session data from the database. This includes any carts your customers are currently working on so use with caution.

Our next useful tool is the Create default WooCommerce pages button, if you’re having issues with WooCommerce pages or don’t want to create them one by one again you can select Install pages and it will create any missing WooCommerce pages. Pages already defined and set up won’t be replaced.

After that, you can delete all the tax rates you’ve set in WooCommerce. If you were going to delete them anyway use this tool versus going through each tax class and remove those rates one by one.

Finally, you can delete WebHook logs and reset the usage tracking settings. When you first installed WooCommerce you may have opted in to send us non-sensitive data that helps us make WooCommerce better for everyone. You can opt-out now by resetting your usage tracking settings.

Logs #

The Logs tab is where WooCommerce keeps logs of all events happening in your store. Some logs, like fatal-errors are kept automatically, while others, like those for payment gateways, first need to be enabled in the relevant extension’s settings.

In the dropdown, you can choose the logs you want to see, then select the View button to see events captured there. This can be useful to get exact errors with timestamps on parts of your store.

If your site experiences a fatal error, they may be logged here under a log named fatal-errors. This is useful when debugging.

By default, logs are kept for 30 days before being purged as of WooCommerce 3.4. This can be changed using the woocommerce_logger_days_to_retain_logs filter which defaults to 30.

There may be many logs depending on which extensions are installed and enabled for debug logging. For support purposes, the most relevant logs are usually the one with fatal-errors in the name, plus the log named for the extension in question. Any log with a date relevant to when the error occurred would be of interest though. Notice how the name of the log is followed by a date.