Support

Akeeba Backup for WordPress

#27739 – Upgarde 2.1.2->2.1.3 on WP 4.7.4 fails

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 12 May 2017 12:51 CDT
rogerco
Upgrade from 2.1.2->2.1.3 fails with message after downloading "Invalid AJAX data: Invalid archive type or extension in file"

IMPORTANT! Please remember to ZIP and attach your backup log file. Without it we are unlikely to be able to help you with backup issues. Thank you!

This is not a backup issue, 2.1.2 has been owrking fine. It is the upgrade that is failing. Downloads, but fails to extract.

Thank you
RogerCO

Custom Fields

WordPress version (in x.y.z format) 4.7.4
PHP version (in x.y.z format) 7.0.18
Akeeba Backup version (x.y.z format) 2.1.2
Monday, 15 May 2017 02:10 CDT
nicholas
There are two bugs affecting the updater in versions 2.1.0.b1 and 2.1.2 inclusive. Upgrading from these versions to 2.1.3 or later requires a manual update. Unfortunately the bug was at a place in the code that gets overwritten on update, making it impossible to test properly. We are working on a better way to automatically test the update to prevent that from happening again.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Monday, 15 May 2017 14:14 CDT
rogerco
In case it helps anyone else - if you can manipulate files on your host, then after a failed upgrade you will find a file called update.zip in the folder "wp-content/plugins/akeebabackupwp/app/tmp". To save downloading a fresh version and uploading it you can simply move the file to "public_html/wp-content/plugins/" (that's the level above the akeebabackupwp folder) and extract it there - assuming you have the facility to extract in place files - not all ftp clients will do this, but if you have cpanel access to your host then file manager lets you do this.
This will overwrite the files included in the update package in the akeebabackup folder.

I can confirm that this time it doesn't seem to overwrite your carefully crafted configuration (for some reason last time I had a update problem the profile values got set back to default ones which was very unhelpful).

I guess you can safely delete the update.zip file once you have extracted it - or you can move it back to the public_html/wp-content/plugins/akeebabackupwp/app/tmp folder where I presume it will be overwritten next time an upgrade is downloaded.
Tuesday, 16 May 2017 01:39 CDT
nicholas
This is correct. I didn't suggest it because it's not evident which version it has downloaded unless you download the ZIP file, extract it and inspect the version.php file.

You can also save the step of moving the file by uploading kickstart.php into public_html/wp-content/plugins and pointing it to Akeeba Backup's update.zip file. Kickstart is a very flexible archive extractor, it's not just for backups ;)


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Tuesday, 16 May 2017 12:40 CDT
rogerco
Thanks Nicholas, take your point about not being sure of the version but if you do it straight after a failed update I guess you should be ok.

Useful tip about kickstart : Your text to link here...

I'll flag this as closed now in hope that the next update works seamlessly :-)

RogerCO
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!