• Resolved Zade

    (@nothin7)


    Every time an order is Completed, I see the following in my PHP error log:

    [14-May-2023 02:31:16 UTC] id was called incorrectly. Product properties should not be accessed directly. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action('wc_ajax_checkout'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, SkyVerge\WooCommerce\PluginFramework\v5_10_12\SV_WC_Payment_Gateway_Direct->process_payment, WC_Order->payment_complete, WC_Order->save, WC_Order->status_transition, do_action('woocommerce_order_status_completed'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array('woocommerce_order_status_completed_notification'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_Customer_Completed_Order->trigger, WC_Email->get_content, WC_Email_Customer_Completed_Order->get_content_html, wc_get_template_html, wc_get_template, include('/plugins/woocommerce/templates/emails/customer-completed-order.php'), do_action('woocommerce_email_order_details'), WP_Hook->do_action, WP_Hook->apply_filters, my_woocommerce_email_order_details, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.

    Can this be fixed? This happens in PHP 7.4 and 8.2. I’m running the latest versions of the plugin (3.0.1), WooCommerce, and WordPress, but I’ve been noticing this error for months if not years.

    Thanks!

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

    I understand that when an order is tagged as completed, you are receiving the error above.

    I was testing on my site that has the latest version of WooCommerce and the Storefront theme, but I could not see the issue after creating an order, paying with PayPal for Braintree and set the order as completed.

    Can you switch the site theme to Storefront temporarily, and disable all plugins except WooCommerce and WooCommerce for Braintree? Check again to see if the issue persists, if not, it means a conflict was affecting the site, and you can then switch back your theme to the original one, reactivate the rest of the plugins (checking again after each plugin reactivation), until you find the culprit. More info: https://woocommerce.com/document/how-to-test-for-conflicts/

    If that does not help, please share your System Status Report, found under WooCommerce > Status, on your site.

    And please send a copy of the fatal error log that is under WooCommerce > System Status > Logs (if any other error is visible about the issue).

    Cheers.

    Thread Starter Zade

    (@nothin7)

    Figured it out. Thanks again.

    Hi @nothin7

    You are most welcome and we’re glad that worked! ??

    Meanwhile, if you have a moment to spare, we would love it if you could share your thoughts with us by leaving a review or feedback. Your experience and feedback are important to help us improve and ensure we’re always providing the best possible support.

    Thanks!

    Hi, @nothin7 I was facing the same error when I try to login to my WordPress website, are you able to login to your website with this error? I was not able to login to my WP website and here I found a Solution

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PHP error: “id was called incorrectly”’ is closed to new replies.