lizardwebs

And yet another – on several sites…

@marcelo – Still looking at it – disabled all plugins, reinstalled WP, switched to default theme – still issues. Somehow, when all this is done, I’m going to end up feeling stupid for missing some small little thing I have no doubt when I find it… Going to take this offline from here though. This doesn’t seem to have anything to do with WordFence and I don’t want to waste their area chasing down rabbit holes LOL. thanks for the input all!

Thanks for the feedback @wordfence! I’ll look at it – I stay on top of updates and it may be some other plugin. It hit 14 of my sites though that I use this software on and it seemed like the logical direction to look after the 5.0.3 – will keep on hunting for the issue! Thanks – LOVE FALCON!

Thank Marcelo – the problem though is that I enabled the xmlrpc in a number of sites so I could use the remote posting software. And after the 5.0.3 update, my remote posting application cannot contact those sites. And I no longer have the option in WordFence of turning it on or off. It’s just flat out off. Verified it via test at https://xmlrpc.eritreo.it

Hey Guys – love the features – however, I think with this last change (5.0.3) something may have gone awry. Specificall with the XML-RPC rollback. I also use a remote posting solution, and had spotted that XML-RPC entry pretty quickly after upgrading so disabled it on a few sites (disabled the disabling of XML-RPC to be exact – thus leaving it enabled where I needed it). Just did the update to 5.0.3 and now my sites that had been working with the above settings now seem to be disabling the XML-RPC completely. No option to re-enable, disable, etc. Haven’t gone hunting through the plugin code for solutions yet, but… Any ideas? I have several sites that are now all reacting the same.

I was having the same issue. I did have domain mapping enabled and it was pointing from the IP to the domain name. Removed the domain mapping back to the IP for the default blog and it resolved the issue with no other apparent issues. It should resolve there anyway – not sure why or how I got that in there….