Support » Plugin: WooCommerce Stripe Payment Gateway » PHP error “billing_first_name was called incorrectly”

  • Resolved lunule

    (@lunule)


    Hi,

    We have PHP errors in our debug.log file – one of the returning errors seems to be related to the WooCommerce Gateway Stripe plugin:

    billing_first_name was called incorrectly. Order properties should not be accessed directly.

    The backtrace shows:

    Backtrace: 
    require('wp-blog-header.php'), 
    wp, 
    WP->main, 
    WP->parse_request, 
    do_action_ref_array('parse_request'), 
    WP_Hook->do_action, 
    WP_Hook->apply_filters, 
    call_user_func_array, 
    WC_API->handle_api_requests, 
    do_action('woocommerce_api_wc_stripe_subs_compat'), 
    WP_Hook->do_action, 
    WP_Hook->apply_filters, 
    call_user_func_array, 
    WC_Stripe_Subs_Compat->stripe_checkout_return_handler, 
    WC_Gateway_Stripe->stripe_checkout_return_handler, 
    WC_Stripe_Subs_Compat->process_payment, 
    WC_Gateway_Stripe->process_payment, 
    WC_Stripe_Payment_Gateway->process_response, 
    WC_Order->payment_complete, 
    WC_Order->save, 
    WC_Order->status_transition, 
    do_action('woocommerce_order_status_pending_to_processing'), 
    WP_Hook->do_action, 
    WP_Hook->apply_filters, 
    call_user_func_array, 
    WC_Emails::send_transactional_email, 
    do_action_ref_array('woocommerce_order_status_pending_to_processing_notification'), 
    WP_Hook->do_action, 
    WP_Hook->apply_filte in /nas/content/live/[...]/wp-includes/functions.php on line 4667

    Could you please investigate this further?

    Thanks,
    Lunule

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Shane Eckert

    (@shaneeckert)

    Automattic Happiness Engineer

    Hi,

    Are you seeing any errors on the front end and is this effecting the operation of your website in any way. Are you just seeing this message in the logs?

    Many times when we have seen this in the logs, it’s due to either a conflicting plugin or a template file that is out of date.

    Are all your template files up to date?

    Thanks!

    lunule

    (@lunule)

    Hi Shane,

    Thanks for your quick response – it took some time to review the whole plugin infrastructure, and now we see that there are indeed some plugins incompatible/not tested with the recent WooCommerce version, and we also have some outdated custom templates.

    So – I’m closing this ticket now. If after fixing everything we still see the error in the debug.log file, I’ll open a new one – but I agree, most probably the fixes will make the error go away.

    Thanks again,
    Lunule

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