shey456

Had to remove the Akismet plugin and it looks alright now.

Hi,

I checked, and yes, it is on.

Thank you.

Thanks for your reply.
Yes, that option was on, and I turned it off.

But to mention, I had the same option on in previous WordPress installations and at then the site in the sub-directory didn’t alarm by Wordfence. It only happened after updating WordPress to 4.3.

I don’t know how this issue relate to this new one.

When I went to the Wordfence scan page, the previous scan was stuck. Displayed,

“Scan Engine Error: Wordfence could not start a scan because the cron key does not match the saved key.”

But kill and re-scan completed with no issues.

Thank you.

Thank you for your response.

Yes, There are two WordPress installs. One for the main site and the other for an add on domain.

I updated to WordPress 4.3 to the add on domain first, and later on that day Wordfence detected this issue on the updated add on domain includes folder. But next day I updated WordPress 4.3 to the main site too. Still Wordfence detects this issue in the same folder on the add on domain.

Is there anything not right? Any steps I should follow?

Thank you.

P.S – The code is actually in this file.

/wp-admin/includes/class-pclzip.php

I cleaned the cache of the browser. It was the issue.

Hi,

Thank you for posting it. I’m going to try them. Hopefully I will be able to fix it. Thanks again. ??

Hi gVectors,

It worked. I’m disappointed I didn’t see that. I even searched for days online though. Sorry for having to bother you.

Thank you.

Is it impossible?
Maybe then how to remove the entire line “You must be logged in to post a comment.”?

It worked. Thank you.