Before You Upgrade
First and foremost, we always recommend testing updates in a staging environment prior to updating a live site, especially if running themes and plugins from 3rd parties. http://docs.woothemes.com/document/testing-updates-using-a-staging-environment/
Debugging a White Screen or Error 500
If you find a white screen or error 500 that usually means something has triggered a PHP error, but errors are hidden on your server. To find out the cause of the error you have two choices:
- Look at your server error logs and find the latest ‘fatal error’
- Enable WP_DEBUG mode and view the page again
Enabling WP_DEBUG involves editing your wp-config.php file and changing, or adding if its not there:
define( 'WP_DEBUG', true );
When this is done, a more useful error message should be shown. Most of the time this contains the name of the plugin and the line number causing the issue allowing you to act.
Debugging Functionality Issues
If something is not working after an update, a likely cause is an outdated or non compatible plugin or theme. The best thing to do is to narrow down the cause. To do this you can temporarily:
- Switch to a default WordPress theme (Twenty Twelve) and test again
- Disable all other plugins except for WooCommerce itself, retest, and re-activate plugins until the issue occurs. This will help you find the culprit.
If after doing the above steps you find that you are hitting the memory limit, you can increase WordPress’ limit. See here.
For More Help
See our self-service guide here.
- The topic ‘How To Debug Issues After Updates’ is closed to new replies.