• Resolved George

    (@chainkiller)


    After i updated to 1.2.0.rc1 the settings page displays the following error:

    ERROR! Could not load the backup engine; file does not exist. Technical information: Path to integration.php: /var/www/clients/client0/web6/web/wp-content/plugins/akeebabackupcore/helpers Path to factory file: /var/www/clients/client0/web6/web/wp-content/plugins/akeebabackupcore/helpers/../app/Solo/engine/Factory.php

    PHP Version: 5.6.2

    https://wordpress.org/plugins/akeebabackupcore/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author nikosdion

    (@nikosdion)

    It seems that 1.2.0.rc1 was not tagged correctly. 1.2.0.rc2 should be correctly tagged. If you have the same issue after upgrading to 1.2.0.rc2 please let me know what is your operating system.

    Plugin Author nikosdion

    (@nikosdion)

    We have found out what the issue is: some filenames are in lowercase when their first letter should be uppercase. We are preparing a new release (1.2.0.rc3) which will address this issue.

    WordPress.org uses a Subversion repository to provision the update packages to the plugins hosted in the Plugins repository. Unfortunately, this makes it impossible for us to test the packaging before actually releasing a version. On top of that, there is no feedback whether filenames are committed in the correct case or not. On the bright side, this version is the last one where a filename case change is required so we don’t expect this near-impossible to prevent issue to occur again.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Error after update to 1.2.0.rc1’ is closed to new replies.