Mark Maunder
Forum Replies Created
-
Yes, you should disable Falcon for now if you have two versions of your site. We’re going to add UA detection in probably the next version that will help you serve two versions of your site and keep caching enabled.
Regards,
Mark.
Unfortunately we don’t control how much memory your hosting provider makes available for your site. Looks like they’ve given you about 64 megs of memory. This isn’t much for a large wordpress site, so please ask them for an upgrade.
Regards,
Mark.
If you could post a screenshot of the gibberish, that would help.
Also, above I asked for the URL of the social sharing plugin that you’re using (or theme or website or utility), not your own site URLs.
Thanks.
Hi,
Would you mind describing what you mean by dissipate? In english this usually means dissolve or fly-apart-into-may-pieces much like the agents that were attacked by the Lawn Mower Man.
Thanks.
Hi,
The second issue is that your .htaccess permissions are set so that your web server doesn’t have permissions to modify it. You need to change this is you want wordfence to update it.
The first issue we’re aware of – where you have a subdir site but a root .htaccess and we will fix this in the next release.
Regards,
Mark.
Hi,
This is probably not Wordfence. Please check your error logs to find out why your site is unavailable.
Regards,
Mark.
@lizardwebs: Sounds like you have some other issue. Here’s the actual code change that completely disables the feature:
Here’s the full list of changes. Scroll past the list of files to see the actual diff:
Even if you don’t understand PHP, it’s pretty obvious what we’ve done here. We’ve removed the code that:
1. Checks to see if the user has chosen to disable XML-RPC.
2. Plugs into the xmlrpc_enabled filter to actually disable XML-RPC.
With that code no longer present, there’s no way that we can disable XML-RPC. So you probably have some other issue with your site.
Regards,
Mark.
Hi Guys,
We need to gather more feedback and examine what tangible security benefit it offers and if there are other alternatives that may provide larger security benefits. Thanks for your input.
Regards,
Mark.
Forum: Plugins
In reply to: [WooCommerce] Plugin: WooCommerce update not workingHi, just wanted to weigh in here since you’re referring to an issue we just fixed. We got a lot of negative feedback re the disable XML-RPC feature we released in Wordfence a couple of days ago so we just put out a release that gets rid of the feature. So if you do have any issues related to XML-RPC being disabled because of Wordfence, just upgrade to Wordfence 5.0.3 and it will be resolved.
Regards,
Mark Maunder – Wordfence creator.
Hi all,
We’ve yanked the feature. I’ve just released Wordfence 5.0.3 and the only difference is that we’ve completely removed the ability to disable XML-RPC.
I’ve also put up a blog entry here explaining what we’re doing to prevent this from happening in future:
In short: We screwed up. We’re sorry. Clearly our release process and quality assurance isn’t keeping up with the growth in Wordfence’s user base and the sites that depend on us. So we need to fix this internally and I can assure you we’re going to improve the process.
Thanks to everyone including Andrew Nacin and all posters above who weighed in on this.
Regards,
Mark Maunder.
Hi Duke,
Please give me the URL of the plugin you’re referring to so that we can reproduce and fix this for you.
Regards,
Mark.
Awesome, thanks for the confirmation.
Regards,
Mark.
OK thanks Cemal and Adrian, this is clearly something we need to fix for this particular config so we’ll get on it and it’ll be in the next version.
Regards,
Mark.
Seeing all of the issues people are having with the new WordFence that have yet to receive a response….
My websites have been doing fine without caching, a choice I made after much research. As a paying customer, I dislike caching forced on me. It has taken me much time and effort to get my sites working.
OK stop right there. I haven’t even read the rest of your post. Firstly, we’ve been working very hard to reply to you and other customers in a timely fashion and have been doing a pretty darn good job.
Secondly, caching wasn’t forced on you. The feature is disabled by default and it’s perfectly OK to leave it disabled so please do so.
Regards,
Mark.