Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.14
PHP version: 5.3.25
MySQL version: 5.5.32-cll
Host: Blanye
Akeeba Backup version: 3.7.10 and 3.8.1

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
Apart from doing regular backups, I've been using Akeeba for creating test sites on my host.
If I have an issue that I'm working on, I'll do a complete backup, and use the kickstart script to unpack it in a seperate folder, and with a seperate database. The database is created from scratch, and the user created for the test site only has access to that database.
If a developer is then doing some debugging they can get full access without compromising the production site.
But I'm seeing 'entangled' websites all of the sudden.
I can see the files get restored to the correct location, and I can see that the database is restored to it's correct location as well, ie. it's own database.
But if I go to the site, it's not the 'testsite' I modify, it's the production site, which gave me some terrible problems :-).
I'm not sure if it's admin tools or akeeba that gives this headache, but I've tried going back to the standard joomla .htaccess to cut down on possibilities, and that didn't help.
So where do I start with solving this?
If you want to see it for yourself, I can of course give you access to the site...
I've contacted the web hotel, but they haven't changed anything for quite a while, and the big update they are working on is not to be rolled out until saturday.

The database information would be stored in configuration.php, the .htaccess file would not affect it. Have you done something "fancy" with your config file, like moving it to another directory? That would cause exactly what you are seeing.

Dale

No, nothing fancy like that, the only thing that has changed recently is that it is now running ssl.

Please log in to your test site via FTP and view your configuration.php file. (Or download and view it, whichever is easier.) You should be able to see the database connection information in the file. I think you are going to see the database information for the live site. That is why the sites are entangled. This can be caused by:

1. During a restore to the same server, the restore script will present the database connection information for the live site that was backed up. You need to replace that information with your test site database information.
2. You entered the proper database connection information for the test site, but the configuration.php file was not writable. In this case the restore script will tell you that, but if you're not paying attention you could miss it.

Dale