Olli Kousa

We’re seeing similar issues where the lowest price either shows the current sale price, doesn’t show up at all or shows zero. All of which are wrong.

Store I debugged this with has only variable products, not sure if this is the case for others too.

I noticed that there are no new database entries for the product after saving it with different price. I tried both ways of saving variations, neither worked.

I looked at the action_save_post_product function that’s hooked to save_post_product. I think it should be using woocommerce_update_product instead. When saving variations via ajax it didn’t seem to trigger at all and when saving whole product both $product->get_regular_price() and $product->get_sale_price() functions return empty, causing the “update if needed” check to fail.

Overall the plugin seems rather buggy at the moment. As a sidenote, I think the migration should’ve been done to custom table, not posts. That would’ve improved performance even more and kept the posts table cleaner. ??

We’ve got few similar reports from users. We have the free version of the Gift Card plugin. We have also had succesful gift card orders with partial payment so it’s not consistent.

There’s the following fatal error in the logs. Stack trace suggests it’s related to “fix_rounding_error()” function.

Fatal error: Uncaught Error: Call to a member function setUnitPrice() on null in /data/wordpress/wp-content/plugins/paytrail-for-woocommerce/src/Gateway.php:1297

I checked that all orders utilizing gift cards that failed had the “order total” off by 1 cent compared to the item_subtotal + shipping + tax. So it would make sense that it’s related.

Didn’t go too deep into it but it seemed like the error only happened with orders that had gift cards used on them.

Had some luck and was able to determine the cause to be Woo Discount Rules -plugin. Both plugins hook into before_calculate_totals action and modify product prices.

The plugin was off at one point which must’ve caused the confusion. Should’ve tested for conflicts right away anyway.

For us the solution is to most likely ditch the discount-plugin (for this and many other reasons) but this could still be relevant issue for other people.

We’re having the same issue. Few cases out of 25 so far after launching Klarna Checkout earlier this week.

Case 1: One customer managed to create three separate orders in WooCommerce
1. Order (image) with correct row data (product and prices), but no information, Klarna key and order total 0€.
2. Order with customer address (no email or phone number), rather odd costs (only incorrect tax).
3. Order with everything correctly.

Case 2: Only one order in WooCommerce which is not linked to the succesful klarna payment.

Also few other cases where customers haven’t been redirected back to success page or something similar, so they’ve ended up making another order. Everything shows up correctly otherwise, so these are harder to debug.

Both cases 1 and 2 are linked to the same error:
ERROR Push callback but no existing WC order found for Klarna order ID

We’ll continue to investigate further, but any insight would be very welcome. The problems seem to be very inconsistent and there could be multiple parallel issues.

Yes, the fee name is what I’m trying to change. I have the following code:

$cart->add_fee( 'Membership discount -5%', -$discount);

But still the checkout labels it as “Additional fee” (“Lis?maksu” in finnish)

Here’s image to what I mean. On the WooCommerce side it shows correctly as “Membership discount -5%”.

I actually were very close, I did look at those rows, although previously didn’t notice the name field. I now tried to edit the code and it still didn’t change. This could relate to caching, but the there’s a comment before the $fee_item array:

// Add separate discount line item, but only if it’s a smart coupon or country is US.

It is not a smart coupon nor are we in US. I’m not sure if that comment is actually relevant as I did not see any conditions for it. But considering that it A) Should use the given fee name B) Even hard coded value did not change it, I’m inclined to believe that it is indeed accurate.

I have the same issue. It’s popping out randomly and causing issues with at least Safari.

It actually caused critical failure in Safari due to PWA trying to load this file.

I did not have a single Advanced-headings block in the site, which makes it quite odd.

My users are getting the same or very similar error that blocks access. I’m unable to replicate the issue of no loading, but the error is logged to console nonetheless.

This seems to be focused on the Safari browsers, both on mobile and desktop.

EDIT: I managed to replicate the loading failure after all. It was linked to a 404 error of a .css.map file (don’t know if the file type is relevant). Immediate workaround was to exclude this file from PWA cache, have to check deeper to what’s causing nonexisting file to load, probably not PWA related.

However, in my opinion such case shouldn’t lead to total failure so it might be something worth checking in the PWA plugin development.

• This reply was modified 4 years, 11 months ago by Olli Kousa.