• Resolved benjibee

    (@benjibee)


    Since upgrading to the 8.0.0 release the API integration with Mollie is returning a 422 error:

    Error executing API call (422: Unprocessable Entity): Line item 1 is invalid.
    The 'imageUrl' field should be a valid URL. Documentation: https://docs.mollie.com/overview/handling-errors.
    Request body: {"status":422,"title":"Unprocessable Entity","detail":"Line item 1 is invalid.
    The 'imageUrl' field should be a valid URL","field":"lines.1.imageUrl","_links":{"documentation":{"href":"https://docs.mollie.com/overview/handling-errors","type":"text/html"}}}. Field: lines.1.imageUrl

    This error is happening regardless of an image being present on the product being processed in the checkout. Our checkout has worked without issue until this update ran, and no other updates were made around this time.

    • This topic was modified 1 month, 1 week ago by benjibee.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter benjibee

    (@benjibee)

    Here’s a cleaned up version of the system report for WooCommerce: https://privatebin.syde.com/?4f90c306d2b35946#5Ug79gdfSp8PZKJPFBCjKKDBt3baPsEEgKVk7QSRGUAy

    I see you’re requesting this from lots of people on this forum, as I’m sure many other WooCommerce developers are. The output from this should not be public as it’s enough information to compromise most WordPress systems by knowing the URL, website info, and all installed plugins. I’m quite shocked how normal this is on these support forums.

    Plugin Support Femi

    (@femiyb)

    Hello @benjibee

    Thank you for sharing the system report, it’s much appreciated.

    For now, we recommend downgrading to the previous version of the plugin (7.1.0) while our developers continue to investigate the issue introduced in version 8.0.0.

    We’ve also noted your feedback regarding the system report request.

    Thanks again for your patience and cooperation!

    Regards,
    Femi

    Thread Starter benjibee

    (@benjibee)

    Great, we’ll do that. Thanks for the quick response and good luck to your team!

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @benjibee

    Our team has created a new version that should resolve the error you mentioned (and some others that have been reported): https://mollie.inpsyde.com/801beta1

    We are still validating some things but wanted to share it in case you want to give it a try and let us know if this resolves the issue you were facing.

    Feedback is much appreciated in any case.

    Kind regards,
    Krystian

    Plugin Support Femi

    (@femiyb)

    Hi,

    We’re happy to confirm that this has been addressed in version 8.0.1.

    If you’re still experiencing the issue:

    • Please make sure you’ve updated to version 8.0.1.
    • Clear any relevant caches after the update.
    • If the issue persists, please reach out so we can assist further.

    Thanks for your cooperation and for helping us track this down!

    Regards,
    Femi

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