Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Andrew Wikel - Debugging WooCommerce

WooConf
April 06, 2016

Andrew Wikel - Debugging WooCommerce

Andrew Wikel is a WooCommerce ninja at Automattic. He is committed to open source values and loves working with WordPress. He fell in love with WordPress in 2008, and has been working with it in some capacity since then. A husband, a father, a WordCamp addict, a coffee snob, lover of shiny things, and a California native trapped in Illinois.

Debugging WooCommerce
The basics of debugging WooCommerce, so that you spend less time worrying about code conflicts, and more time selling.

WooConf

April 06, 2016
Tweet

More Decks by WooConf

Other Decks in Technology

Transcript

  1. WooCommerce is awesome Customizing WooCommerce using actions and filters, or

    just adding plugins or themes, is a great way to provide a tailored solution for your exact needs, but sometimes things can go haywire.
  2. Questions to ask • When exactly did you first notice

    the problem? • Have any updates been applied to your website recently? • Have you changed themes or made any design changes? • Have you installed any new plugins? • Is your problem happening in one browser, or all of them? • Do you see any specific error messages?
  3. Cheating, the WooCommerce way We’ve built a fancy tool for

    you (really for us, but you can use it). It’s called the System Status Report, and you’ve likely seen it in the WooCommerce menu.
  4. Things to look for • Anything in red, which means

    a problem. • If you’re using an old version of a plugin from us, it will tell you. • It will tell you the template overrides you are using in your theme.
  5. Still not seeing anything? • Go to the page and

    use Firebug/Chrome Dev tools to look for anything out of the ordinary. • Use the built in logging for WooCommerce extensions that have it. This can help you narrow down certain issues with payments or shipping. • WP_DEBUG
  6. Don’t do any of this live • Make sure you

    have a backup of your site • Perform all debugging (and updates and everything else) on a staging site.
  7. Undo how you broke it • If you did something

    to break it, undo it • This is why you should have a backup to roll back to (if an update went awry, or your theme has outdated templates, etc.)
  8. Start in a vacuum • Deactivate everything (all plugins except

    the one that you have the issue with) • Change the theme to Storefront • Try to break it again
  9. If it works • Start reactivating plugins/theme until you find

    the culprit, and leave that deactivated while you contact the dev, etc.
  10. If it doesn’t • Try the exact setup on a

    completely different site to narrow it down to server configurations
  11. Resources to remember • WooCommerce Documentation • Woo Experts •

    Advanced WooCommerce • WooCommerce Troubleshooting 101