3 months of PHP errors: ‘inpsyde-blocks’

  • Resolved Dave Loodts

    (@davelo)


    1 month, 2 weeks ago

    I don’t know what we can do to wake up Mollie support. After my 2-months support ticket i though about doing a 3 month ticket.
    I just went throught 12 WooCommerce shop of us that uses Mollie.
    Only 1 had no “inpsyde-blocks”, the other 11 shops had a lot of errors, depending on the amount of visitors between 500 and 10.000 errors every day.
    It’s needles to say it’s not easy to investigate error logs when they are so full of errors.

    We also use Sentry, which is a external error logging tool. We had to deactivate our account there, as the amount of Mollie’s errors pushes us to the limits of our monthly Sentry plan, just after a few days in the beginning of the month.
    So i give it just a few more weeks, and then we probably are going to switch to another payment provider.

    But still, i hope Mollie finally wakes up and fixes this.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Krystian Syde

    (@inpsydekrystian)

    1 month, 2 weeks ago

    Hello @davelo

    Thanks for sharing all that and I’m sorry its taking so long to fix this.

    Could you give this package a try? https://mollie.inpsyde.com/deactivated_in_blocks_v2

    We already shared it previously under same versioning, but some users got confused and thought they had tested it when they actually hadn’t. Let me know once you’ve had a chance to test it so we can confirm whether it solves the problem on your end.

    Kind Regards,
    Krystian

    Thread Starter Dave Loodts

    (@davelo)

    1 month, 2 weeks ago

    I installed the plugin on 1 site, and i can confirm the error is finally gone.

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    1 month, 2 weeks ago

    Hello @davelo

    Thanks for the feedback. I’m glad we were able to get it sorted out.

    Kind regards,
    Krystian

    Thread Starter Dave Loodts

    (@davelo)

    1 month, 2 weeks ago

    Well, not yet… i’m not going to install that “beta” plugin of all other 10 sites.
    It will be solved when there’s an official update + confirmation that the error stays gone in that official update.

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    1 month, 2 weeks ago

    Hello @davelo

    That is completely up to you and I understand it.

    For clarity, this version only contains the fix related to the dependency issue and does not introduce any additional changes. It is not an RC release and is considered safe from a stability perspective.

    This fix will be included in an upcoming official plugin update.

    Kind Regards,
    Krystian

    Thread Starter Dave Loodts

    (@davelo)

    1 month, 1 week ago

    And when is the new release with solution planned? Any day?

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    1 month, 1 week ago

    Hello @davelo

    Thanks for checking in. The fix is planned to be included in the next release scheduled for 10 March.

    Kind Regards,
    Krystian

    Thread Starter Dave Loodts

    (@davelo)

    1 month, 1 week ago

    Waw, that is still on month to go…. so +4 months with these errors… I’m 20 years in WordPress business, i never saw plugin builders delaying these kinds of issues and just launch a fix release… which is the obvious thing to do, as it took already 3 months.

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    1 month, 1 week ago

    Hello @davelo

    The fix is already shared. The package exists and has been tested. I agree that the timeline is a bit long so far. What we are waiting for now is the scheduled release cycle. We do not usually push standalone hotfixes unless something is a real production blocker. In this case, although the issue is obviously annoying, it was not classified as critical. Payments were still processing correctly, there was no data loss, and no vulnerability. Because of that, it was planned for the regular release instead of triggering an emergency patch.

    I appreciate your patience and your feedback. And again, apologize for the inconvenience this has caused.

    Kind regards,
    Krystian

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

You must be logged in to reply to this topic.