100,000 inodes created by this plugin in under an hour

  • This issue of overwhelming inode creation has been known, and unaddressed, for 2 years now. (See original support thread HERE)

    It created so many that it put my account in danger of being shut down, and I’ve wasted hours today trying to clean up the mess by deleting all these files.

    I had to go in through my host’s file manager simply to stop the plugin, since it had used so many resources that I couldn’t load the admin panel.

    This is the second time today that I’ve had to do this, after trying to change the settings on the last forced shut-down and clean up.

    It not only didn’t speed my site up, it shut it down completely, more than once, with a problem that has existed UNRESOLVED for two years.

    I give it one star because that’s the required minimum to post a review.

Viewing 1 replies (of 1 total)
  • Thread Starter mugwumpr

    (@mugwumpr)

    The uninstall is also still as ineffectual as it was 2 years ago (link to original support thread HERE). Promises of a cleaner uninstall from the developer were clearly lies, since exactly the same files were left in my site as are listed in the thread from 2 years ago.

    It leaves garbage scattered throughout WordPress, files, database, and htaccess and is, again, a waste of hours to clean up completely.

    I really wish WordPress would allow us to give negative stars on a review. This plugin has richly earned a couple from me.

Viewing 1 replies (of 1 total)
  • The topic ‘100,000 inodes created by this plugin in under an hour’ is closed to new replies.