lordmatt

Awesome thanks.

Had to uninstall as this update crached my site.

I’ve noticed that _ajax_nonce has no value. I suspect this is not correct.

No, its me. I was in settings. The FAQ meant under dashboard.

Update: It looks like this is a content negotiation vs cache problem. I have requested changes from my host and in the meantime have added .htaccess directives that I hope will set the cache time for JSON content to 0.

I too wish to do this

Yes, thank you. That exactly answers my question.

Yes, please.

Found the problem. It was not the plugin at all. My hosts were too aggressively protecting accounts against DDoS.

Thanks for the reassurance. I wonder why Mastodon instances are like that?

After some digging, I found that in Webmention\Handler\WP::parse_site_json() it assumes the JSON was all good and so has no error checking. Another plugin was corrupting the JSON and so it ran into trouble when json_decode( $response->get_body(), true ) returned null rather than the expected array.

I’ve solved the problem for now.

I fear it may be

I’m running Version 3.1.2 (my plugins are set to auto update). As far as I know, nothing interacts with blocked list but I can take a closer look. It was working last time I interacted with it and I could not find anything obviously wrong with the code.

I have noticed that there is a new row added to wp_sitemeta with a meta_key of “banhammer_options” (no quotes) every time I try to save settings. I was also able to restore the ban list by editing the database directly. The list empties every time a save options is attempted.

Redirect returns to default on each save.

• This reply was modified 2 years, 2 months ago by lordmatt.

Update: I checked the ticket I have open with my host. They are going to check the logs as it should work.

I’m also wondering if WordPress’s REST API could be getting in the way? Although honestly I am still just guessing.