Support » Plugin: GF Mollie by Indigo » Bug: Conflict with other Mollie API plugin

Bug: Conflict with other Mollie API plugin

  • Resolved Brugman

    (@brugman)


    3 months, 1 week ago

    Hi. In gf-mollie-by-indigo.php you have require_once plugin_dir_path( __FILE__ ). 'Mollie/API/Autoloader.php';. On my site I have another plugin that also uses the Mollie API. They don’t conflict feature wise, but apparently that plugin got loaded first, and this causes an error along the lines of “cannot re-declare class Mollie_API_Autoloader”. You could wrap the require in a if ( !class_exists( 'Mollie_API_Autoloader' ) ) to fix this. The other plugin also has this check. I’ve made this change on my end, but if you update the plugin without fixing this, my site will throw an error again. So I hope you can add this to your first next update. Thanks!

    • This topic was modified 3 months, 1 week ago by Brugman.
    • This topic was modified 3 months, 1 week ago by Brugman.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Indigo Webstudio

    (@indigonl)

    3 months, 1 week ago

    Hi,

    Can you tell us what other plugin you are using. We want to check it so that we can make sure that it uses the same Mollie API version.

    Thanks,
    Petra

    Brugman

    (@brugman)

    3 months, 1 week ago

    It’s a custom build for a client. It has Mollie API Client v1.5.1 as a vendor package, remote API v1, but we could update that. With class_exists, your plugin seems to work.

    Plugin Author Indigo Webstudio

    (@indigonl)

    1 month, 1 week ago

    Hi,

    We released a new version with an option that allows you to disable loading of the Mollie API. You can use the following filter in your own plugin or functions.php of your childtheme

    add_filter( ‘gf_mollie_load_api’, ‘__return_false’ );

    Petra

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Topic Tags

Views