Plugin conflict

  • Resolved Nkanyi

    (@nkanyi)


    2 years, 6 months ago

    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 to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author ndre

    (@ndre)

    Hi @nkanyi,

    I checked the provided URL, but I cannot see the eCommerce Product Catalog active there?

    Thread Starter Nkanyi

    (@nkanyi)

    Hi @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

    (@ndre)

    Hi @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 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

    (@nkanyi)

    Thank you very much @ndre .

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin conflict’ is closed to new replies.