- Clerk.io Help Center
- Using Clerk.io on WooCommerce
- Troubleshooting
-
Working with Clerk.io
-
Using Clerk.io on Other / Custom Platforms
-
Using Clerk.io on Shopify
-
Using Clerk.io on Magento 1
-
Using Clerk.io on Magento 2
-
Using Clerk.io on WooCommerce
-
Using Clerk.io on Prestashop
-
Using Clerk.io on BigCommerce
-
Using Clerk.io on Shoporama
-
Using Clerk.io on Shopware 6
-
Using Clerk.io on DanDomain
-
Using Clerk.io on Lightspeed
-
Using Clerk.io on SmartWeb / HostedShop
-
Using Clerk.io on DynamicWeb
-
Using Clerk.io with Any Email Client
-
Using Clerk.io with Copernica
-
Using Clerk.io with Autopilot
-
Using Clerk.io with Active Campaign
-
Using Clerk.io with Marketing Platform
-
Using Clerk.io with MailChimp
-
Using Clerk.io with MailUp
-
Using Clerk.io with Apsis
-
Using Clerk.io with UbiVox
-
Using Clerk.io with CleverReach
-
Using Clerk.io with Google Ads
-
Using Clerk.io with Act-On
-
Audience Integrations with Facebook
-
Using Clerk.io with DotDigital
-
Using Clerk.io with Klaviyo
Why is WooCommerce Showing Warnings in my Backend, and on the Website?
Check how to disable debug mode in WooCommerce.
This error usually happens, if WooCommerce's Debugging has been activated. This is never a good idea to have activated on a live-setup because it slows down pages, and potentially shows error messages in the frontend.
The sync issue happens if WooCommerce encounters an error while generating the product-data for the import.
This can be solved by deactivating Debug Mode either through the plugin or directly in the WooCommerce files.
Using the Plugin
If you are using Clerk.io's v2.2.4 or later, Debugging can be disabled directly from the Plugin page in your WooCommerce backend.
Go to Clerk -> Clerk Settings -> Debug Guide and click Disable Debug Mode:
-1.png)
Or Directly in the Files
Debug Mode can also be deactivated through FTP, in wp-config.php by setting define(WP_DEBUG', false).
This guide explains it in more detail:
https://docs.woocommerce.com/document/woocommerce-product-search/api/debugging/
And this guide explains an alternate workaround:
https://aristath.github.io/blog/wp-hide-php-errors
Errors will still be logged even when not in Debug Mode, but they will be logged to a file instead.