Poor coding

The entire base of this plugin is poorly planned out. It contains a series of hacks that break basic coding standards in order to achieve it’s goal. It also targets other plugins and breaks them as I can see many other reviewers have reported. Don’t risk crashing your site.

As expected, a retaliatory rating from the developer of Plugin Organizer, in response to our review of Plugin Organizer, after he added malicious code to his plugin that intentionally completely disables WP-SpamShield on sites.

The irony of this, is that he completely ignores the major issues caused by his plugin and code, and yet he claims that WP-SpamShield will “crash” your site. Evidence clearly contradicts this false claim.

It also targets other plugins and breaks them as I can see many other reviewers have reported.

??? This is blatantly false. WP-SpamShield is one of the most compatible plugins out there.

@foomagoo,
As previously mentioned, you ignore the damage done by your own plugin, you provide no option for other developers to opt-out or to work together, and then you complain when other developers add code to protect their own plugins.

@ Anyone else reading this:
I apologize to all of you that you have see this side of plugin development. It’s quite unpleasant. This review can safely be ignored. Unfortunately plugin developers sometimes take an adversarial approach instead of a collaborative one. We do our best to work with other developers, but sometimes they decide to be unprofessional.

@foomagoo,

As usual, more false statements.

As expected, a response blaming me for blocking the malicious code you added to your plugin targeting mine.

Well, you clearly ignore the true timeline of events.

As you’ve done to numerous others. Anyone who wants to see evidence of it just needs to browse your support threads and bad reviews.

??? Again, what??? Every word we’ve ever posted online is true and can be verified by any third party.