Using Troubleshooting Mode
One of the most common causes of issues with WordPress plugins is conflicts with other plugins or with your site’s theme. One way to identify a possible conflict is to deactivate your plugins and switch to a default WordPress theme. However, temporarily deactivating plugins or switching themes may not be possible, may be time-consuming, or may impact how your site displays to users.
The Health Check & Troubleshooting plugin allows you to do these troubleshooting steps safely, without affecting the front-end of your site and what your site visitors see.
Note: If you are experiencing AMP validation errors with your Web Stories when running them through the AMP Test Tool, the Health Check & Troubleshooting plugin won’t be able to identify any potential plugin/theme conflicts. These possible conflicts will need to be investigated by manually deactivating plugins/themes. For steps on how to do this, refer to the Troubleshooting outside of Troubleshooting Mode section below.
Install and activate the plugin
- In your WordPress admin, go to Plugins → Add New.
- Search for "Health Check".
- Click on Install Now next to Health Check & Troubleshooting
- Once installed, click on Activate
Turning on Troubleshooting Mode
In the WordPress admin, go to Plugins > Installed Plugins. You will now see a Troubleshoot option for each of your plugins. Select Troubleshoot next to Web Stories.
A panel will appear at the top of the Plugins page showing that you are in Troubleshooting Mode. As described on the screen, deactivating plugins or themes while in Troubleshooting Mode has no effect on your site’s visitors. They will see what they normally would.
Troubleshooting with Web Stories and a default theme
Now that you’re in Troubleshooting Mode with Web Stories enabled, check to see if the problem that you’ve been experiencing is still occurring. For example, if you were experiencing errors in the Editor, try opening and editing a story again.
You can always return to the Troubleshooting Mode panel by clicking Troubleshooting Mode in the admin toolbar.
If the issue is still occurring with only Web Stories activated, try changing to a default theme by selecting Available themes in the Troubleshooting Mode panel and clicking on Switch to this theme next to one of the WordPress default themes named after a year (Twenty Twenty, Twenty Twenty One, etc.)
After switching to a default theme, check again to see if the problem that you’ve been experiencing with Web Stories is still occurring.
If your problem is still occurring with only Web Stories and/or the default theme turned on, the issue is likely not theme- or plugin-related. Feel free to create a topic on our support forum for further assistance
If your problem is not occurring with only Web Stories and/or the default theme turned on, it means that one of your plugins or your theme could be causing the issue. Continue troubleshooting by following the steps below
Continuing troubleshooting as needed
If the issue that you’ve been experiencing with Web Stories does not occur with only Web Stories enabled, turn your other plugins back on, one at a time.
To enable a plugin in Troubleshooting Mode, click on Available plugins and then Enable next to the plugin name. Make sure that Web Stories is still enabled. After enabling a plugin, check to see if your Web Stories issue is still occurring. If the issue begins to occur again after a plugin is turned on, that plugin could be causing the issue with Web Stories. You can temporarily disable it and reach out to that plugin’s support for further assistance
Disabling Troubleshooting Mode
When you’re done with troubleshooting, you can turn off Troubleshooting Mode by clicking on the Disable Troubleshooting Mode button.
Troubleshooting outside of Troubleshooting Mode
When experiencing AMP validation errors through the AMP Test Tool on your Web Stories, the troubleshooting steps using the Health Check and Troubleshooting plugin will not work to identify plugin/theme conflicts. You will need to manually deactivate your site’s plugins and themes in order for AMP test results to update.
In the WordPress admin, go to Plugins > Installed Plugins. One by one, select the Deactivate option for your plugins making sure to leave the Web Stories plugin active. After each plugin you deactivate, run your Web Story URL through the AMP Test Tool once more to check if the validation errors no longer occur.
For best results, run the validation check in an Incognito browsing window to avoid any cached results.
If your problem is still occurring with only Web Stories turned on, the issue is likely not plugin-related. Continue to the Theme section below to continue troubleshooting
If your problem is no longer occurring after deactivating a particular plugin, it means that that plugin is likely causing the issue. You can temporarily keep the plugin disabled and reach out to the plugin’s support for further assistance
In the WordPress admin, go to Appearance > Themes. Find one of the WordPress default themes named after a year (Twenty Twenty, Twenty Twenty One, etc.) and select Activate. Run your Web Story URL through the AMP Test Tool once more to check if the validation errors no longer occur. For best results, run the validation check in an Incognito browsing window to avoid any cached results.
If your problem is still occurring with the default theme enabled, the issue is likely not theme-related. Feel free to create a topic on our support forum for further assistance.
If your problem is not occurring after enabling a default theme, it means that your theme is likely causing the issue. You can temporarily keep your theme disabled and reach out to your theme’s support for further assistance.
Finding console errors
Console errors can provide a clue or even an explanation to the cause of issues in Web Stories. To check for console errors:
- Navigate to where the issue is, for example the Web Stories Editor or your live Web Story
- Open browser developer tools by tapping the F12 key or right-clicking with your mouse and selecting Inspect
- Select the Console tab
- Refresh your browser and check the Console section in the developer tools window
Any console errors will display in red. Not all console errors will be related to a Web Stories issue, but they can still be helpful when troubleshooting.
Sharing your console errors
The best way to share your console errors on the Web Stories support forum is by using screenshots. You can do this by uploading the image to a service like Imgur or Google Drive, then share the link in your forum topic.
An example console error when there is a CORS policy issue:
More information and troubleshooting steps regarding CORS issues can be found here.