Support

Akeeba Backup for WordPress

#22806 Cannot Restore Site with 1.3.3

Posted in ‘Akeeba Backup for WordPress’
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

WordPress version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Wednesday, 17 June 2015 10:47 CDT

LeClerc
Hi Guys,

I have the same problem as here: #22654 – Moving to new server "Force UTF-8" problem, but with WordPress, not Joomla.

Since upgrading (from 1.3.1) to 1.3.3, I cannot do a fresh recovery of a website using kickstart pro and Angie.

I get to the point at which it requires a database recovery, however I am unable to recover the database with the error: SQL=CREATE DATABASE ...... CHARACTER SET 'utf8mb4' (screenshot attached).

The database is most definitely already created (and is empty) and the user definitely has the requisite rights to be able to write to the database, indeed using a recovery file created with 1.3.1 works perfectly with exactly the same credentials with the same database.

I did notice in the changelog for 1.3.2 (which I skipped): # [HIGH] ANGIE: Restoration may fail or corrupt text on some servers due to UTF8MB4 support - and an extra checkbox on the database restoration page (which makes no difference whether it's checked or not!). I wonder if this could have something to do with it?

Kindest regards,
Alan.

nicholas
Akeeba Staff
Manager
In the database restoration page there's a checkbox called "Allow UTF8MB4 auto-detection". It is checked by default. Uncheck it and then click on Next. Did that help?

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!

LeClerc
Hi Nicholas,

Thanks for your reply.

I have tries that (along with "enforce utf8 etc) - it changes the error message, however still does not perform the restore of the database.

Attached different screenshot.

Regards
Alan.

nicholas
Akeeba Staff
Manager
OK, then it is as I suspected: you are either entering the wrong database information or you're using the wrong database driver. Try switching between the MySQL and MySQLi drivers and triple check your database connection information.

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!

LeClerc
Hi Nicholas,

Ah, that's rather embarrassing! I hadn't changed the MySQL driver option as the MySQLi had always worked (even with MariaDB).

I can confirm that it works fine with the MySQL (PDO) driver - everything restores just fine.

Regards,
Alan.

nicholas
Akeeba Staff
Manager
You're welcome, Alan :)

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!