How to Uninstall Easy8 Plugins

Introduction

Uninstalling a plugin in Easy8 must be done properly to avoid database issues and internal errors. Simply deleting plugin files from the system is not enough—plugins also store data in the database, which must be cleanly removed during uninstallation.

This guide explains how to safely uninstall Easy8 plugins using the built-in Rake commands.

Target Audience

Administrator

Prerequisites

Before starting, make sure:

You have access to the server terminal
You can run commands with the correct user (e.g., easy)
The application is in maintenance or downtime state (recommended)
You are working in the application’s root directory

Common Mistake

Do not just delete the plugin folder from the file system. This will cause Redmine to try loading non-existent components, which may lead to errors such as:

The single-table inheritance mechanism failed to locate the subclass: 'EpmActivityFeed'...

To properly remove a plugin, follow the steps below.

Option 1: Uninstall All Easy Plugins

Use this command to remove all Easy8 plugins:

rake easyproject:uninstall:all_plugins RAILS_ENV=production

You will be prompted to confirm the operation. This command rolls back plugin database migrations before removing them.

Option 2: Uninstall a Single Plugin

Use this command to uninstall one specific plugin:

rake easyproject:uninstall:plugin RAILS_ENV=production NAME=plugin_name

Example:
To uninstall the easy_budgetsheet plugin:

rake easyproject:uninstall:plugin RAILS_ENV=production NAME=easy_budgetsheet

If You Already Deleted the Plugin Folder

If a plugin was removed from the file system without being uninstalled:

Restore the plugin directory back to the plugins folder
Then run the appropriate uninstall command (as shown above)

Conclusion

Always use the provided Rake commands to uninstall plugins in Easy8. Never delete plugins manually without uninstalling them first. This ensures your database stays clean and avoids application errors.

If you’re unsure which plugin is causing problems, check the production.log for errors and restore the plugin before attempting uninstallation.