Support

Akeeba Backup for WordPress

#25653 – 1050 Application Error

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.
Tuesday, 19 July 2016 06:02 CDT
trevorwood
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?

Custom Fields

WordPress version (in x.y.z format) 4.5.3
PHP version (in x.y.z format) 5.6.9
Akeeba Backup version (x.y.z format) 1.9.0.b2
 
Tuesday, 19 July 2016 07:33 CDT
tampe125
Hello Trevor,

what you experienced is the exact reason why you always should use lowercase prefix: if you are under a case-sensitive server and you move to a case-insensitive one, things will break ;)
This is always true, not only using Akeeba Backup, but even using a manual backup.

For your information, we just added a check in Akeeba Backup and it will warn you if you have a multicase table prefix.

Just to be sure, did you resolved your issue or you need further assistance?


Davide Tampellini

Developer and Support Staff



Italian: native

English: good



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Tuesday, 19 July 2016 07:58 CDT
trevorwood
Unfortunately the Plesk WordPress installer can choose from uppercase as well as lowercase letters and (due to a bug) won't let anyone select their own prefix letters.

I'm using a WordPress plugin to change all the database prefixes which'll fix the problem. I've also logged this as a problem with Plesk
 
Tuesday, 19 July 2016 10:08 CDT
tampe125
Thank you very much for the report, I hope Plesk will fix their issue promptly.


Davide Tampellini

Developer and Support Staff



Italian: native

English: good



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Thursday, 18 August 2016 17:20 CDT
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!