v2.9.7.6

Safer Restores to Another Site, and xSpeed Database Cleanup Works With the Firewall On

This release fixes two problems you reported. Restoring a backup onto another site now keeps that site safe until the backup is in place. On OpenLiteSpeed, xSpeed’s database scan, clean and optimize work again without turning the firewall off.

🐞 Bug Fixes

• Backups
  • Restore to Another Site and restore to a new site no longer empty the chosen site before the backup arrives. Its current files and database are kept until the backup is in place. If the restore fails, they are put back.
  • A cut-short backup file now stops the restore instead of being restored.
  • A restore that is retried no longer wipes the site a second time. If there is not enough free disk space, or another restore of the site is still running, the restore stops and tells you why.
  • The restore window now says what really happens: “This replaces the files and database of the selected site with this backup. Its current files and database are kept until the backup is in place, and put back if that fails.”
  • This covers local, S3-compatible and SFTP backups. Google Drive and pCloud restores work as before. Restore a backup to another site
• Firewall
  • On OpenLiteSpeed WordPress sites, the built-in firewall no longer blocks xSpeed’s database tools. Database scan, clean and optimize now work, and their settings save, with the firewall still on. Every other firewall rule still applies.

Please note

• Existing OpenLiteSpeed sites with the 8G Firewall on: to get the fix, open the site’s Security page and, under Firewall rules, turn 8G Firewall off and on again. New sites and sites that turn it on from now get the fix by themselves. Enable the 8G firewall in xCloud