Fatal Error on version 4.2.2

Same here, on a few sites in my portfolio. It’s been causing lots of admin area problems. I reported it yesterday and haven’t heard anything back yet. I’ll sit in on this ticket too.

Hey guys – we have a very similar issue.

We installed/activated Taxjar and only after enabling the configuration settings (check boxes) to actually turn on the tax calculations on the front end did things start to break. Now, while things on the front end seem to be working correctly, as in the tax is displaying and calculating correctly at checkout, it’s simply the admin that we’re getting the ‘fatal error’ that is breaking other features and plugins.

Here’s the error:

Fatal error: Uncaught Error: TaxJar\Order_Meta_Box::get_order_tax_calculation_metadata(): Argument #1 ($order) must be of type WC_Order, bool given, called in /home/name/www/site-name.bak/wp-content/plugins/taxjar-simplified-taxes-for-woocommerce/includes/admin/class-order-meta-box.php on line 32
in?/home/name/www/site-name.bak/wp-content/plugins/taxjar-simplified-taxes-for-woocommerce/includes/admin/class-order-meta-box.php?on line?45

Call stack:

1. TaxJar\Order_Meta_Box::get_order_tax_calculation_metadata()
   wp-content/plugins/taxjar-simplified-taxes-for-woocommerce/includes/admin/class-order-meta-box.php:32
2. TaxJar\Order_Meta_Box::output()
   wp-admin/includes/template.php:1456
3. do_meta_boxes()
   wp-admin/edit-form-advanced.php:723
4. require()
   wp-admin/post.php:206

Has there been any updates or resolutions for you all?
Does anyone have a technical contact at Taxjar? I can’t seem to reach anyone.

• This reply was modified 3 months, 2 weeks ago by seedcity.

I also reported this to WooCommerce.com to try to get some eyes on it.

FYI you can downgrade it via WP-CLI with this command wp plugin update taxjar-simplified-taxes-for-woocommerce --version=4.2.1 and this has patched the affected stores in my portfolio just fine.

In order for it to stop bugging you about the 4.2.2 update; edit the file taxjar-woocommerce.php and set the Version: line near the top from 4.2.1 to 4.2.3-beta then the real v4.2.3 (or later) will download over it when ready.

Update. Reverting back to 4.2.1 did solve our problem.

Version 4.2.3 just dropped and it indicate some fixes in the change-log. I’ll test it out.

@seanconklin did Version 4.2.3 fix this issue?

Wow, crazy that upon logging in it made me checkbox that I have no WPE affiliation, taking things too far for a community site I would say.

Anyhow, yes, we no longer face this problem.

Awesome thanks for responding so quickly @seanconklin !!

YES this WPE drama needs to stop and we get back to being a collaborative community. ??