Support

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.

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 :)

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.