Some months ago I opened ticket #23622:
I have found the problem
The error message I was getting was 1050 Application Error
Table 'f3a7v2bw_ak_params' already exists SQL=CREATE TABLE `f3A7v2bW_ak_params` ( `tag` varchar(255) NOT NULL, `data` longtext, PRIMARY KEY (`tag`) ) DEFAULT CHARACTER SET utf8;
The problem is the table name. The WordPress site was originally created by Plesk on a Linux server. Plesk is a bit naughty and created random table prefixes using uppercase letters. This is not recommended by MySQL (they should all be lowercase)
When I moved the site to my Windows test server (using kickstart.php) the table names were lowercased
However, Akeeba Backup is still looking for them in the original case. When it can't find it, it tries to create it but Windows/MySQL comes back and says it already exists
I can try and fix this by changing the case of all the tables on the original site, but would it be possible to put a work around in somewhere
It's not possible to just change the case of $table_prefix in wp_config.php as this breaks the whole admin side of the site (I know, I've just tried it and get a "You do not have permission to access this site" message
Perhaps Akeeba Backup can check for lowercase table name if the error comes up?
I have found the problem
The error message I was getting was 1050 Application Error
Table 'f3a7v2bw_ak_params' already exists SQL=CREATE TABLE `f3A7v2bW_ak_params` ( `tag` varchar(255) NOT NULL, `data` longtext, PRIMARY KEY (`tag`) ) DEFAULT CHARACTER SET utf8;
The problem is the table name. The WordPress site was originally created by Plesk on a Linux server. Plesk is a bit naughty and created random table prefixes using uppercase letters. This is not recommended by MySQL (they should all be lowercase)
When I moved the site to my Windows test server (using kickstart.php) the table names were lowercased
However, Akeeba Backup is still looking for them in the original case. When it can't find it, it tries to create it but Windows/MySQL comes back and says it already exists
I can try and fix this by changing the case of all the tables on the original site, but would it be possible to put a work around in somewhere
It's not possible to just change the case of $table_prefix in wp_config.php as this breaks the whole admin side of the site (I know, I've just tried it and get a "You do not have permission to access this site" message
Perhaps Akeeba Backup can check for lowercase table name if the error comes up?
