mfassier

Indeed, this was a PayPal problem all along.

Sorry, missing the basic stuff:
WP is 4.8
WC is 3.1.1
PP for WC is 1.4.5.1

+1 as well. I’ve just wasted the valuable time of a few people, including other devs, blaming them for something they had nothing to do with. Perhaps this problem exists with other plugins as well, but as of now Backup WP is the one that crashes my site. Upon deactivation all plugins – including more than one that deals with Dropbox – starts working again. I do not have the coding skills to suggest a solution, but you do need to find one. Aside from this major flaw, I like your work very much and would hate having to stop using it because you don’t play nice with others…

Well, you did hit the nail right on the head. We are using Backup WP and in fact, the only reason we were re-visiting the issue today was because I had a bit of spare time and was looking into why Backup had stopped working a week ago… Disabled Backup WP and voilà, your menus are back. So I’ll make the changes I wanted then re-enable Backup. I see the Backup dev is getting a lot of heat for it, but I have to say his plugin is pretty cool and up until recently was working flawlessly (well, if you don’t count the fact that it nuked yours in the process). I’ll take this matter to him instead of bothering you.

Thanks for the support, keep up the good work !

Nope, a reinstall did not fix it… I really have nothing fancy running on there, aside from the fact that it’s a multilingual site. Ever ran into troubles with WPML or WCML sites ? It’s almost impossible to deactivate these without breaking a lot of stuff, but then again these were running long before I first installed PDF Invoice.

Hello again. I did cycle most of the plugins on and off and found no change. I’m still met with an almost blank page under WooCommerce-> PDF Invoices.
The plugin works well, it pumps out the necessary invoices and packing slip with all transactions, but there is nothing we can do short of editing the code itself to make modifications. I guess the next step will be to remove and reinstall. I’ll let you know what happens.

Me again. We’re still stuck with this problem and after traveling to the moon and back, the solution was in fact extremely simple : in PaypalExpres, $shipping is rounded, in PaypalPro, it wasn’t.
Added $shipping = number_format($shipping,2,'.',''); at line 871 of the pro module and it looks like it’s all good.

In my case it’s the shipping module that returns 3 decimal. If I manually round it off in the code before passing it on to PP for WC, then it works properly. My problem is I’m unable to do this using proper accounting convention (rounding half-up). The strange part of this of course is that if my client checkouts with PP standard, it all goes fine. If he uses his credit card and PP pro, it goes to hell.

Going out on a limb here : this used to work fine, could I roll back to 1.1.6.1 to see if problem goes away ? This would likely help to find the culprit too. Where can I find a previous version ?

Thanks for the quick reply. Actually, we’re not including taxes in WC, taxes are calculated on the subtotal. What do you figure the timeframe is for a fix ?

Well that was a big fat lie… We’ve indeed fixed the shipping calculation issue, but now taxes aren’t properly rounded down – they’re always rounded up – resulting in a one-cent mismatch for Paypal, thus killing the transaction. We’re struggling here, using PHP_ROUND_HALF_UP doesn’t seem to do any good. We didn’t even know where this issue comes from in the first place, this setup has been working for months ! Now, if a transaction happens to fall down from .05, then it gets rounded up and Paypal complains. If it’s above, then the transaction goes thru resulting in a “lottery” for our clients ??

Thanks for your quick feedback. As a matter of fact, we managed to fix this about an hour ago. We rewrote part of wc-gateway-paypal-pro-angelleye.php to round off the shipping value being passed with 3 decimals.

We’re using Canada Post to calculate shipping and although it had been working fine for 6 months now, I can only imagine than an update broke this. I do believe there was an WC update on Friday morning, but I did not apply it so I’ll check with my colleague.