Support » Plugin: Wordfence Security - Firewall & Malware Scan » Why are WordFence’s database fieldnames miXeDCase (ie non-default)

  • A few days ago the question was asked in a different area – after deactivating and deleting WordFence, WordFence database fieldnames still are in the database. Someone graciously answered promptly with the solution. I have not been successful in finding the choice to delete the database as suggested, most likely because I’m a bit too new to all of this. (help for this?)

    I too have the same problem, but I really do NOT want to delete WordFence and want to get to using the paid versions. The reason I (and others maybe) are deleting WordFence is because the 20+ mixed case fieldnames (all lowercase is the default) These are reported as an error by my backup plugin and other plugins.

    When asked, the backup plugin developer responded the it was a very uncommon practice not to follow default conventions. They offered a link reference to PHP site with a possible solution (ie hack?). I think this would be unwise of me to try as a non-programmer, not understanding the correct tools/process of making a patch.

    It seems WordFence could easily use the default method (all lowercase-default) in naming their fieldnames. (not as “pretty”, but “pretty” is not important in this case).

    I really do NOT want to delete WordFence, especially in view of their recent updates, but I have time and money invested in my backup solution and other plugins that follows default PHP conventions and that I am very happy with.

    There doesn’t seem a way to ask WordFence directly as pre-sales, unpaid user. Of course I’m not going to purchase WordFence just to be able to ask them the question. Must I move forward without WordFence? (Not that I want to) Can you suggest an alternate plugin – free or paid??

  • The topic ‘Why are WordFence’s database fieldnames miXeDCase (ie non-default)’ is closed to new replies.