Sonja London

It definitely is not resolved. I first discovered this problem 2 years, 7 months ago.
duplicate tables

If you want to try to force a workaround try setting the MySQL system variable lower_case_table_names . This is not allowed by many hosts though.

Alternatively you can delete wordfence before moving a system and then reinstall after.

But the 2 best solutions are

1. Get WF to fix this design error
2. Or find another security plugin

Except for this, I like WordFence but after 2 years, 7 months, I am losing patience. I will not be recommending WF to any of our teams clients until this design error is fixed.

Thanks for responding.

They were added by accident either through the user edit screen &/or a batch import that was not well formed. Occasionally they are added intentionally as a way to disable a user’s access.

But my question is about how to list them, not how they got there.

THanks. Not sure how I missed that.

This is also happening in the english version. I do not think it has anything to do with the language.

See this support post https://www.ads-software.com/support/topic/no-file-difference-warning-if-repository-readme-is-updated

I agree. These warnings do not appear to be valid security issues. Investigating them or even having to look at them is a big waste of our time.

Please do something about these false warnings.

Very glad to hear that it is in the queue.

We have been big fans of yours until we discovered this and honestly had begun looking at the competition.

Any idea how soon we may see it?

I know a number of people that have been hit with duplicate tables. Some members of our team develop on windows, some macs.

We have also discovered incoming clients who had duplicate table and did not know it. I suspect there are many people who do not know that they have duplicates. Unless one looks at the database or runs a newer version of Duplicator, it would not be obvious.

Also, for the record, it can be either the OS and/or the “lower_case_table_names” setting. Some hosts set this and/or do not give access to this and other database settings on more “economical” hosting plans.

Also might be a good idea to suggest workarounds until a fix is out.

For now, we are telling our team to just delete WordFence before migration and reinstall after.

This is NOT “an error within the Duplicator plugin”.

This is a WARNING from Duplicator of a dangerous practice by WordFence that MAY cause trouble if moving between systems that have different settings or file systems. It has caused duplicate tables many times.

https://www.ads-software.com/support/topic/double-wordfence-tables-and-duplicator?replies=5

It is always best practice to create table names in lower case.

Duplicator is 100% right to warn people of things that may cause trouble during a deployment or migration. Kudos to Duplicator for the warning.

FOrtunately WF people are considering correcting this problem.

WordFence team is wrong and it has been pointed out to them some time ago. Mixed case table names are a bad practice:

https://www.ads-software.com/support/topic/duplicate-tables?replies=9

https://www.ads-software.com/support/topic/double-wordfence-tables-and-duplicator?replies=5

https://www.ads-software.com/support/topic/case-sensitive-mysql-table-names-broken-migrations?replies=4

This is a warning from Duplicator of a condition that MIGHT cause problems IF you move from a system allows mixed case table names to one that uses lower case and back as is common during development or migrations. It is even recommended in the MySQL manual that table names should be in lowercase.

WordFence is considering changing it. Until then consider using lower_case_table_names=1 in your mysql configuration file to force lower case.

Please DO NOT remove these roles.

@jason – Do we have an ETA on TLD updates? We are very interested in this, as we love some of the new TLDs.

We have same problem.

It shows a check mark “?”

We are not seeing the role dropdown using TwentyFifteen and most recent version of BackWPup even.

We are also having 100% failure rate with BackWPup to SugarSync on many sites. We have seen these failures on BackWPup 3.1.2 (with sugarsync patch to curl), 3.2.0 and 3.2.1. They each have one of the following messages:

ERROR: SugarSync API: cUrl Error: SSL read: Error:00000000:lib(0):func(0):reason(0), errno 104

ERROR: SugarSync API: cUrl Error: select/poll returned error

ERROR: SugarSync API: Http Error: 503

Is there any chance WordFence will get rid of the troublesome camelCase names?

We would like to know how this can be done. We found requests for this feature from years past. Has it been implemented?

If not, is there a workaround?