wpnbi

Thanks everybody for the help. I had more than 20 sites crashed and this thread helped me get them back up.

Hi kid5sparkle – thank you. Switching to the Authorize.net 2.0 worked for me too.

I was on Authorize.net AIM/CIM/ARB previously.

After doing that I wondered if this would be as good as the previous method – and what the differences were between the two methods. Here’s an article I found from WP E-Commerce (which happens to be my software for WordPress.

https://docs.wpecommerce.org/authorize-net-2-0/

I’m hoping to be able to get Authorize.net to come up with a solution so I can go back to using Authorize.net AIM/CIM/ARB, but in the meantime, your answer got me back processing payments – thanks ??

Here’s Authorize.net’s blog post. Apparently thousands of merchants were / are unable to process.

https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Production-Certificate-Upgrades-begin-May-27-2015/bc-p/50616

I’ve done everything in here and I’m still not processing.

Authorize.net want to know:
~ What is the Trace route to the api end point (I’m thinking end point is: secure.authorize.net – is that correct) ????

~ IP address of server (I know this)

~ List of all root certs installed on server (I’m working on trying to figure this out)

Hey Franz,

It’s not that simple.

I have about 170 installations of NextGen on client websites. Those clients often are the ones to click on the “upgrade” button – not me.

Those clients assume that when an update is available, it has already been tested and is ready for production – just like when their anti-virus software alerts them to an update being available – they install it and move on with their day…

For a considerably long time, NextGen could be trusted to not break a website. That clearly is no longer the case.

NextGen updates must now be regarding with suspicion and caution.

Please hurry up with the wp-cron and transients patch.

I have four servers that won’t sop running wp-cron jobs no matter what I do. Have upgraded to newest version of NextGen (2.0.25) but that has not stopped the wp-cron jobs

I’ve applied the new version (2.0.25) to all installations on one of my servers BUT the NextGen generated wp-cron jobs keep coming up non-stop…

Any one know how to help stop all of the NextGen generated wp-cron jobs?