Mark Maunder

Firstly, thanks very much Otto for weighing in here.

For the folks that are complaining about this issue, you have the following setting in your wp-config.php file which should not be used in production sites:

define(‘WP_DEBUG’, true);

That is the only way that this error can possibly be generated and made visible to your customers.

I strongly recommend you disable debugging if you’re running a production website.

I’d appreciate it if some of the folks here can confirm that this setting IS in fact enabled in wp-config.php and also give me some insight as to why you would do this. Not looking to hen-peck our users, but I’d like to gain a deeper understanding of how you choose to configure your sites.

We changed the order in which the logging code is run as a performance enhancement in the newest version and it looks like is_404() is being called too early. So we’re working on a fix which will be released shortly.

Regards,

Mark.

Firstly, thanks Jan for being a volunteer moderator. Really appreciate you helping out on the forums.

Hi Chris, I’m the plugin creator. I’d really like to help solve any issue you have. It looks like you posted your original message 2 hours ago, so hopefully we’re getting back to you soon enough to help out.

To be clear, we’re not some group of hackers in a basement. Wordfence is owned by Feedjit Inc. of which I’m CEO. You’re welcome to reach out to me at mark @ wordfence dot com. If you’re running a business, I’d love to see how we can work together.

Wordfence the product is put through rigorous QA before we release it which is controlled by Kerry Boyte, my co-founder. She has built and run large QA teams at prestigious firms like the BBC and Symantec. In fact she built the BBC’s digital TV testing lab from the ground up. So you might say we know a thing or two about testing.

However it sounds like we missed a bug. But it also sounds like you’re running an older version of WordPress correct? Admittedly our test coverage on older versions is lacking because we consider it important for site security that all our customers run the newest version of WordPress. Presumably if you’re keeping Wordfence up-to-date you’re also upgrading WordPress itself.

Chris, I think you have probably wasted enough time on advocacy in this thread and it sounds like you have a business to run, so if you can post the error you received, we’ll give it our swift attention. As Jan mentioned if you’re a paying customer please visit http://support.wordfence.com/ where we’ll give you the priority support you’ve paid for.

Kind regards,

Mark Maunder
Wordfence Founder and Feedjit Inc CEO.

PS: Our terms of service including limitation of liability clause are available here. They’re fairly standard and you’ll find much common ground in the ToS of other SaaS providers and software companies.

http://www.wordfence.com/terms-of-use-and-privacy-policy/

Thanks for the comprehensive feedback.

If you do decide to enable Falcon again and you see these symptoms, it would be very helpful if you could share your .htaccess file with us before you restore the backed up version. I’d like to see how Falcon modified it and what else you have in there that may cause problems. That way we can build in compatibility for your specific scenario. You can email your htaccess to genbiz @wordfence.com if you do decide to try this in future and we’ll investigate.

Thanks.

Mark.

No. In fact if you try to enable it you’ll get a warning that you can’t enable falcon with any other caching plugin enabled.

You shouldn’t be using multiple caching plugins because they’ll probably slow you down.

Regards,

Mark.

Hi all,

Posting a belated update on this. Clearly we sorted out the Akismet issues some time ago. During the last week since this happened we’ve been working hard to upgrade our systems and that upgrade is now almost complete. The plugin scanning portion of our infrastructure has been upgraded to a brand new beefy distributed storage system with 8 additional CPU cores thrown in to speed up plugin hashing. That was the biggest task. Did you know that as of right this minute WordPress has 42054 plugins in the official repository comprising over 350 gigabytes of data?

We’re busy completing the migration of our theme and core mirrors to the new system and that will be done within 48 hours. However, this is not critical because we haven’t had any performance issues in those areas. There also won’t be any down-time as we complete this task.

So as of right now all systems are green and have been since we resolved the original issue just under a week ago.

Regards,

Mark.

Hi,

We fixed this issue a while ago. I’m not sure why you’re not being alerted to upgrade. Please upgrade to 4.0.3. It is a production version (not a beta).

Regards,

Mark.

I think we already chatted via our priority ticketing system. Let me know if that’s not the case. Marking this resolved.

Regards,

Mark.