Every WordPress stack is different, and rollback coverage is extended to new configurations with every release. When something cannot be undone, Foenix tells you right away instead of reporting a false success. Rollback is a safety net, not a backup: always keep one at the hosting level. Backups →
How rollback works
Before Foenix modifies your site, the previous state is saved. If the change causes an error, Foenix detects the problem and reverts to the saved version automatically. You can also trigger a rollback yourself from the Rollback button in the session.Honest by design
After a rollback, the session reports exactly what was reverted and what was not. If a change could not be undone, you see it immediately in the session and can act on it, instead of discovering it later.What rollback covers
- File changes: theme files, plugin files, snippets
- Post and page content, including long posts with images and SEO meta
Limitations
- Settings and options changes are not reversible via rollback
- If the site is completely broken and the dashboard is inaccessible, rollback cannot help - restore from a hosting backup instead