Atomix

What steps have you taken to try to troubleshoot this so far?
https://docs.wordfence.com/en/Troubleshooting_and_Common_Errors#Scanning_and_Scan_Results

What server are you using? IIS? Apache? Nginx? Litespeed?
Which version of PHP?

For us, to ensure scans always complete we’ve had to add a few lines to our .htaccess file (specific to Litespeed Web Server), and also change the maximum memory limit and maximum time per step in the Options page. Since then all scans have been successful.

A couple of things to check:

• Are you running Wordfence Premium? If not, the firewall rules may be out of date (unless you’re definitely running the latest Wordfence plugin).
• Check the Firewall page and scroll to the end of the list of rules. Does it include the latest 4.7.X rules (auth-bypass)? If not, Wordfence doesn’t have the information it needs to protect your site from these attacks.
• Also, is the Firewall definitely active? (Does it say “Protecting” or is it still in “Learning Mode”?). We had an issue where the firewall reverted to Learning Mode after the wp-content/wflogs/ directory was accidentally deleted during a deployment.
• Which version of WordPress are you running? Was it below 4.7.2 at the time of the attack?
• Could it be one of your plugins? Have you tried searching for them on wpvulndb.com to see if any have known vulnerabilities?

• This reply was modified 8 years, 1 month ago by Atomix.

I have made several critical fixes to the plugin and submitted a Pull Request:
https://github.com/fatzebra/FatZebra-WooCommerce/pull/4

We had this too, try going to the W3TC (“Performance”) admin menu, there’s some new settings available (a message will appear at the top of the page). Once you save the settings again it will add the missing data and the notices should disappear.

Did you go to Tools=>Beta Testing and switch to “Bleeding Edge Nightlies”? As soon as you do that it should appear in the update screen, I was able to upgrade from 3.8.1 to 3.9b2 without any trouble.

This is actually controlled by the WordPress core, inside the get_the_title() function.

Try this hook in your theme functions file:

/**
 * Tribe Events: Replace 'Private: ' title prefix from events
 */
function tribe_events_remove_post_status($title, $id) {

  $cpt = get_post_type();
  if($cpt == 'tribe_events') {
    $title = str_ireplace('Private:', 'Internal Only:', $title);
  }
  return $title;
}
add_filter('the_title', 'tribe_events_remove_post_status', 10, 2);

Confirmed broken in 3.6.1 as well, had to downgrade.

Bump! – Can anyone help!?

Thanks for the response,

all fixed!