possible plugin conflict

Hi Danicholls,

You’ll find that plugin authors don’t respond to support requests placed in 2-star reviews. Since you’ve already given the plugin a really low mark, you’ve already given your verdict and brought down the plugin’s ranking, and there’s no incentive left for the plugin author to help you.

It could be any one of your plugins that breaks JavaScript in the WordPress dashboard, and it’s not fair to penalise UpdraftPlus by bringing down our ranking before you’ve found out which one it is.

David

Alright. You might consider not making all of your buttons rely on JS in the first place. Perhaps that’s a norm in WP admin interfaces, but it’s not a best practice anywhere else on the web, and this is a perfect example of why. I’m not seeking to penalize your plug-in, just reporting my experience, caveats and all. If I get time, I’ll go through the gamut of reinstalling your plugin, deactivating the others, potentially uninstalling the others, and all of that fun stuff, and revisit the review.

Here’s a relevant web page: https://updraftplus.com/do-you-have-a-javascript-or-jquery-error/

Use of jQuery/JavaScript is normal throughout WordPress (check out the list of most downloaded plugins, and see how many of them require it to function), so I’d appreciate if you were able to either delete the review, or reset it to nearer the ‘average’ value (it was 4.8 before this review, which brought it down to 4.7). Reviews equal reputation, and that equals my livelihood. I do actually lose sales if recent reviews are bad ones, and I can’t be all that thrilled about losing sales because UD doesn’t provide work-arounds for problems in other plugins or themes.

Fine. But it would make your plugin more robust if you weren’t at the mercy of others blowing up the JS for you. (Have no issue with JS anywhere else, btw, or without it. The conflict may be library-/namespace-based.) If you can do it, I hope you do.

Hi danicholls,

Thanks, appreciated.

We really can’t work around it – the UD page uses jQuery heavily, everywhere. It’d be a huge amount of work, and would be likely to benefit a tiny, tiny number of users (you’re the 3rd user I recall having this problem, and we’ve had 190,000 downloads (the other 2 users fixed it immediately after being pointed to the above instructions – one just needed to update his theme with an already-available update that fixed the bug)), and I can’t see any way we could justify that kind of effort-investment/pay-off ratio.

David