Support

Good evening

Of all the years using Akeeba this is the first I've had to submit a ticket. I will try to give you as clear information as possible.

I am writing with a restoration issue for waynemallows.com

Earlier I went to move a site from my development location to my clients. (both on Abivia hosting) The first restore started the usual steps then went live without going through the database and other configuration settings but restored the site looking correct. (in hindsight I should have left it like this but wanted the complete site moved.) This had happened to me with a previous build I had done and it seems it was auto linking to the DB in the development area. (if it is helpful the URL for this instance is live hopeandharry.com and it is linking to a DB at my dev alisonmeeks.com all on Abivia.com) When I saw Wayne's site do the same thing this morning I made sure I had both of the current full backups downloaded and removed my developement site. Upon trying to restore next I got an Akeeba error message "Insecure setup detected". #21301 said I should rename my kickstart.php which I did and proceeded with my restoration (I also double checked my file size per the note on this ticket). It seemed to be progressing correctly, asked me for the DB info etc but upon completion the front end was broken code and it was not allowing me access to admin at all. Back to CPanel and removed everything and started fresh this time using the other backup - this one gives me the Angie password error. I had seen discussion on the forums about Chrome auto filling so typically made a point to delete this field. Anyway it is looking for a password and it isn't the super admin password. After searching the support area again and finding #18328 it suggests removing password.php but when I do I'm not getting a restore.

I have not tampered with the Akeeba Pro standard backup settings (don't touch what you don't know) and have done many restorations over the years I've never run into this.

I have attempted to review applicable files prior to submitting a ticket but have been unsuccessful.

Thank you in advance for your assistance,
Alison

NB: With assistance I was able to get this resolved. (thanks Alan) A stupid mistake on my part and live_site. (note to others - leave this area blank)

What is still a mystery is why it was automatically hooking back up with the DB on the dev URL vs following it's steps. If you have any ideas on this I would be grateful to hear them.

Thanks again,
Alison

The restore checked and found that it could connect to the original database, so it assumed that you were restoring the same site. The default database settings were retained when you restored and you connected to the same database as you backed up.

The easiest way to correct is to reinstall and use the correct database connection information for your new site.

It didn't get as far as asking me what the connections were supposed to be Dale. It jumped past that several times on two site restores. :/

Thank you

That I can't explain. Regardless of whether it is restoring to a new server or the same server it should show you the database connection screen. The difference is whether or not it shows you the default connection settings.

Beats me too Dale but it has happened a couple times and didn't show me the screen so I thought it worth mentioning.

Thank you again :)