Title: PHP error: “id was called incorrectly”
Last modified: May 14, 2023

---

# PHP error: “id was called incorrectly”

 *  Resolved [Zade](https://wordpress.org/support/users/nothin7/)
 * (@nothin7)
 * [3 years ago](https://wordpress.org/support/topic/php-error-id-was-called-incorrectly/)
 * Every time an order is Completed, I see the following in my PHP error log:
 *     ```wp-block-code
       [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)

 *  [Igor H](https://wordpress.org/support/users/ihereira/)
 * (@ihereira)
 * [3 years ago](https://wordpress.org/support/topic/php-error-id-was-called-incorrectly/#post-16736034)
 * 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](https://www.woocommerce.com/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](https://woocommerce.com/products/woocommerce-gateway-paypal-powered-by-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/](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](https://wordpress.org/support/users/nothin7/)
 * (@nothin7)
 * [3 years ago](https://wordpress.org/support/topic/php-error-id-was-called-incorrectly/#post-16743312)
 * Figured it out. Thanks again.
 *  [xue28 (woo-hc)](https://wordpress.org/support/users/xue28/)
 * (@xue28)
 * [3 years ago](https://wordpress.org/support/topic/php-error-id-was-called-incorrectly/#post-16743489)
 * Hi [@nothin7](https://wordpress.org/support/users/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](https://wordpress.org/support/plugin/woocommerce-gateway-paypal-powered-by-braintree/reviews/).
   Your experience and feedback are important to help us improve and ensure we’re
   always providing the best possible support.
 * Thanks!
 *  [Asmat Ullah](https://wordpress.org/support/users/asmatullah88/)
 * (@asmatullah88)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/php-error-id-was-called-incorrectly/#post-16826267)
 * Hi, [@nothin7](https://wordpress.org/support/users/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](https://dailytechpakistan.com/how-to-fix-wp-blog-header-php-error-in-wordpress-website/)

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

The topic ‘PHP error: “id was called incorrectly”’ is closed to new replies.

 * ![](https://ps.w.org/woocommerce-gateway-paypal-powered-by-braintree/assets/icon-
   256x256.png?rev=3234800)
 * [Braintree for WooCommerce Payment Gateway](https://wordpress.org/plugins/woocommerce-gateway-paypal-powered-by-braintree/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-gateway-paypal-powered-by-braintree/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce-gateway-paypal-powered-by-braintree/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce-gateway-paypal-powered-by-braintree/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-gateway-paypal-powered-by-braintree/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce-gateway-paypal-powered-by-braintree/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [Asmat Ullah](https://wordpress.org/support/users/asmatullah88/)
 * Last activity: [2 years, 11 months ago](https://wordpress.org/support/topic/php-error-id-was-called-incorrectly/#post-16826267)
 * Status: resolved