Akeeba Backup for Joomla!

Saturday, 03 December 2022 10:43 CST

dhillock

Hello,

I've read the following in detail

https://www.akeeba.com/documentation/akeeba-backup-joomla/restoring-backups.html#general-guidelines

And more specifically, these two paragraphs.

Do not restore in a subdirectory of your main site. For example, if your site's root is in public_html do not restore to public_html/dev. The reason is that the .htaccessfiles, which tell Apache (your web server) how to server your site, cascade. That is, Apache will read all .htaccess files in all folders leading to the one hosting your site'sindex.php file. This will cause problems with the restored site which you will experience as 404, 403 and 500 error messages or blank pages. These have nothing to do with our software and / or the restoration. It's how your web server works. Use a subdomain instead.

If you are restoring on a subdomain, make sure that the subdomain's root directory is NOT a subdirectory of your main site. This is the same as the previous paragraph, really. Most hosting control panel software default to using a subdirectory of your site's root when creating a subdomain. For example, if your site is www.example.com and its root is public_html if you create the subdomain dev.example.com your hosting control panel will put its root in public_html/dev. Therefore you will have the problem we described above. In this case ask your host what is the best way to create a root folder for the subdomain next to public_html, not inside it.

From the reading of the above, would this installation tree avoid the problem that are mentioned above.

Joomla Site-1 is stored in this folder: public_html/joomla1/

Joomla Site-2 is stored in the folder: public_html/joomla2/

Because right now I have the following (different names of course). As it turnes out, when I have domain issues, the support people always try and push my joomla1 and joomla2 folders into the public_html folder.

public_html/old_joomla_site/

public_joomla1/

public_joomla2/

Your feedback is appreciated.

David

Sunday, 04 December 2022 10:14 CST

nicholas

I would put www.example.com in public_html and dev.example.com in dev_html which is located next to (not inside of) public_html.

This is something I have, in fact, been doing on my sites for the past 15 years. If you are using cPanel you can do that yourself through its Domains page. For example, when creating a new domain deselect the "Share document root (...) with “your-site-domain-here”." and select a different document root for the subdomain as explained above.

This configuration is fairly trivial. If your host cannot figure out how to make a subdomain work with a web root outside the main site's root and they insist on putting two unrelated sites one into another(!!!) they are completely incompetent and you need to go to a different host.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 05 December 2022 08:03 CST

dhillock

Thank you for the feed back. Got it.

David

Support