This feedback doesn’t make a lot of sense to me – since the plug-in does not affect a site database or make any other changes that cannot be rolled back by simply de-activating the plug-in, for example – or better by adjusting its options. It’s incapable of “destroying” anything.
sorry for being so assertive but actually it did.
after activation, clicked in the main dashboard and it just would take forever to load. Tried loading another dashboard page in another tab and the same happened – just wouldn’t load, would stay loading forever.
going to the site fronted and it loaded, but all the images were replaced by the nag image. That site uses a page builder, with over 50 pages built like that and over 500 articles in standard wp style. All the images, no matter which, were messed up.
And the backoffice just wouldn’t load. VPS load skyrocketed to 400% (and it’s usually below 10%).
So the only solution was to ftp and delete the plugin dir. Which led to a terribly messed site, luckilly had a semi-fresh backup and managed to save the day.
site is hosted in a VPS, wp multisite with wp super-cache, jetpack, akismet, wordfence, domain mapping, enfold theme with page builder.
Maybe the plugin isn’t suppose to do that, but it actually did: I had no control of what it was doing after activation, couldn’t even go to it’s options page. IMHO it shouldn’t fire-up upon activaton, just after going though the options page and having the admin clicking in the buttons. And maybe it works OK in smaller blog-style WP sites, but clearly isn’t prime time ready for CMS style sites, with probably more complex iterations regarding how images are attached to posts.
I understand you probably invested some time in building this plugin, which is something to be cheered, and am sorry for being so candid (or so blunt), but it’s the feedback I have.
From your own description the plug-in did not “destroy” your web site. You experienced some inconvenience, and, if you had thought through what you were doing when you first installed and activated the plugin – loading a version 1.0 of a plug-in that comes with warnings that it may not be appropriate for non-standard sites – that inconvenience should have been minimized.
I would need to know more about your site (link?) to understand – and potentially to re-produce whatever occurred – but having a backup available should be standard practice. In a normal installation, the plug-in does nothing until the user has altered default settings, so your one suggestion doesn’t on the surface make sense. I also have no idea why you felt you needed to delete your entire plug-in directory, if that’s what you are saying you did, when there are many ways to remove a problematic conflict – most obviously by removing the particular plug-in instead.
Leaving a 1-star rating and advocating that the plug-in be removed from the Repo, and then disappearing for nearly two months is, to say the least, not very helpful to me or very illuminating for anyone. I’m not going to say anymore, since I have no interest in making this personal. If you want to investigate the problem further, we can do that, and you can contact me directly if you wish to do so. In the meantime, I will make the cautions about using the plug-in on a non-standard site more emphatic.
