Are you running the latest versions of WordPress and Wordfence? I know this has happened before with localized versions, and if that is the only difference, it is safe. If it is still happening when Wordfence is up to date, I can notify the dev team.
Hi,
The basic answer is yes, I am running with WP version 4.3, and with the most recently published version of Wordfence (Free).
The upgrade to WP 4.3 was several days ago, and with Wordfence, from memory, although I can’t remember exactly when, I think it was similarly recently updated. I only use about 10 plugins, and all are up-to-date.
Thanks for your interest,
Alan
Me again …. I perhaps should mention that my webhost moved the site onto a different server recently, and because they forgot to delete the site from the old server, I had a strange situation with the latest published article not appearing on the version of the site that had been moved to the new server. That has now been rectified, and the old site on the first server removed. Everything is back to normal now, and the ‘missing’ article, together with all its images is back and being displayed correctly.
It may have been possible that whatever confusion has occurred, may mean that the updates to WP and Wordfence took place somewhere in between the server transfer, and the alleged Core Modification was only picked up by Wordfence when the site was correctly restored …. maybe. Do you think this is a possibility?
Regards,
Alan
Yes, it is possible that the move triggered the issue to come up — from past reports, it looks like it happens most on hosts where WordPress can be installed automatically, so they may have placed your site on top of a default installation. I did more searching and found that we do have an open issue for this on the current version, so it should be fixed in the future. You can safely click the link to ignore this file, for now.
-Matt R
FB518
Very many thanks Matt, I very much appreciate your quick responses.
Regards,
Alan
No problem — I’m just marking this resolved for tracking of issues awaiting responses, but you can expect the fix in a future release. Thanks!