Chapter 5 of 8
Updates and care
A safe approach to updates and a record of the work done.
For managing WordPress, depending on your permissions
Before every update
- Make sure you have a current backup of the site and can restore it with your hosting or backup provider.
- Check that digiWatcher Agent is communicating and its data is up to date.
- Read any warnings and choose a suitable time for the work. For a sensitive site, test the change on a staging copy first.
Restoring the original files after a failed update doesn’t replace a full backup of the site and database.
How to do it in digiWatcher
The agent uses the updates that WordPress itself offers. digiWatcher isn’t meant for installing new plugins or editing their files. If the core details only show information about a new version, update directly in WordPress following the on-screen instructions.
- Open Updates in the main navigation, or WordPress → Updates in the website details.
- Choose the website and the offered update. Running updates must be allowed for that website; connecting the agent alone doesn’t confirm that every action can be performed.
- Follow the allowed actions and the confirmation dialog. If an action isn’t available, first resolve the reason shown in the app.
- When it finishes, check the job result, the site’s uptime, and important features, for example a form or an order. If something fails, assess the state first; don’t run another batch blindly.
Record the care you’ve done
In the website details, record the work done under History → Care history. Note what changed and with what result. Before sharing with a client, check the record’s visibility; internal notes are for your team only.