Support

Akeeba Backup for Joomla!

#12544 ABI with multiple Databases not going to the next page

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Tuesday, 05 June 2012 01:13 CDT

user51436
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.4
PHP version: 5.3.1
MySQL version: 5.1.44
Host: localhost
Akeeba Backup version: 3.5.1

Description of my issue:

I do a full backup of my WebSite everyday using Akeeba Backup, and download the backup file with my FTP program using Binary Transfer Type.

From time to time (as advised by the Akeeba team), I test the backup in my local machine (Mac OSX with XAMPP).
My last restoration was using ABI 3.3.13. And, since yesterday, I am trying to restore my last backup (that uses ABI 3.5.1) with no success.

With any files that uses ABI 3.3.13 (I tried 3 different backup files with this version of ABI), the sequence is correct as following:
(using kickstart 3.5.1)

1) The system extracts correctly all my files and present me "Run the installer";
2) Show me that my local server has only "Display errors" setting without the recommended configuration (I click Next);
3) The system present me a "Warning Dialog" that is ok, and I click "Yes";
4) The first DB is "Site's Main Database";
5) The "Database type" is already filled with "Mysqli";
6) I fill out the form: Database server host name: 127.0.0.1 (tried localhost as well), User name, Password, Database name and click Next;
7) The progress bar is presented, and goes 'til the end and I click "Ok";
8) Steps 3-7 are presented again, twice, for my 2 extras DB's configured with Akeeba Backup (the only difference is the correct name on step 4);
9) The page "Site Setup" is presented, I just uncheck "Enable FTP Layer" and click "Next";
10) The confirmation page is presented and I click on "remove the installation directory" link;
11) And my site is fully working in my localhost.

The problem will be depicted now.

If I try to do the steps above with a file that uses ABI 3.5.1 or 3.5.0, there are problems with some points numbered above:

3) No "Warning Dialog" is shown in any of the three DB's;
4) The first DB is not the site's main anymore, it shows me first the two extras DB's and the main is the last one to be shown;
5) The "Database Type" is not filled with "Mysqli" anymore, I have to change it from "Mysql" to "Mysqli" manually;

The last DB to be presented is the Site's Main Database. I fill out the form, click Next, the progress bar shows up, I click "Ok" when the progress bar is full, and the system goes, again, to the same "Site's Main Database" page. And if I fill out the form again, it does it again and again... never going to the step 9.

One last information: If I try to restore a backup file that uses ABI 3.4.3, I have succes. The only problem is the absence of the Warning Dialog (step 3), but I can finish the restoration with success.

I hope I have presented all the information necessary.

Kind regards,
Thyago

nicholas
Akeeba Staff
Manager
I believe this is related to a known issue in ABI. Please download and install the latest dev release over your existing installation, retry backing up and test the new backup. Does it work now?

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!

user51436
Hello Nicholas,

I've installed the svn1550 version of Akeeba Backup Pro and now it's a little bit better:

1) I am still not receiving the "Warning Dialog";
2) Mysql is still the option automatically checked;
3) The Site's main Database is still the last one to be presented;
4) Now it's not stucked in the third DB anymore. I can reach "Site's Main Database" page, but the "Super Administrator Settings" is blank, I have to fill it out manually;
5) My website uses portuguese language, and we have some signs in some letters (like á, é, í, à, ...). Looks like my extras DB's are not being restored with the correct characters. All text with these accents are trunked in the letter marked. This was never a problem with Akeeba Backup;

Kind regards,
Thyago

nicholas
Akeeba Staff
Manager
Hi,

1. It is only shown when restoring to a different domain/subdomain.
2. I know. I haven't touched that yet.
3. That's by design. Making it the first one made the code much more complex.
4. This means that ABI can't read your configuration.php. Most likely your original site either had no configuration.php in its root directory or that file merely included an off-site PHP file where the configuration is stored. This scenarios are not supported and I've explained many times why they don't add anything at all to security.
5. Cool thing, I am Greek, we use a completely different character set and I regularly test my software with Greek content! Akeeba Backup does support international characters. In fact, it is charset neutral, i.e. it doesn't care about the character set of your data. However you have to make sure that both the source and the target databases use the same collation. So just check your database collation and change it to utf8_general_ci, or use the Force UTF-8 option in ABI, as per our documentation :)

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!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!