Hi @andyward75,
Most likely, those plugins were improperly coded so when you deleted them they were not properly uninstalled. Meaning, you need to perform a manual cleanup of those plugins.
Follow this advice, clear your cache (all layers), then re-run Wordfence. You should be good to go.
If satisfied with the above, please close this topic as “Resolved.”
Cheers!
Hi @andyward75,
As Generosus says, my first suspicion would be that some traces of those plugins remain for Wordfence to be picking them up. Let us know if we need to look into it further from here.
Many thanks,
Peter.
Hi, I decided to write to Ninja after the first reply. Before I did, I decided to search the site for anything with “caldera” in it and I had two results:
./wp-content/plugins/litespeed-cache/thirdparty/caldera-forms.cls.php
./wp-content/plugins/ninja-forms/includes/Database/CalderaSubmissionDataSource.php
I wrote to Ninja, explaining that I had converted from Caldera and that I had Wordfence and that it (WF) was reporting issues with plugins and they replied:
This file is part of our plugin and actively in use: ./wp-content/plugins/ninja-forms/includes/Database/CalderaSubmissionDataSource.php
What this file does is access your previously existing Caldera Forms submissions for display on the submissions page. You should NOT delete that file as it is in current use (even if you don’t pull up old Caldera submissions.)
This file is part of some other plugin not associated with us, so I can’t speak to it with any familiarity:./wp-content/plugins/litespeed-cache/thirdparty/caldera-forms.cls.php.
Ninja Forms Reply
Since then, I have had a further scan result and the two critical errors have now disappeared DESPITE NO ACTION HAVING BEEN TAKEN. Perhaps you could suggest what might be happening here.
Many thanks
Hey @andyward75,
Thanks for that. Helpful. Glad your issue is solved.
Here’s what most-likely happened: (one or all of these events)
- Cache was cleared – automatically or manually. Yes, clearing cache (all layers) many times solves Wordfence findings.
- A conflicting plugin was deactivated, then deleted and/or reactivated. Yes, this too solves many issues.
If the issue comes back, perform a clean uninstall of those plugins (if they’re still around, ask the developers for detailed instructions).
If satisfied with the above, please close this topic as “Resolved.”
Cheers!
Well, I’m not sure that I would agree that the issue is solved. Maybe it has gone away, but solved?
Anyway, the issue is not now being reported so I guess the ticket can be closed.
