owenlenegan

I am also getting this issue with 4.9.4 and this is with brand new, fresh installs of the latest WP release so no plugin issues and all permissions and ownership settings are correct. Also using Chrome. Never had a problem before this version of WP and if I replicate the exact same install with the previous release the bug/error doesn’t occur.
Other than using an old release version of WP, has anyone found a fix for this?

Did any of you guys find an answer to this? Same issue. If I switch to ugly p=123 permalinks it all works fine but as soon as I use %postname% it breaks. I was so angry/determined to get this working I literally did a brand new base WordPress install on a different server – stock Apache2/PHP/MySQL settings and not a single plugin (other than UM, of course), base theme and zero additions to functions.php. Nope… still broken. If anyone has found the reason please let me know, I actually rather liked UM – it ran well and took mods like a champ on my last install but, now I realize, that site was running ugly permalinks (page=123). Does UM only work with ugly PLs?!

Hi Mike – Running WP 4.8.2 on Clean Commerce and getting the same error with Woo PP Gateway 1.4.4. Oh, I’m on Woo 3.2.1. Really weird because everything was fine for months and now I noticed the error message and cannot ascertain what the issue is. Like Theo, obviously Woo is (and always has been activated). Seem to recall having a nightmare experience by installing JetPack (never, everrr again!!!) around that time. Rid myself of JP and I haven’t noticed any major errors expect the PP Express Checkout message.

BUT! Following your instructions to Theo above re debugging logs, there’s clearly a big problem – lots of:
CRITICAL Uncaught Error: Call to a member function get_cart() on null in /var/www/meowwoofmeow/wp-content/plugins/woocommerce-jetpack/includes/add-to-cart/class-wcj-add-to-cart-per-product-type.php:52

I can’t see what that has to do with the PayPal Gate plugin, though. Any ideas?

Is best that in your apache2.conf write

<Directory /var/www/html/yourDirectory>
AllowOverride All
</Directory>
restart your apache and ready. Simple

Just remember that allowing open (‘All’) Override rather than using the ‘Options’ switch and being a bit more discerning with Symlinks allows .htaccess sanctioned files to overwrite a whole bunch of default Apache2 directives designed to prevent malicious code injection/execution. I say this after losing my last WP site to this vuln. Apparently its included ‘detected’ in some broad Metasploit/Burp scans as a medium level vuln too. Just sayin’!

I’m just getting – “Error: The API certificate is not valid.” for every PayPal API certificate even though it’s 100% valid and in the correct format etc. Had it reissued, then a brand new one issued… nothing. Woo says its invalid no matter what. Very weird given I have used Woo PayPal Gateway for years and it has always worked first time.