Nice to see you’re working on Plugins, does that mean we’ll get a fix for the Plugin.Deactivated event’s bug? It fires both when the plugin is deactivated, and also when the plugin is activated which of course can cause some major headaches, espeically for the first time people are learning to create plugins (I speak from experience on that one). At the very least could the documention for this event be changed to notify people of the issue? This was reported almost 3 years ago in this thread, but nothing ever came of it.
3 Likes