Restoring individual files is safer than replacing the entire account when only one component is damaged, but you should always validate the file version before overwriting production content.
Common symptoms
- A single config file was deleted
- Only one template or asset is broken
- You want to avoid rolling back recent site changes
Troubleshooting steps
- Identify the exact file path and compare timestamps between the live file and the backup copy.
- Download the live version first so you can revert if the restored file introduces new issues.
- Replace only the required file or folder rather than extracting the entire backup over the site.
- Test the specific affected function immediately after restore.
- Document what was restored and from which backup date for future troubleshooting.
Additional notes
- Restoring old configuration files can reintroduce obsolete database or domain settings.
- Always keep a copy of the current file before overwrite.
When to contact support
Contact support if you are unsure whether a restored file will affect other dependent components.