Erik,
This plugin doesn’t save any data in the database outside of a post meta value ('stf_exclude'), which would not effect the “plugin page” (I assume you mean the admin screen for plugins?).
When you disable it on the network admin, you are essentially making it unavailable to network sites, so it shouldn’t appear on those sites unless you enable it. This sounds like, perhaps, a conflict with activating/deactivating from a network versus single site perspective? (Another article here)
That said, once deactivated the plugin will not function. This plugin does one very simple thing – it removes functions from WordPress action hooks (wp_enqueue_scripts, wp_print_head_scripts, and wp_print_scripts from the wp_head action). If the plugin is deactivate, or the checkbox (post meta) for a specific post/page is selected, these functions remain in the action hooks and everything works normally.
Because of the way action hooks work, these functions are always hooked into the wp_head action, then unhooked by the plugin – upon each page load. If the plugin is deactivated, the functions are hooked in and work. The plugin can’t do anything if it’s deactivated, and if it is not active those functions will be hooked into those actions and work normally.
Post meta would be removed upon deleting the plugin (through the admin interface, which will run the uninstall script which should clean the meta data). However, while the post meta would otherwise remain in the database, it will not do anything – it would just be “orphaned.”
Does that answer your question? I’m not entirely sure of the issue you’re having exactly, so if that doesn’t please be more specific on what is/isn’t being displayed and where.
Cheers,
Joshua
Erik,
I just looked back through the code and noticed that I don’t actually have the uninstall script set up correctly to delete the post meta, but instead to delete the (currently unused) settings field. In the next version I’ll fix this to correctly remove the post meta.
That said, your issue would be unaffected by this – orphaned post meta (if any, as it would only exist if the meta box was used) would not cause blank screens or activation/deactivation issues.
A little more information on your issue, if it turns out to be specific to this plugin, and I’m happy to problem solve and include a solution in the next release. Do you have debugging set up? If you’re getting a white screen of death, there is likely an error that is either not being displayed or is (potentially) being saved in a debug.log file.
Thanks,
Joshua
Erik,
I’m closing this issue since I haven’t heard anything. I’m working on a new version that should be out soon, but I haven’t fully tested on multi-site yet. That’s on my list of to-dos, though. If you need further assistance, please use the Github Issues or open a new thread on this forum.
Thanks,
Joshua
