• Resolved mischademuynck

    (@mischademuynck)


    I did an update om my live site and encountered this problem. So I reversed and got my live website up and running again, but with old plugins.
    So made a staging website and did the updates step by step.

    Last one I did was Woocommerce (4.6.0) and now there are no Mollie payments available. It says in dutch: “Sorry, het lijkt erop dat er geen betaalmethoden beschikbaar zijn voor je staat. Neem contact met ons op als je hulp nodig hebt of op zoek bent naar alternatieve mogelijkheden.”

    So, no payment options for your state…

    I can see the Mollie options in the woocommerce payment options, but when I clock to configure one of these options, the page is empty. Happy to provide screenshots or a short movie.

Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter mischademuynck

    (@mischademuynck)

    Hi @niklasinpsyde,
    Tried this on the staging website. Updated everything and set Mollie to testing. Enabled Vibe plugin en as expected this broke the payment. After replacing the mollie plugin with the provided plugin it worked again.
    So I am glad there is light on the end of the tunnel, but I did not use this on my production website. What’s your advise?

    Love to hear from @vibethemes how they are going to fix this permanently

    Best regards,
    Mischa

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @mischademuynck,

    In theory, there should be no negative implications by increasing the init priority for the Mollie plugin. But while it effectively resolves the behavior, it does not fix the actual cause of the problem. As mentioned, this is not a fix we can provide by default. Our developers expect everything to still work fine when increasing the init prio, but I can’t give any guarantees.

    Changing our init priority can be done by modifying line 171 in the mollie-payments-for-woocommerce.php
    from
    'mollie_wc_plugin_init'
    to
    'mollie_wc_plugin_init',1

    After doing that, Mollie is initiated before VibeBP and properly loaded as a result. But instead of changing our init priority, we would prefer to find out why we can’t init when running after VibeBP so that an actual permanent solution can be proposed.

    Kind regards,
    Niklas

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘no payment options available after wc update an mollie update’ is closed to new replies.