Missing basic WooCommerce functions support

  • Resolved Enwikuna

    (@enwikuna)


    4 months, 1 week ago

    Hi there,

    we are providing a plugin to our customer where they have the option to map WooCommerce payment methods to a remote payment method from a CRM system. Inside our settings page, we fetch all available WooCommerce payment methods via this function call:

    WC()->payment_gateways()->payment_gateways()

    Sadly, Mollie is not part of the returned items. This is a function WC provides to be able to do such things as we do. We kindly ask you to support this function or tell us how we can get all enabled payment methods from Mollie.

    • This topic was modified 4 months, 1 week ago by Enwikuna.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Femi

    (@femiyb)

    4 months, 1 week ago

    Hi @enwikuna

    Mollie gateways should normally be returned by WC()->payment_gateways()->payment_gateways(), as the plugin registers them via the standard woocommerce_payment_gateways filter.

    Could you please confirm:

    • Whether Mollie payment methods are visible and working on the normal WooCommerce checkout.
    • In which context the function is being called (admin page, REST request, AJAX, etc.).

    If possible, sharing a minimal reproduction or more details about the setup would help us investigate further.

    Thanks.

    Thread Starter Enwikuna

    (@enwikuna)

    4 months, 1 week ago

    Hi there,
    Thank you for your response and for confirming that the Mollie payment methods are correctly registered and working on the standard WooCommerce checkout.
    We have investigated the issue within our get_available_payment_gateways function and identified the cause. It appears that the Mollie gateways use magic __get methods to provide properties like id, enabled, and method_title. In our previous implementation, we were using isset() to check for these properties before accessing them. However, since the Mollie gateway class does not implement the magic __isset method, isset() returned false for these properties even though they were accessible.
    We have now updated our logic to more robustly handle these cases by directly checking for property existence or the presence of magic methods. Additionally, we have improved the title retrieval to ensure that vendor prefixes (like “Mollie” or “WooPayments”) are correctly displayed in our mapping settings, providing a better user experience.
    The function is typically called within the WordPress admin context when the WooMex order settings page is loaded.
    Best regards, The Enwikuna Team

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

You must be logged in to reply to this topic.