Support » Plugin: Eway Payment Gateway » Site error when in backend

  • Resolved mercurydan


    Im getting these error details in an email and finding strange behavior in my backend. Im not sure if its the new update or not. Im also looking to update from PHP 7.4 to 8.1. So not sure if this is caused by PHP error

    WordPress version 6.1.1
    Active theme: Astra Child (version 1.0.0)
    Current plugin: Eway Payment Gateway (version 5.0.0)
    PHP version 7.4.33

    Error Details
    An error of type E_ERROR was caused in line 697 of the file public_html/wp-content/plugins/eway-payment-gateway/includes/integrations/class.WooCommerce.php. Error message: Uncaught TypeError: Argument 1 passed to webaware\eway_payment_gateway\MethodWooCommerce::wooEmailOrderMetaKeys() must be of the type array, null given, called in public_html/wp-includes/class-wp-hook.php on line 308 and defined in public_html/wp-content/plugins/eway-payment-gateway/includes/integrations/class.WooCommerce.php:697
    Stack trace:
    #0 public_html/wp-includes/class-wp-hook.php(308): webaware\eway_payment_gateway\MethodWooCommerce->wooEmailOrderMetaKeys(NULL, false, Object(WC_Order))
    #1 public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array)
    #2 public_html/wp-content/plugins/woocommerce/includes/class-wc-emails.php(488): apply_filters(‘woocommerce_ema…’, Array, false, Object(WC_Order))
    #3 public_html/wp-includes/class-wp-hoo

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter mercurydan


    It seems to be fixed when I rollback to previous Version 4.5.1

    • This reply was modified 1 month, 3 weeks ago by mercurydan.
    Plugin Author webaware


    G’day mercurydan,

    Thanks for the bug report. It’s happening because some other plugin is breaking the filter hook woocommerce_email_order_meta_fields by passing null (probably the same mistake I made in Minimum Age for WooCommerce once, returning without a value).

    I’ve made a change that permits the first parameter to be an array now, so it should no longer break. Please update to v5.0.1 and let me know if you still see any problems.


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