Removed support for Akeeba Backup JSON API v1 (APIv1). APIv1 was deprecated since version 7.0.0 released in January 2020. It has been replaced by APIv2 which has been fully operational since version 7.4.0, released in November 2020. The old APIv1 was meant to be removed in mid-2022. Due to the pandemic, we extended its life by another year. Now, it's time for it to go away forever. If you are using a very old version of Akeeba Remote CLI or Akeeba UNiTE which does not support APIv2 you will need to update to Akeeba Remote CLI 3.1.0 and Akeeba UNiTE 5.1.1 respectively.
Removed support for the legacy Akeeba Backup JSON API endpoint (wp-content/plugins/akeebabackupwp/app/index.php). That endpoint was unreliable for use with some WordPress sites, especially those hosted on managed or "WordPress-optimised" hosts which prevented direct access to arbitrary .php files. We introduced the new endpoint wp-admin/admin-ajax.php?action=akeebabackup_api which goes through WordPress' AJAX entry point file in Akeeba Backup for WordPress 7.7.0, released on August 2022. While we allowed remote clients to connect to either entry point for a year and change, it is now time to disable access to the old entrypoint. Please note that the new entrypoint only accepts Akeeba Backup JSON API v2 (APIv2) calls. If you are using a very old version of Akeeba Remote CLI or Akeeba UNiTE which does not support APIv2 and/or the new endpoint you will need to update to Akeeba Remote CLI 3.1.0 and Akeeba UNiTE 5.1.1 respectively.
Re-enabled integrated updates with WordPress. We have now successfully tested that updating from Akeeba Backup for WordPress 8.1.0 to 8.1.1 and later versions will work just fine with the integrated plugins updater in WordPress. As a result, we are re-enabling this integration. Please remember that this will take effect in the next update, from 8.1.1 to 8.1.2 or a later version.
Bug fixes and minor improvements. Please, take a look at the CHANGELOG below.