Support

Akeeba Backup for WordPress

#25570 – Backup directory path & missing site name

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.
Sunday, 10 July 2016 12:21 CDT
appnweb
Hello,

We are using Akeeba Backup for Worpress in Wordpress courses we are giving to beginner and advanced students (core version because we are not allowed to use paid extension). During those courses, the students have sometimes to extract a backup and restore it on another subdomain of the same domain.

Doing that we noticed two details that may be annoying especially when learning to use WP :

- The backup directory path does not update during the restore (same domain or another) except if specified manually in the replacements and that means you have to know the exact path of the new folder. When restoring on another domain, running the configuration wizard fix the problem getting the path back to the default directory. When restoring on another subdomain of the same domain, this does not work as the directory exists. Sometimes in that case, the directory browser does not work properly, maybe due to the directory being outside site root. And it's not easy anyway for the students to browse back to their new subdomain folder even when the browser is working. Is it possible either to fix that or to add a button to reset the default directory ?

- Some of our students deleted the site name in WP before doing the backup. That got us to notice that if the site name is empty, the restore runs normally all the way but then the website can not connect to the DB. I admit it's an unusual case but good to know anyway and probably easy to fix for you.

And by the way a big thanks for the wordpress version ! It's great for us you made it.

Custom Fields

WordPress version (in x.y.z format) 4.5.3
PHP version (in x.y.z format) 5.6
Akeeba Backup version (x.y.z format) 1.9.2
Monday, 11 July 2016 02:57 CDT
tampe125
Hello,

thank you very much for your reports.
  1. You are right, that could be pretty annoying. Let me see if we can find a workaround for it
  2. Well, to be honest you should never do that. However thanks for reporting, we will try to add a new check on this.


Davide Tampellini

Developer and Support Staff



Italian: native

English: good



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



Monday, 11 July 2016 23:26 CDT
appnweb
Tanks for your answer.

Of course, you are right about the site name that should never be empty but unfortunately WP allow that and it should not either.

I don't know why the student of our example did that, probably because he wanted to hide the sitename on the frontend and choose the wrong way to do it.

That's the advantage of teaching, you encounter issues you will never have known about by yoursfelf :)
Tuesday, 12 July 2016 01:22 CDT
nicholas
Thank you for your feedback! We will include a fix for this issue (i.e. not allowing you to leave the site name empty) in the next release of Akeeba Backup.


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!



Thursday, 11 August 2016 17:20 CDT
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
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!