Manually Removing Plugins

Overview

  1. Contact the plugin developer and ask for guidance.
  2. Review the below Plugin Package Uninstall References with the plugin developer to ensure their instructions are complete.
  3. Write up a list of changes you plan to make
  4. Test changes in Dev environment first if possible.
  5. Document changes in your change log.

Plugin Package Uninstall References

  1. Locate the plugin packages associated with the plugin you want to remove:
  2. C:\inetpub\wwwroot\App_Data\RockShop
  3. Copy the .plugin files to another local folder.
  4. Rename each file to have a .zip extension instead of .plugin.
  5. Explore each uninstall folder in each zip file which may contain:
    • deletefile.lst — this text file documents files to delete relative to the application root when uninstalling the plugin.
    • Uninstall SQL files per Rock RMS database migrations.
    • Note: Many plugins do not include uninstall SQL files which makes them difficult to fully delete without guidance from the plugin developer. Instead they use custom assemblies which are supposed to include down migrations. 
  6. The uninstall deletefile.lst and the uninstall SQL/migrations should take care of the following:
    • Remove the plugin folder and its contents: wwwroot\Plugins\[Plugin Provider]\[Plugin].
    • Remove files added to the bin C:\inetpub\wwwroot\Bin in IIS. See warning here related to these deletes.
    • Note: Deleting files from the bin will cause rock to restart (and recompile?).
    • Remove pages, attributes, groups, etc., the plugin specifically added in Rock. Note if you are going to remove pages manually it is best to do so before you delete plugin related bin files.
    • Consider deleting related SQL objects (tables, views, indexes, etc.) the plugin provider specifically created.
    • Consider deleting data generated when using the plugin (e.g., background checks, pastoral care requests).
    • Delete application data created by the plugin in records in tables such as BlockType.
    • Update \wwwroot\App_Data\InstalledPackages.JSON.

If possible, remove the purchased plugin from your organizational profile. According to the core team, this is not currently possible.