woocommerce/docs/getting-started/debugging.md

---
post_title: Resources for debugging
menu_title: Debugging
---

## WordPress

A good place to start is usually the debugging tools built into WordPress itself:

* [Debugging in WordPress](https://wordpress.org/documentation/article/debugging-in-wordpress/)

## Logging

WooCommerce has a logging system that can be very helpful for finding and tracking errors on your site:

* [Logging in WooCommerce](../utilities/logging.md)

## Xdebug

If you're using `wp-env` to run a local development environment (this is the recommended method for the WooCommerce monorepo), you can activate Xdebug and then use an IDE like VS Code or PhpStorm to set breakpoints and step through the code as it executes:

* [Using Xdebug](https://github.com/WordPress/gutenberg/tree/trunk/packages/env#using-xdebug)
add graymatter to docs 2023-11-29 18:48:05 +00:00			`---`
			`post_title: Resources for debugging`
Further adjustment of post titles, menu titles, and tags (#43685) * Adjusting post_titles, menu_titles, and tags for docs folder Adjusting the post_titles, menu_titles, and tags for document files in the docs folder * Update removing-product-product-category-or-shop-from-the-url.md * Update classic-theme-developer-handbook.md * further adjustments and casing * Move HPOS/CLI contents into README --------- Co-authored-by: Jacklyn Biggin <hi@jacklyn.dev> 2024-01-16 19:29:00 +00:00			`menu_title: Debugging`
add graymatter to docs 2023-11-29 18:48:05 +00:00			`---`
Scaffold new debugging and logging docs 2023-08-24 19:42:38 +00:00
			`## WordPress`

Completed first draft of debugging and logging docs 2023-08-25 21:08:10 +00:00			`A good place to start is usually the debugging tools built into WordPress itself:`
Scaffold new debugging and logging docs 2023-08-24 19:42:38 +00:00
			`* [Debugging in WordPress](https://wordpress.org/documentation/article/debugging-in-wordpress/)`

			`## Logging`

Completed first draft of debugging and logging docs 2023-08-25 21:08:10 +00:00			`WooCommerce has a logging system that can be very helpful for finding and tracking errors on your site:`
Scaffold new debugging and logging docs 2023-08-24 19:42:38 +00:00
Update debugging link for using the logger 2023-08-29 21:05:23 +00:00			`* [Logging in WooCommerce](../utilities/logging.md)`
Scaffold new debugging and logging docs 2023-08-24 19:42:38 +00:00
			`## Xdebug`

Completed first draft of debugging and logging docs 2023-08-25 21:08:10 +00:00			If you're using `wp-env` to run a local development environment (this is the recommended method for the WooCommerce monorepo), you can activate Xdebug and then use an IDE like VS Code or PhpStorm to set breakpoints and step through the code as it executes:
Scaffold new debugging and logging docs 2023-08-24 19:42:38 +00:00
Completed first draft of debugging and logging docs 2023-08-25 21:08:10 +00:00			`* [Using Xdebug](https://github.com/WordPress/gutenberg/tree/trunk/packages/env#using-xdebug)`