Updating Rise Audit Pro
Overview
Updating Rise Audit Pro should be done carefully, especially on production systems that already contain audit data.
What this article explains
This article explains how to update the plugin safely without losing logs or breaking the installation.
Why it is useful
- It reduces the risk of losing plugin files or custom changes.
- It helps administrators confirm the update was successful.
- It encourages backups before changing production files.
Who should read this?
RISE Admin, Server Administrator, Developer / Support Engineer.
Where to find it
RISE CRM plugin files and Rise Audit Pro → Plugin Health after the update.
How to use it
- Create a database backup.
- Create a backup of the current plugin folder.
- Download the updated plugin package.
- Replace the plugin files carefully.
- Do not delete database tables unless you intentionally want to remove data.
- Open Plugin Health and test key pages.
Example workflow
Before updating on production, an administrator updates the plugin on staging first, verifies Plugin Health, checks key log pages, and then applies the same update to production.
Common mistakes
- Replacing files without a backup.
- Deleting plugin tables during an update.
- Assuming custom file edits will survive an update.
- Skipping Plugin Health after updating.
Related articles
- Requirements
- Plugin Health Overview
- Deactivation and Uninstall
- Customizing Views Safely
