What's new

This is a bugfix release, addressing the issues not caught during the beta stage of version 7.0.

PHP versions supported

We only officially support using our software with PHP 5.6, 7.1, 7.2, 7.3 or 7.4.

We strongly advise you to run either of the two latest available version branches of PHP on a branch currently maintained by the PHP project for security and performance reasons. Older versions of PHP have known major security issues which are being actively exploited to hack sites and they have stopped receiving security updates, leaving you exposed to these issues. Moreover, they are slower, therefore consuming more server resources to perform the same tasks.

Kindly note that our policy is to officially support only the PHP versions which are not yet End Of Life per the official PHP project with a voluntarily extension of support for 6 to 9 months after they become End of Life. After that time we stop providing any support for these obsolete versions of PHP without any further notice. New version branches of PHP will be supported experimentally starting sometime during their Release Candidate phase and fully about 4 to 8 weeks after the first stable version of that branch is released.

WordPress versions supported

We officially only support the latest WordPress 5.x release.

Our software should also work on WordPress 4.9 and ClassicPress 1.x since we do not rely on any features added in later WordPress versions.

We fully support single site and multi-site installations of WordPress. Multi-site installations can be converted on restoration from directory-based to subdomain-based or vice versa. You cannot restore a single site backup into a multi-site installation. You cannot restore / convert a blog of a multi-site network installation into a single site WordPress installation (in fact, there is no official WordPress method to do that safely).

We do not recommend using our software with WordPress versions earlier than 4.6 as some WordPress features we rely on for our software to function properly did not exist in these vintage versions. We generally strongly advise against running old, no longer maintained versions of WordPress for security and performance reasons.

Changelog

Bug fixes

• [HIGH] An error about not being able to open a file with an empty name occurs when taking a SQL-only backup but there's a row over 1MB big
• [LOW] Backup log file did not appear correctly (but you could still download it)
• [LOW] Dark Mode: modal close icon was invisible both in the backup software and during restoration
• [LOW] Dark Mode: some interface elements (e.g. footer, modal chrome) would always appear in their Light Mode scheme
• [LOW] Fixed automatically filling DropBox tokens after OAuth authentication
• [LOW] Notice in Control Panel when maximum error reporting is enabled
• [LOW] Redirections for the legacy frontend backup method should be to remote.php, not index.php

Removed features

• pCloud: removing download to browser (cannot work properly due to undocumented API restrictions)