Updated Woo-commerce - Caused massive issues!

[dan7s]

Good Morning,

I’ll be honest, I’m certainly no expert when in comes to websites which is why I have probably made this mistake.

I have upgraded Woo-commerce to the latest version - 3.3.5 and am now having massive issues - Im not sure if this is caused by a X theme/Woo-commerce conflict with the latest version.

I have the error logs, is there any you could check to see if this is an x/woo conflict?

I would really appreciate any help with this,

Thanks in advance,
Dan

[rad]

Hi there,

Thanks for writing in.

There are many possible causes, and yes please provide your error logs. Or provide your site’s URL, admin and FTP login credentials in a secure note so we could check it. For the meantime, please check for the following first:

1. Ensure everything is up to date according to our version compatibility list at https://theme.co/apex/forum/t/troubleshooting-version-compatibility/195. Please follow the best practices when updating your theme and plugins. See https://theme.co/apex/forum/t/setup-updating-your-themes-and-plugins/62 for more details.

2. Clear all caches including browser cache then deactivate your caching plugins and other optimization plugins.

3. If you’re using a CDN, please clear the CDN’s cache and disable optimization services.

4. Test for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

5. Remove custom CSS, Javascript and templates.

6. Reset your htaccess file by renaming it to .htaccess-bak. Then in WP Admin Menu, go to Settings > Permalinks and just click the Save Changes button.

7. Contact your host to increase your allocated memory or do it yourself by adding this code in your wp-config.php

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

Thanks.

[dan7s]

Hi Rad,

I have added a secure note with login details - for the site and cpanel.

I think the majority of the error log is filled with what looks like outdated commands (a snippet below)

27-Apr-2018 16:22:56 UTC] The WC_Cart::ship_to_billing_address_only function is deprecated since version 2.5. Replace with wc_ship_to_billing_address_only.
[27-Apr-2018 16:23:00 UTC] id was called incorrectly. Order 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_without_payment, WC_Order->payment_complete, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_completed’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_New_Order->trigger, WC_Email->get_content, WC_Email_New_Order->get_content_html, wc_get_template_html, wc_get_template, include(’/plugins/woocommerce/templates/emails/admin-new-order.php’), do_action(‘woocommerce_email_order_details’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails->order_details, wc_get_template, include(’/plugins/woocommerce/templates/emails/email-order-details.php’), do_action(‘woocommerce_email_after_order_table’), WP_Hook->do_action, WP_Hook->apply_filters, Tco_Woo_Hooks::email_other_fields_list, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[27-Apr-2018 16:23:00 UTC] id was called incorrectly. Order 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_without_payment, WC_Order->payment_complete, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_completed’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_New_Order->trigger, WC_Email->get_content, WC_Email_New_Order->get_content_html, wc_get_template_html, wc_get_template, include(’/plugins/woocommerce/templates/emails/admin-new-order.php’), do_action(‘woocommerce_email_customer_details’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails->email_addresses, wc_get_template, include(’/plugins/woocommerce/templates/emails/email-addresses.php’), WC_Order->get_formatted_billing_address, apply_filters(‘woocommerce_order_formatted_billing_address’), WP_Hook->apply_filters, Tco_Woo_Hooks::order_formatted_billing_address, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

[rad]

Hi there,

These looks like related to checkout and payment process, and pointing to Woocommerce plugin itself. have you tried contacting Woocommerce community or developer?

But I tried the process and I don’t see any issue at all.

Would you mind listing the issues you’re getting? I can’t promise any solution, but if the issue is related to the theme then I can add them to our issue tracker.

Thanks!

[dan7s]

Hi Rad,

I have reached out to the Support team at WC, they say that;

" It appears there is an action calling “id” incorrectly. Accessing directly order data is not allowed, e.g. $order->id. Correct method going forward is $order->get_id()

This appears to be a template conflict issue. I’ve confirmed there are no webhooks on your site."

Is it possible that the template files included in X are causing this? If so what would the best solution be?

Thanks,
Dan

[Alaa]

Hi Dan,

We don’t have such an example $order->id in the theme WooCoommerce templates files.

Could you please let us know what are the symptoms of these “massive issues” you are getting? or they are just those notices in the server error log?

Thanks.