Massive problem / evergreeen by this plugin: autoload issue

Normally, if you delete the plugin via the “Plugins -> Installed Plugins” page, it should automatically delete its settings. If you’ve already uninstalled the plugin using another method (e.g., by manually deleting the files), you could try installing it again (just install, don’t activate) and then deleting it as described above.

If that doesn’t help, could you be more specific about what the “auto load data” is? What is the largest table that you mentioned? Is there a specific table entry that’s very large?

Again, what data are you referring to? Is there a specific auto-loaded option that’s not getting deleted? If you’re sure that it’s related to this plugin (options it creates usually have names starting with ws_ or ame_), you may be able to delete it manually using phpMyAdmin or another DB management tool.

Why all other plugins working so much smarter which also handle menue in wp?

I assume this is a rhetorical question.

• This reply was modified 1 month, 3 weeks ago by Janis Elsts.

Ah, so you had the Pro version installed at some point. One thing to note is that installing and uninstalling the free version will not delete all Pro version data. It will only delete the settings that are also used by the free version.

In this case, you would need to install and uninstall the Pro version to clean up options like that. Or you could delete the ws_menu_editor_pro entry manually – that should be safe to do if the plugin has been uninstalled.

Not really. Please check your support threads. Its an evergreen and a lot of users stuck in this issue.

There are multiple user reports about the size of the menu configuration, and I do agree that it can get inconveniently large, especially on sites with lots of menu items and custom role settings. However, my impression was that this thread was about a different problem: settings not being cleaned up after uninstallation. I don’t think that has come up much before.

1. The next update will include some minor configuration size improvements, though enabling compression in the “Settings” tab will still be more effective. However, if you’re using the free version, this won’t have any effect on DB entries that are exclusive to the Pro version.
2. Since you mentioned Kinsta earlier, here’s a tutorial from Kinsta.com on how to clean up plugin data in DB tables:
   https://kinsta.com/blog/uninstall-wordpress-plugin/#cleanup-tables-in-phpmyadmin
   In this case, you would need to search the wp_options table for ws_menu_editor_pro and delete that entry. It’s probably a good idea to back up the database first.