Title: Plugin conflict
Last modified: May 18, 2022

---

# Plugin conflict

 *  Resolved [Nkanyi](https://wordpress.org/support/users/nkanyi/)
 * (@nkanyi)
 * [4 years ago](https://wordpress.org/support/topic/plugin-conflict-363/)
 * Hi .
    After the last update the plugin began to conflict with other plugins in
   my website. when the plugin is active website users were unable to make payment
   due to the plugin. the plugin is preventing users to proceed to the payment gateway
   when the users click on “Proceed to Checkout gateway”. I had to re activate plugin
   in order to resolve this issue.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-conflict-363%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [ndre](https://wordpress.org/support/users/ndre/)
 * (@ndre)
 * [4 years ago](https://wordpress.org/support/topic/plugin-conflict-363/#post-15656030)
 * Hi [@nkanyi](https://wordpress.org/support/users/nkanyi/),
 * I checked the provided URL, but I cannot see the eCommerce Product Catalog active
   there?
 *  Thread Starter [Nkanyi](https://wordpress.org/support/users/nkanyi/)
 * (@nkanyi)
 * [4 years ago](https://wordpress.org/support/topic/plugin-conflict-363/#post-15659190)
 * Hi [@ndre](https://wordpress.org/support/users/ndre/)
    Thank you for taking your
   time to attend to my issue. yes I deactivated the eCommerce Product Catalog plugin.
   Could you please pretend to be buying something on the website . When you click
   on proceed to checkout button you should be re directed to payment gateway .once
   you done please let me know , I will activate the plugin and I will let you know.
   when the plugin is active it prevents the “Proceed to Checkout” Button to function
   in a proper manner.Thank you
 *  Plugin Author [ndre](https://wordpress.org/support/users/ndre/)
 * (@ndre)
 * [4 years ago](https://wordpress.org/support/topic/plugin-conflict-363/#post-15659590)
 * Hi [@nkanyi](https://wordpress.org/support/users/nkanyi/),
 * Thank you for the information.
 * What are you trying to achieve with the eCommerce Product Catalog plugin?
 * If you what to create a separate catalog you should not mix the checkout pages
   with WooCommerce. Both plugins probably have the same checkout pages defined,
   which is causing the issue.
 * If you want to take advantage of the eCommerce Product Catalog design with WooCommerce
   products, you should use the [WooCommerce Catalog Booster](https://wordpress.org/plugins/catalog-booster-for-woocommerce/)
   along with eCommerce Product Catalog.
 * If you want to replace WooCommerce, you should import all WooCommerce products
   to the eCommerce Product Catalog (there is an import tool in the settings) and
   disable WooCommerce.
 *  Thread Starter [Nkanyi](https://wordpress.org/support/users/nkanyi/)
 * (@nkanyi)
 * [4 years ago](https://wordpress.org/support/topic/plugin-conflict-363/#post-15659613)
 * Thank you very much [@ndre](https://wordpress.org/support/users/ndre/) .

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

The topic ‘Plugin conflict’ is closed to new replies.

 * ![](https://ps.w.org/ecommerce-product-catalog/assets/icon-128x128.png?rev=1103243)
 * [eCommerce Product Catalog Plugin for WordPress](https://wordpress.org/plugins/ecommerce-product-catalog/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ecommerce-product-catalog/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ecommerce-product-catalog/)
 * [Active Topics](https://wordpress.org/support/plugin/ecommerce-product-catalog/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ecommerce-product-catalog/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ecommerce-product-catalog/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Nkanyi](https://wordpress.org/support/users/nkanyi/)
 * Last activity: [4 years ago](https://wordpress.org/support/topic/plugin-conflict-363/#post-15659613)
 * Status: resolved