Verwijder plug-in gegevens alstublieft!

AI-generated summary

In a support thread titled “Remove plug-in data please!”, nathank seeks help to completely wipe corrupt data from the Custom Wizard plugin, noting that simply uninstalling and reinstalling won’t delete the data. angus provides a command-line solution using Rails console to destroy plugin-specific data via PluginStoreRow.where(plugin_name: 'custom_wizard').destroy_all, and optionally logs with custom_wizard_log. He cautions that this method may not work for all plugins, as storage methods vary angus. He also notes that the Custom Wizard plugin includes a built-in “Manager” tool that can achieve similar results angus. nathank thanks him and agrees to post details of the issue on thepavilion.io for further discussion. The thread highlights a practical workaround for plugin data cleanup, while emphasizing plugin-specific differences and available UI tools.

I’ve got a plugin (unofficial of course) which has collected a bunch of corrupt data which is causing problems. Can you help me to sort it out?

What I’d like to do is wipe out the data associated with the plugin (in this case Custom Wizard Plugin 🧙) and start afresh.

I know that if I just uninstall the plugin and re-install it, the data will be preserved:

This is not what I want. I want that data wiped!

I love the plugin, but have clearly pushed it a little too far. @angus - you might have a clever trick for me too of course.

Hey @nathank.

If you’re absolutely sure you want to do that, you can do this in your server command line

./launcher enter app
rails c
PluginStoreRow.where(plugin_name: 'custom_wizard').destroy_all

Note that this will not destroy all logs associated with the custom wizard. To do that you can do the following. There shouldn’t be any reason to destroy logs however, unless you have some kind of privacy concern.

./launcher enter app
rails c
PluginStoreRow.where(plugin_name: 'custom_wizard_log').destroy_all

If you have time please make a post here describing the issue as you see it: Pavilion.

Thanks Angus - that is amazing service! I’ll post about the issue I encountered there.

Now, the method above should work for any plugin, huh? Sweet.

Not necessarily unfortunately. Different plugins use different storage methods.

I would also just note that the Custom Wizard Plugin has a “Manager” which you can use to essentially do the same thing. I’m interested to learn what issues you had, but let’s continue the conversation over at thepavilion.io.