Issues since upgrading to latest version

Hello,
Regarding the first issue, while being on the Blocking page and after trying to block any IP manually, please check the browser console looking for any JS error you might have.

For the second one, could you please check wp-config.php file and let me know the lines you added their for the network setup?

Also, go to (Wordfence > Tools => Diagnostics) and click on “Send Report by Email” button at the top of the page, you can send the report to “alaa [at] wordfence [dot] com”, make sure to include your forum username, I will take a look at this report and let you know my findings.

Thanks.

Hi:

No JS errors in console when trying to manually add an IP.

Can you be more specific as to which lines from wp-config you would like to know about. Not sure what you mean exactly by “the network setup”.

I sent you the report.

Thanks.

@wfalaa

Do you have any further insight? I am using Multisite, btw.

Hi,
I mean lines like those ones when you first configured the network.

After updating to the recent plugin version (7.0.4) are you still having the Blocking issue? are you sure you entered a reason for the manual IP block, the button should get highlighted after that (as it’s grayed out in first place).

Thanks.

Hi @wfalaa:

Yes, wp_allow_multisite is set to true. It is a multisite network.

The 7.0.4 update has not resolved this issue.

There are still MySQL errors that the table ‘wp_0_wfBlocks7’ is missing.

Yes, I am entering a reason for the block. As you know, the reason is a mandatory field. After clicking ‘Block this IP address’ the ‘Wordfence is working’ notice comes up, then goes away, but the IP block list is still empty.

After this line: define( 'WP_ALLOW_MULTISITE', true ); there should be other lines as well, like:

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
define('DOMAIN_CURRENT_SITE', 'domain');
define('PATH_CURRENT_SITE', '/directory/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

Could you please share these lines as well? also, are you sure the same error happens (the error appears again in the error log recently) with a fresh database tables?

Thanks.

Hello,

I’m experiencing exactly the same problem.
I’m also working on multisite configuration.
Is it a bug or a configuration problem?

Best regards,

Neorobot

Hi @wfalaa,

have:

define( 'WP_ALLOW_MULTISITE', true );
define('SUBDOMAIN_INSTALL', false);
define('DOMAIN_CURRENT_SITE', '<my domain>');
define('PATH_CURRENT_SITE', '/wordpress/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

the use of:

define('MULTISITE', true);

causes HTTP 500 for me.

If it matters, this network has existed since WordPress-MU. The v6.x series of Wordfence worked fine.

Thanks.

• This reply was modified 7 years, 1 month ago by spiffywiffy.

Hi @spiffywiffy
On certain old multisite installations such as yours, where both:
define( 'WP_ALLOW_MULTISITE', true );
and:
define('MULTISITE', true);
can’t be defined together, the plugin might not be able to fetch the correct database table prefix, this issue has been logged to our dev team but unfortunately, I don’t have an ETA for the update that could address this issue.

Thanks.

Hi @wfalaa:

Thanks – at least its on the radar.

• This reply was modified 7 years, 1 month ago by spiffywiffy.

Hi @spiffywiffy,

We are looking into all types of setups for multisite before implementing a solution as we want to make sure it is compatible with all setups.

Would you be interested in testing the fix in your environment before we release it? If so please let me know by sending an email to yann[at]wordfence[dot]com.

We would be very grateful if you could help us!

7.1.1 resolved this.