Ideas and Pixels

Okay, thank you. That would be great.

@fortispay Sure! We just created a new order manually in the system with an order status of “Pending Payment”, then used the “Send Order Details to Customer”, which sends an email about completing the order by filling out payment details with a link like this:
/checkout/order-pay/637567/?pay_for_order=true&key=wc_order_eEJlMHttol5RI

That is where we see the Invalid settings for Fortis Gateway. Please check your configuration. message.

Thanks for your help!

And, yes, I rant — you would, too, if every few months your entire day was hijacked by an update that breaks your store. I stayed silent for a year or more hoping you guys would clean up the way you push updates. I love Woo, but someone seriously needs to manage your production pushes.

Thanks for attempting to help, Mike. My issue keeps stemming from the ->payment_complete() method. Can you confirm this is deprecated or changed?

I’ve been using WooCommerce for years. I’ve supported you guys with dozens of premium purchases. But everytime a client wants to upgrade, it breaks so many things. I searched for solutions, only to find the same suspects copping out time and time again.

Just upgraded another site today and what do you know — Authorize.net AIM has broken upon checkout. Of course it did.

There have been a number of times that updating Woo has broken my sites, but this one takes the cake. Whoever makes this needs to do some serious unit testing before releasing.

I’m having this issue, too. I would imagine this has cost us thousands already… no response, nothing.

My god, what’s with this Mike Jolley guy? He alone makes me never want to use WooCommerce again. I hate when developers break things (even if they thought they were “fixing” them), then refuse to shoulder any blame. You, sir, are giving your organization a terrible name. While your answers are valid, they are not compassionate in the slightest. You seem to have no care that we’re having these issues.

The answer was the op caching component. I removed it from the configs and everything is working as normal now! Thanks so much, David!

I’ve tracked it more specifically. It’s dying here (pardon my “oops” logs, those help me identify where it stops firing. It stops at Oops 4, so the require is broken it seems.

$this->log(‘Oops! 2’);
$backup_files = $this->jobdata_get(‘backup_files’);
$this->log(‘Oops! 3’);
global $updraftplus_backup;
$this->log(‘Oops! 4’);
// Bring in all the backup routines
require_once(UPDRAFTPLUS_DIR.’/backup.php’);
$this->log(‘Oops! 5’);

There’s only a single thing, that I would imagine is unrelated:

[23-Jul-2015 21:09:01 UTC] PHP Warning: Module ‘ming’ already loaded in Unknown on li…

Thanks, David.

I put this in my wp-config.php, functions.php and in a plugin:

if (!function_exists(‘gzopen’)) {
function gzopen($filename , $mode, $use_include_path = 0 ) { return gzopen64($filename, $mode, $use_include_path); }
}

Still not working.