WTFSPARK

@polsola Worked like a charm! Made sense now that I think about it..Thanks!

For the sake of clarity, I resolved the issue by disabling the plugin, then upgrading to the latest version, from 2.4.7 to 2.4.8, which as I stated fixes A LOT of API issues! Which this is clearly an API issue. Now everything is working as expected.

@caugas That Makes sense. My client is on Media Temple, however Media Temple was acquired by Godaddy and uses the same setup, as their shared hosting is powered by Godaddy now. That’s how I made the assumption from the error you and Richard posted.

*A manual reset is easy. You’re essentially just renaming the plugin folder to disable the plugin(s).

Disabling the plugin and re-enabling works for now. The latest Woocommerce version 2.4.8 released 10/26/2015 fixes a slew of API issues, so it may remain stable. Only time will tell since I can’t manage to recreate the error for now.

Having the same issue here. It looks like everyone experiencing this issue uses Media Temple or Godaddy. My client is using Media Temple. Anyone else?

*I’m currently working on this issue now. I disabled woocommerce for now to get the site working till I find a solution. I’ll follow up with an update and encourage anyone else to do the same.

@tdox81 I’m looking for the same thing for an Entertainment blog. Please keep me posted if you find or found something that works. I’ll do the same on my end if I come across something first. Thanks!