Support

Hello,

I've been using JoomlaPack for a while now and it has always worked great for me. I just recently upgraded to Akeeba Pro, I'm running 3.0 Stable. I have setup cron jobs to backup twice each day. I have been using a sub-domain as a development area for several months now and I am finally ready to push the site live to the root domain.

I created a new database for the live site to use, and I am indicating this to ABI in step 2 (DB Restore). But every time I try to move my site to the root domain, I get the error: "No database definitions were found or no database was selected."

I have tried over 10 different backup files and each one fails at step 2. I am using BlueHost, and my development site is backing up directly to my server. I am then copying the backup file to new location using CPanel File Manager.

When Akeeba is performing a backup, the step "Finalizing the backup process" takes an unusually long time. The "Last server response" message hits 110 seconds before it refreshes a few times and finalizes the backup. Akeeba confirms that the backup is complete, but this seems like a very long time for a server response.

I am not sure what else I can try to get this fixed. Any help would be greatly appreciated.

The error message indicates that the /installation/sql/databases.ini file is not present or can't be read. If that file is there, it may be a permissions error. Flag the /installation folder, sub-folders and files 777. (Some servers will throw a 500 error on files flagged 777, back it down to 755 if you get a 500 error.) There is usually a flag in your ftp client to apply permission changes to the entire tree instead of just the current folder.

I got this working. The databases.ini file was there, but ABI wasn't updating that file with the new database information I was feeding it in the GUI.

So I manually edited the databases.ini file so that it contained my new database name, user and password. Once that was done, it installed just fine.

Another issue that cropped up: I tried backing up as a ZIP file and it kept stalling out. Not sure if anyone else is experiencing that issue, but it might be something to look into.

Thanks for the help!

I didn't think the installer updated databases.ini. That should hold the default login details for the databases. The Joomla! database information is updated in the configuration.php file, any other databases wouldn't be written anywhere. Oh, well. I'm glad you got it working.

The zip file format is much slower than the jpa format. This is due to the calculation of the internal CRC32 checksums that the zip format needs. The time difference isn't much on a human level, but it is significant on a computer level.