Title: How to debug?
Last modified: May 13, 2025

---

# How to debug?

 *  [archesis](https://wordpress.org/support/users/anchises/)
 * (@anchises)
 * [1 year, 2 months ago](https://wordpress.org/support/topic/how-to-debug-9/)
 * How can I debug this plugin in case the sychronisation doesn’t work? I tested
   it on one website where it worked, on a different website (but same server) it
   refuses to work. The message “initialSyncCompleted” constantly pops up in WP 
   dashboard, however no “Sync” is happening = customers with newsletter subscriptions
   are not transferred to the corresponding list in CleverReach. If I add some to
   the list directly in CleverReach then the number of recipients in Woocommerce/
   CleverReach Dashboard reflects that, so it seems there is a least some connection.
   However the recipients are not synchronized between Woocommerce and CleverReach.
   Manually forcing it does nothing. How can I find out why it isn’t working?

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [cleverreach7](https://wordpress.org/support/users/cleverreach7/)
 * (@cleverreach7)
 * [1 year, 2 months ago](https://wordpress.org/support/topic/how-to-debug-9/#post-18474135)
 * Hello!
 * You can check any of these:
 *     ```wp-block-code
       To rule out typical causes in advance, please check1) Whether the store is directly accessible. This means above all that the CleverReach plugin folders must be accessible, an HTACCESS block or HTPASSWORD can impair the correct function of the plugin2) The server on which the CRM / CMS / store system is installed must be able to process CURL3) The latest version of the plugin is used4) The store URL:a) is an HTTPS URL that has a valid SSL certificateb) Frontend routes that the plugin opens must be accessible (no redirection). If you have such a redirect for frontend routes, please contact us. We will send you a list of the plugin frontend routes that need to be activated for the plugin to work correctly.5) The store server must be able to call itself via the frontend route using the CURL library.6) When it comes to the initial connection between the store and CleverReach: this should be done with Chrome or Firefox in the latest version
       ```
   
 * You can also check your serverlogfiles if there are any errors present regarding
   the Plugin.
 * If you see any error messages, you can contact the CleverReach support directly
   on our website to send us the Logfiles for further investigations.
 * Best Regards
 * Dennis
 *  Thread Starter [archesis](https://wordpress.org/support/users/anchises/)
 * (@anchises)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/how-to-debug-9/#post-18485976)
 * Thanks, I will see what I can do.
 * WordPress debug.log says the plugin uses some deprecated functions. I am on PHP
   8.3
 *     ```wp-block-code
       PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\Infrastructure\TaskExecution\TaskRunnerStarter implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/Infrastructure/TaskExecution/TaskRunnerStarter.php on line 22PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\Infrastructure\TaskExecution\AsyncBatchStarter implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/Infrastructure/TaskExecution/AsyncBatchStarter.php on line 10PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\Infrastructure\TaskExecution\QueueItemStarter implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/Infrastructure/TaskExecution/QueueItemStarter.php on line 22PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\BusinessLogic\Receiver\Tasks\Composite\SubscribeReceiverTask implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/BusinessLogic/Receiver/Tasks/Composite/SubscribeReceiverTask.php on line 16PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\BusinessLogic\Receiver\Tasks\Composite\UnsubscribeReceiverTask implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/BusinessLogic/Receiver/Tasks/Composite/UnsubscribeReceiverTask.php on line 12PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\BusinessLogic\Receiver\Tasks\Composite\ReceiverSyncTask implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/BusinessLogic/Receiver/Tasks/Composite/ReceiverSyncTask.php on line 23PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\BusinessLogic\InitialSynchronization\Tasks\Composite\InitialSyncTask implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/BusinessLogic/InitialSynchronization/Tasks/Composite/InitialSyncTask.php on line 16PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\BusinessLogic\Authorization\Tasks\Composite\ConnectTask implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/BusinessLogic/Authorization/Tasks/Composite/ConnectTask.php on line 9PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\BusinessLogic\Scheduler\ScheduleCheckTask implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/BusinessLogic/Scheduler/ScheduleCheckTask.php on line 28PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\BusinessLogic\Utility\Tasks\TaskCleanupTask implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/BusinessLogic/Utility/Tasks/TaskCleanupTask.php on line 20PHP Deprecated:  CleverReach\WooCommerce\IntegrationCore\Infrastructure\TaskExecution\TaskRunnerStarter implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /…/cleverreach-wc/vendor/cleverreach/integration-core/src/Infrastructure/TaskExecution/TaskRunnerStarter.php on line 22
       ```
   

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘How to debug?’ is closed to new replies.

 * ![](https://ps.w.org/cleverreach-wc/assets/icon-256x256.png?rev=2758238)
 * [Official CleverReach® Plugin for WooCommerce](https://wordpress.org/plugins/cleverreach-wc/)
 * [Support Threads](https://wordpress.org/support/plugin/cleverreach-wc/)
 * [Active Topics](https://wordpress.org/support/plugin/cleverreach-wc/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cleverreach-wc/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cleverreach-wc/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [archesis](https://wordpress.org/support/users/anchises/)
 * Last activity: [1 year, 1 month ago](https://wordpress.org/support/topic/how-to-debug-9/#post-18485976)
 * Status: not resolved