Support

Akeeba Backup for WordPress

#32698 – Update fails, blank screen

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.
Saturday, 21 March 2020 10:31 CDT
Burt
Hi Akeeba,

Just updated Akeeba Backup for WordPress to 7.1.0. After this update I can not create backups.
After clicking the button 'Update now' a blank page is shown, with this URL:
https://www.domainname.nl/wp-admin/admin.php?description=Backup+taken+on+Saturday%2C+21+March+2020+15%3A23&angiekey=&comment=

Nothing else, no message on the screen, just blank.

Prior to this update I had 7.0.2 installed and I just created a backup, without a problem.
After the update it doesn't seem to work. Have seen this behaviour now on several websites, same issue.

Hope for your advise.

Best regards, Bert

Custom Fields

WordPress version (in x.y.z format) 5.3.2
PHP version (in x.y.z format) 7.4
Akeeba Backup version (x.y.z format) 7.1.0
Saturday, 21 March 2020 13:25 CDT
nicholas
I am not sure I can follow you. The "Update Now" button in Akeeba Backup only appears when an update to Akeeba Backup is available for installation. If you already have Akeeba Backup 7.1.0 -- the latest version at the time of this writing -- there is no update available and this button is not shown. It actually reads "Up to date". Clicking it does not take you to the URL you said, it takes you to the update page where it tells you it's the latest available version. Moreover, Akeeba Backup 7.1.0 can take backups. All of the above have been tested not just on my development and test sites but also my own live blog, the latter earlier today i.e. after we made the release publicly available.

Please tell me:
  • Have you tried clearing your browser's cache?
  • Do you have any .htaccess code or a third party plugin which enforces caching on your sites?
  • Do your sites use CloudFlare, another CDN or a caching proxy such as Varnish?
  • How did you update Akeeba Backup. Did you use the update from inside the plugin itself or did you use the WordPress Plugins or Updates page? Please specify.
  • What exactly do you mean with "clicking the button 'Update now' ". Do you do that on version 7.0.2 BEFORE updating to 7.1.0? Because doing that on 7.1.0 is not possible since this button no longer appears. It's also unrelated to taking backups. These two points make your ticket very confusing and prevent me from helping you.
  • What do you mean with "I can not create backups"? What is the exact error message you receive when taking a backup? If you produce a backup log file please ZIP and attach it to your reply.


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!



Saturday, 21 March 2020 15:48 CDT
Burt
Hi Nicholas,

My apologies, I mixed up 'backup' and 'update' in my message. I'm sorry for that. Thanks for your elaborate answer.

The update of Akeeba Backup for WordPress works just fine, no problem here.

After the update to version 7.1.0 I noticed a strange behaviour with the button 'Backup now'.
In stead of creating a backup it just produced a URL and a blank page:

https://www.domainname.nl/wp-admin/admin.php?description=Backup+taken+on+Saturday%2C+21+March+2020+15%3A23&angiekey=&comment=

Nothing else, no message on the screen, just a blank screen.

I'm using Akeeba Admin Tools + its .htaccess creator, no CloudFlare or CDN, no other caching mechanism.
After clearing the browser cache the problem has gone, the 'Backup now' works just fine now. Thanks for your advise.

Again, sorry for the confusion.

Thanks and best regards, Bert

The ticket can be closed.
Sunday, 22 March 2020 04:43 CDT
nicholas
Ah, now it makes perfect sense :)

We have rewritten our backup software's JavaScript for version 7.1.0 to make it better performing. We replaced all inline scripts with JS files that can be better cached by your browser and we're passing script options from the backend to the frontend using an embedded JSON document. However, if for any reason the old script was to load on the new version you'd get wonky results like you experienced. Our solution to that is adding a script version query parameter when loading JS files (that's the standard way to do it). In some cases this may not work (e.g. because of browser options, a browser bug or a third party WordPress plugin which is overriding script version queries or combining loaded JS files) and that requires the browser cache to be cleaned.


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!



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!