Backups. Backups. Backups. This is the most important habit when using Foenix. Make a backup before every session where you plan to make changes. No exceptions.
Why backups are critical
Foenix has full administrator-level access to your WordPress site and can modify files, the database, plugins, and themes. If something goes wrong - an unexpected conflict, a PHP error in generated code, or an incomplete agent run - the fastest recovery path is always a recent backup. Foenix has a Rollback feature for some file changes, but it does not cover everything - especially database changes, published content, and settings.
Where to make backups
Always back up at the hosting level - not inside WordPress. A backup plugin inside WordPress only protects you if WordPress itself is still running. If the site breaks completely, you need a backup that exists outside of it - on your hosting server or in cloud storage. Most hosting providers offer:
- Automatic daily snapshots (cPanel, Plesk, Cloudways, etc.)
- One-click restore from the hosting control panel Check your hosting dashboard and enable automatic backups if not already active. If your hosting doesn’t provide snapshots, use a backup plugin that stores copies outside your site - for example UpdraftPlus or BlogVault with cloud storage. The rule stays the same: the backup must survive even if the site doesn’t.
Sandbox and staging
The safest way to try a risky or bulk task today is the built-in Sandbox: a WordPress copy on our servers where you can rehearse the task before running it on your live site. Quick Start → A built-in Staging feature that clones your own live site is in the works. Until then - for changes on a live site, please rely on backups at the hosting level.
When to make a backup
- Before any session where you plan to make edits
- Before running an agent for the first time
- Before modifying
functions.php or theme files
- Before installing or modifying plugins