12/21/2014 at 9:02 am
#313255
Keymaster
@ Mike
Honestly, no clue because it is a core WordPress error. A few minutes of searching suggests this is being caused by hosts upgrading their servers to patch the shellshock security vulnerability. Two solutions seem to exist … waiting a few hours and restarting apache.
Hope that helps!
