mrtopf

I had the same problem and did some digging (actually still have, need to wait for somebody to update the firewall).

Some findings: “Rules list” can be found at “All options -> Advanced Firewall options”. For me it said that it cannot update the rules list and I need to make sure I can access the wordfence servers (unfortunately without telling me where they are).

So if you have a firewall which blocks outgoing traffic, this might be a problem.

I did some more digging and the server which it uses to get the rules file from can be found in vendor/wordfence/wf-waf/src/init.php

and in my case it’s

https://noc4.wordfence.com/v1.8/

So this must be reachable from your server. I will find out soon I hope.

Hope this helps.

Thanks for the reply.

For now I solved it by telling the FS component, that we are always in “direct” mode by adding this to my functions.php:

function my_filesystem_method($method, $args, $context, $allow_relaxed_file_ownership) {
    return "direct";
}

add_filter( 'filesystem_method', 'my_filesystem_method', 10, 4);

This means though that the FTP prompt will never show up anymore like for plugin updates (I guess it will just fail). For me that’s no problem though as I update my plugins via wp-cli.

I still wonder though how other plugins do it, like cache plugins etc. Those seem to work.

(hypergeneric: It does actually create the file in uploads/ but the FS system does test the writability in general, like on the WP core files.)

I should maybe add that I have my WordPress secured in that the WWW user can only write in uploads which might be the issue here. The question then might be if another method of writing a temp file can be used (e.g. one using real temporary files).

Well, I am not sure I can give you the full embed but I am pretty sure it’s the above mentioned embed.js which is the problem. I will try to make a test case though and report back.

(https://downloads.mailchimp.com/js/signup-forms/popup/embed.js as <script>)

I have the same problem but don’t really want to disable the popup (I actually just added it).

What I did was creating an exit intent popup in mailchimp and adding it to the site via the provided code which loads the mentioned embed.js

So if you can have a look at it it would be very much appreciated. Something seems to conflict here.

Thanks!

Christian

Based on the remark by danielshields I only found out that post.php is trying to also process WP_Error instances instead of WP_Term instances. So I am not sure if those were previously filtered out. WP_Error instances of course have no term_id and thus it breaks.

I have no idea though how to fix that as I am not really too much into the taxonomy part of wordpress. I guess one could filter out the WP_Error instances in cpt-onomies (they are created by a filter I think) but one would need to find the right call to it I guess.