The document discusses advanced debugging techniques for troubleshooting issues in development environments. It recommends not debugging on production, setting debug constants, using tools like grep, var_dump(), error_log(), and Query Monitor. It also mentions permissions, version control with git, identifying filters and hooks, and leaving documentation for others working on the project. Contact information is provided at the end.

1. The Magic of
Advanced Debugging

3. Work Days

5. Once upon a time

8. Where to start

9. Don’t ever debug on
production

10. Set debug constants

13. Fatal error: Cannot use object of type stdClass as array in
/Users/ivdimova/Sites/project.dev/wordpress/wp-content/plugin
s/custom-social-feed/includes/init.php on line 645, referer:
http://project.dev/

14. Invalid argument supplied for foreach() in
/Users/ivdimova/Sites/project.dev/wp-includes/plugin.php on
line 523

15. Plugin conflicts?!

16. Grep all the things
grep all the things

17. var_dump();
error_log();
error_log( print_r( $object, 1 ) );

18. Query Monitor

20. Xdebug

26. Permissions, permissions

27. Version Control

28. git log

29. git blame

31. Identify filters and hooks

32. add_action( 'plugins_loaded', 'prefix_remove_action', 10 );
function prefix_remove_action() {
$invoice = new WC_Gateway_Sprout_Invoices();
$result = remove_action( 'woocommerce_thankyou_sprout_invoices', array(
$invoice, 'thankyou_page' ), 20 );
}

36. Leave legacy for others

38. Contact:
iv.dimova@gmail.com
@iv_wp
https://www.linkedin.com/in/ivdimova