Hi @jess888,
The cache area of the plugin gets re-written when things change, so it’s possible that it has updated itself since. These files are effectively compiled versions of the .twig files, and if the twig files change, then the content of these files will change as well. This avoids the twig files being processed every time (which would severely slow down the calendar). So you do not have to be concerned 🙂
Thanks,
Ben
Thank you so much, Ben. I figured there must be some kind of explanation.
I appreciate it!
Another potential explanation given by WordFence:
“After discussing with my colleagues it appears that this issue can occur when a empty file is created by the plugin upon install and populated with various information generated based on plugin settings.
It should be safe to ignore that file being modified — we can’t say it’s permanently safe, as it could still be modified maliciously, but it is also expected to be modified in the plugin’s normal operation.
Since it won’t match what’s in the repository, it will still be scanned for malware as long as they don’t add it to the excluded files list. (Using the “Ignore” links in the scan results should be fine.)
I’d also suggest you mentioned this issue to the plugin author so they’re aware that including a 0-byte file when releasing their plugin can interfere with Wordfence.”
