• I received the following from the wordpress website. Do you think this could be due to the WordPress version?

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error
    on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, WooCommerce SecureSubmit Gateway.

    WordPress version 5.6
    Current theme: Storefront Child (version 2.5.8.1596560329)
    Current plugin: WooCommerce SecureSubmit Gateway (version 1.13.0)
    PHP version 7.2.25

    An error of type E_ERROR was caused in line 99 of the file /var/www/wp-content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Abstractions/HpsBuilderAbstract.php. 
    Error message: Uncaught HpsArgumentException: Get needs a transactionId in /var/www/wp-content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Abstractions/HpsBuilderAbstract.php:99
    
    Stack trace:
    #0 /var/www/wp-content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Abstractions/HpsBuilderAbstract.php(38): 
    HpsBuilderAbstract->validate()
    #1 /var/www/wp-content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Services/Fluent/Gateway/Credit/HpsCreditServiceGetBuilder.php(30): 
    HpsBuilderAbstract->execute()
    #2 /var/www/wp-content/plugins/woocommerce-securesubmit-gateway/classes/class-wc-gateway-securesubmit.php(319): 
    HpsCreditServiceGetBuilder->execute()
    #3 /var/www/wp-content/plugins/woocommerce-securesubmit-gateway/classes/class-wc-gateway-securesubmit.php(220): 
    WC_Gateway_SecureSubmit->isTransactionActiveOnGateway(68087)
    #4 /var/www/wp-includes/class-wp-hook.php(287): WC_Gateway_SecureSubmit->process_capture(Object(Automattic\WooCommerce\Admin\Overrides\Order))
    
    #5 /var/www/wp-includes/c

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hello,

    I’m not entirely sure how this error occurred and I’m not able to reproduce it. Can you tell me if this occurred when an admin attempted to capture a payment in the WooCommerce orders screen?

    Feel free to email us directly at [email protected]

    My client got the same error on their site once we updated to woocommerce 5.0.0 I reverted woocommerce back to 4.8.0 and we aren’t seeing this error anymore. I believe this plugin needs to be tested with this new version of woocommerce. Here is our version of the error:

    
    An error of type E_ERROR was caused in line 99 of the file /webclient/default/bromilow/sites/v2.bromilow.com/html/content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Abstractions/HpsBuilderAbstract.php. Error message: Uncaught HpsArgumentException: Get needs a transactionId in /webclient/default/bromilow/sites/v2.bromilow.com/html/content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Abstractions/HpsBuilderAbstract.php:99
    Stack trace:
    #0 /webclient/default/bromilow/sites/v2.bromilow.com/html/content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Abstractions/HpsBuilderAbstract.php(38): HpsBuilderAbstract->validate()
    #1 /webclient/default/bromilow/sites/v2.bromilow.com/html/content/plugins/woocommerce-securesubmit-gateway/classes/includes/src/Services/Fluent/Gateway/Credit/HpsCreditServiceGetBuilder.php(30): HpsBuilderAbstract->execute()
    #2 /webclient/default/bromilow/sites/v2.bromilow.com/html/content/plugins/woocommerce-securesubmit-gateway/classes/class-wc-gateway-securesubmit.php(319): HpsCreditServiceGetBuilder->execute()
    #3 /webclient/default/bromilow/sites/v2.bromilow.com/html/content/plugins/woocommerce-securesubmit-gateway/classes/class-wc-gateway-securesubmit.php(220): WC_Gateway_Sec
    

    Hello,

    I have tested using WooCommerce Version 5.0.0, WordPress Version 5.6.2, and Version 1.13.0 of our plugin. I am still unable to reproduce the issue. Can you tell me at what point you’re seeing this error?

    Feel free to email us directly at [email protected]

    Sorry for the delay, we haven’t ran into this error in a while. My client triggered the error again today and after some investigation we’ve found what seems to be the problem. It doesn’t seem to be a woocommerce conflict, but instead an issue isolated to this plugin only.

    A customer made an order on the site but provided the incorrect billing address. The credit card was never authorized. Then when editing the order my client selected the option to capture credit card authorization and then we saw the error. I suppose it makes sense that this created a fatal error because how would it capture payment if the card was never authorized in the first place. If these conditions always create this error, it may be best that it fails gracefully with a warning message on the edit order screen rather than a fatal php error.

    Let me know if you need any more information.

    Hi @ezimmerman9 , Thanks for following up, and for the detailed explanation. We’ll certainly look into this.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Uncaught HpsArgumentException’ is closed to new replies.