robnalexpress

GoDaddy – ugh – too bad. Here’s just one of many themes explaining why they don’t recommend GoDaddy.

Have you guys talked to support at your hosts? My issue was the exact same as yours: 4 WordPress sites on the same VPS, but only one having issues with saving featured image. Maybe you guys just like the challenge of trying to fix things yourselves, but that’s a time eater, so I opened a ticked with my host and the tech investigated and fixed it in less than 40 minutes by whitelisting script that was causing ModSecurity errors.

Have your host check for ModSecurity errors being tripped by the IP in question and whitelist the script causing the error. As I posted above this solved the problem for me.

My fabulous host, liquidweb, solved it for me. Here are the Tech’s comments:

“I did find a few ModSecurity errors being tripped by the IP this ticket was created for. I have whitelisted the script causing the error.”

My fabulous host, liquidweb, solved it for me. Here are the Tech’s comments:

“I did find a few ModSecurity errors being tripped by the IP this ticket was created for. I have whitelisted the script causing the error.”

My fabulous host, liquidweb, solved it for me. Here are the Tech’s comments:

“I did find a few ModSecurity errors being tripped by the IP this ticket was created for. I have whitelisted the script causing the error.”

Same issue here on 3.4.1. No problem on another site on same WP/Theme versions. Any ideas?

Saving featured image hangs for me in 3.4.1. Any new ideas?

Reinstalling didn’t work for me on 3.4.1. Anyone have a fix?

@carpecollum-

Some of your audios, like the one on this page, are still not playing.

@carpecollum-

Check to see if your audio files contain any unusual characters, such as “é”. I went ahead and replaced audio player with oEmbed HTML5 audio, only to find the same thing happening with files that contained this character in words such as Dupré or Fauré. Renaming those files fixed the issue in oEmbed HTML5 audio, and although I haven’t tested it yet, I suspect it may have been the same problem with the “file nor found” in audio player, since it was the same MP3s with the “é” in them.

Solved. It was a Headway Theme issue.

I don’t think W3TC is working for me with WP 3.4.1. I completely uninstalled and re-installed W3TC, and while everything appears normal in the WP admin, I don’t think the plugin is actually working.

Anyone else experiencing this?

The audio files are on this page. They are inserted into the WordPress page like this:

[audio:https://robreillyorgan.com/wp-content/uploads/2011/11/Prelude-in-G-Major-Bach.mp3|titles=Prelude in G Major - Bach]

What if I just change the link to:

[audio:https://robreillyorgan.com/static/wp-content/uploads/2011/11/Prelude-in-G-Major-Bach.mp3|titles=Prelude in G Major - Bach]?

Specifying the file location on the self-hosted CDN in the plugin settings has no effect. This is really not a big issue for me. is there any advantage to having the mp3s served from the self-hosted CDN?