Viewing 5 replies - 1 through 5 (of 5 total)
  • Actually the problem was first discussed with the WordFence team 2 years, 7 months ago.

    https://www.ads-software.com/support/topic/duplicate-tables/ .

    They created a reference number for this issue. It is FB1078 .

    It is a an error in design. It is bad practice to use mixed case database table names.

    Hi @mik84
    This issue appears to happen only on Windows servers (which are not officially supported) or while developing on Windows or MacOS machines then trying to migrate to a linux server, and for the latter you can remove the Wordfence tables on the development site before copying the live site to it, or before copying the development site back to the live site, you can do that using “Delete Wordfence tables and data on deactivation” option, or you can do it manually using any of the database management tools (phpMyAdmin for example). Please let me know if you can reproduce this issue by another way.

    The case “FB1078” is still opened seeking for possibilities to improve this behavior, there are many other factors need to be considered before proceeding with changing the database table names, that’s why I can not tell if or when “FB1078” may be implemented.

    Thanks.

    Thread Starter mik84

    (@mik84)

    I just asked my hosting provider, and ever single bit is running on a fully Linux Centos server. It has never seen Windows. Not even remotely.

    And I downloaded the plugin straight to my WordPress, through WordPress’s own plugin installer.

    So no migration, no Windows.

    If you are working totally on linux servers, then you shouldn’t worry about this case, as reported in Duplicator plugin warning:
    “For table name case sensitivity issues either rename the table with lower case characters OR be prepared to work with the lower_case_table_names system variable setting.”
    But you won’t need to deal with “lower_case_table_names” variable as it’s set to 0 by default on linux and you aren’t using Windows or macOS for development or migration purposes, so you can safely check “Yes. Continue with the build process!” and build your package using Duplicator plugin.

    Thanks.

    Hello!

    I hope we were successful in helping you resolve your issue with Wordfence! Since we have not heard back from you in the past 2 weeks I will now be marking this support thread as resolved. However, if we still haven’t resolved your issue please reach out to us as we would be more than happy to further assist you!

    Thanks and have a great day!
    Chloe

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Bad mySQL table name! Hasn’t been fixed in 11 months’ is closed to new replies.