• Viktor Bijlenga

    (@viktorbijlenga)


    Description
    We are experiencing an issue with the payment gateway provider logo/icon for Nets/DIBS on a site. Instead of displaying the default logo icon alongside the name of the payment gateway, we are seeing a broken image icon. Upon inspection, it appears that the image is returning a 404 response.

    I’ve open an issue with Nets, but it might be a good idea to share the problem here as well.

    Expected behaviour
    The default logo icon of Nets/DIBS should be displayed together with the name of the payment gateway.

    Current behaviour
    The logo icon is broken and returns a 404 response. The path to the image that is currently broken is:

    https://cdn.dibspayment.com/logo/checkout/combo/horiz/DIBS_checkout_kombo_horizontal_04.png

    This asset is included in the classes for payment-methods in the plugin. Path:

    /dibs-easy-for-woocommerce/classes/class-nets-easy-gateway.php:80

    Steps to Reproduce

    1. Navigate to the payment gateway section in the cart.
    2. Observe the broken image icon.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Viktor Bijlenga

    (@viktorbijlenga)

    I got a reply from Nets support regarding this issue. It might be a temporary issue on their end that’s causing the 404.

    I would think that this is not related to Woocommerce but is something that needs to be resolved in our systems since the image file is located on our domain. However, I will leave it to our developers to investigate and determine what needs to be done.

    louisekrokedil

    (@louisekrokedil)

    Hi,

    ?As you already mentioned this is a temporary issue at Nets and the Nets/Nexi team is working on the solution. In the meantime we will remove the logo in the plugin until this is resolved.

    Thread Starter Viktor Bijlenga

    (@viktorbijlenga)

    Great to hear that this will be solved in a future release! Feel free to mark this as solved.

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