wfBlock?

I’m a big fan! Please keep up the great work here.

I’m reviewing Grey Rock Block Synchroniser for Wordfence and Cloudflare against Wordfence 9.0.0 and noticed a couple of compatibility concerns that may affect synchronization.

It looks like Grey Rock checks for active Wordfence blocks using:

wfBlock::getBlocks()

In the Wordfence 9.0.0 files I’m looking at, wfBlock::getBlocks() does not appear to exist. The available block methods seem to include wfBlock::ipBlocks(true) and wfBlock::allBlocks(...). As a result, Grey Rock may skip current/active Wordfence IP blocks and only rely on historical WAF events.

I also noticed the historical reader checks for the table as:

$wpdb->base_prefix . 'wfhits'

Wordfence 9.0.0 defines this table as wfHits, with casing handled internally through Wordfence’s own table helpers. That may work on lowercase-table installs, but it could fail on case-sensitive MySQL/MariaDB setups where the table exists as wp_wfHits.

So the short version is:

• Wordfence 9.0.0 does not appear to expose wfBlock::getBlocks().
• wfBlock::ipBlocks(true) may be the more current active-block source.
• Historical WAF sync still appears valid in concept because Wordfence records blocked:waf events.
• The wfHits table casing may need to be resolved through Wordfence’s table helper or checked with both casing variants.