Tim

I just had the same issue too. I searched for “WP help jaquith” which did the trick. (Jaquith is the author name)

• This reply was modified 7 years, 3 months ago by Tim.

I’ve just had the same issue with Vidahost (part of the Paragon group along with TSOHost).

Did anyone find out what the issue was?

I saw that this plugin had been flagged as an issue with WP4.3 so I’m glad to see you’ll have it fixed within the next 10 days.

I really like this plugin, thanks!

I’d like the option to specify category (or even selected categories) as I have posts that I’d prefer not to have the bar to be displayed.

The workaround does work thanks. I forgot about it and came back to find my original posting!

I’ve put resolved as the changes can be saved, but still a mystery why the buttons don’t work.

Are you using Jetpack? You’ll see ‘feedback’ if you have jetpack forms switched on and there’ll be a conflict.

I cloned the site, upgraded the plugin and there appears to be no problem.

The only differences:
1. updated the plugin instead of installing a fresh 3.0.1
2. not connected Jetpack to WP
3. not scheduled a backup job to complete

BTW I’m using the TwentyFourteen theme. I’ll try and whittle down the above list over the next couple of days (need to update because of the RSS load time).

I can’t give admin access to my site at the moment, but I have cloned the site and am waiting to see if the issue occurs with the cloned site.

Photon doesn’t remove images because when deactivating the setting you’d need to use the media that you’ve uploaded. So it doesn’t look like Photon is the issue..

Here are my plugins (not for the website where the image is hosted though). If others have anything in common, please say so.
<img src=”https://timothyjefferson.com/plugins.png”&gt;

Do any of you use the Jetpack plugin, with photon activated?

Yes, this appears to be the case.

I don’t know if a conflict has caused this to happen.

3.0.1 was the version I installed originally (only came across it on Friday).

I guess I’ll wait until the next version is released before wrestling with an update. If there is a conflict with something else, maybe it would have been resolved by then.

Interested to know what has changed in 3.0.1 to cause such catastrophe…

Let me know how I can help.

I wouldn’t have selected it it if it was an option (was it a default in 3.0.1?). I can’t see that option in 2.67.68 though, which is what I’m now using.

Yes, same here. I’ve added a post to this forum. Have ended up using v2.67.68 instead.

First time using the plugin, so hope it’s fixed soon! If the fix is as fast as customer service, i’m sure it won’t be long ??