redsand

Edit: unlike the widgets plugin, Scott asked us to close this. I won’t betray his wishes by editing his code or taking it over. That would be disrespectful.

Mika, that’s a blatant lie. I am going to ask again that you not lie about us. I never asked you to close WP-SpamShield. We had already received noticed that Otto had booted it. What I did say, www.ads-software.com was no longer trustworthy, and that we wanted you to close all of our other plugins.

If you and Otto continue to lie about us publicly, I will be forced to start publishing the email thread so that you will stop lying about us.

We’ve removed code … twice? Once was for a backdoor, and the other I Remember was when someone posted private information by accident.

There was never a backdoor or private info in WP-SpamShield’s code.

@ipstenu,

Wow…just wow.

@ipstenu,

Mika, I have to publicly confront you on that statement. We did not break any rules, and you have not yet provided us an answer to exactly which rule we have broken. Please do not lie publicly about us.

— Scott

Hi Lap!

I can verify that’s 100% correct.

We’ll be happy to help if any refinements/improvements need to be made in the future to make compatibility even better. ??

I don’t care for being forced to rate an extension. When I find something to replace WP-SpamShield I will.

Hi @greggluhring,

I’m sorry that you felt you were forced to rate the plugin. That’s definitely not our intention at all. You’re definitely not forced to rate anything…I’m not sure how you got that impression but if something is not working we do want to know so we can fix it ASAP. When the reminder notice comes up to ask if you want to rate it (only 1 time, ever) all you need to do is click the link on the reminder notice and it will close. You’ll not see it again…ever.

If you want to edit your review, reduce the number of stars, etc, just click near the top of the review where it says “you can edit your review at any time.”

If something is not working properly, please let us know at the tech support URL and we’ll look into it right away.

— Scott

Hi @diegocanal and @jkirker,

The two plugins are not compatible and should not be used together. We have more info on our Known Issues and Plugin Conflicts page. If you have any questions or comments, feel free to contact our tech support and we’ll be happy to help.

— Scott

@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.

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,

That’s simply not accurate.

You started off unprofessional. You specifically targeted my plugin. I pointed out the bug you created by relying on my plugin never changing.

No, we did no such thing. You seem to be missing a huge point here: You created a plugin that causes massive interference with other plugins, with no way for other plugin devs to opt out.

As a result, other plugin developers are forced to create fixes to prevent your plugin from breaking their code and functionality. That is not targeting you…that is merely protecting their code, and more importantly: protecting their plugin users.

That’s the point you keep missing. Every single code edit we ever made, was a response to your code.

I’ve been doing this a long time and you aren’t the first developer I’ve dealt with who blames the bug they created with their poor coding skills on someone else.

Jeff, your attitude is simply unprofessional. The irony is that you’re blaming everyone else for the issues your plugin creates. Regarding the “poor coding skills” comment, I’ll simply ignore that as it is ridiculous. You don’t create one of the best WordPress anti-spam plugins, and build the reputation we have by “poor coding skills.”

@foomagoo,

You’re welcome to spin it any way you like, but that’s simply not true.

The whole purpose of Plugin Organizer is to interfere with other plugins, yet you do not like it when other plugin developers add code to protect teh integrity of their own code.

You do not sufficiently warn your plugin users that there is a high likelihood PO will break other plugin functionality.

Why would I add an opt out for any plugin? That would defeat the purpose of Plugin Organizer. If a user wants to run your plugin but doesn’t want it to load on a certain page then it’s their website. Let them do it. They are making an effort to disable your plugin and you are preventing it.

That’s really the crux of it: You don’t want to add an opt out, because you’re worried that people won’t use PO anymore. That’s the definition of not being willing to work with other plugin developers.

You updated Spamshield with more malicious code that called the unlink command and deleted the MU plugin file. Which makes Plugin Organizer not work.

First off, you shouldn’t even be installing an MU plugin. That’s suspicious to start off. Protecting the integrity of our code is not malicious.

And now you are playing the victim as if I was the one that started targeting your plugin.

We don’t “play” anything. It is a fact that you’re adding code to target the plugin. As of the other day, we were minding our own business.

So the only way Plugin Organizer can continue to run on a site with Spamshield installed is to disable it.

No, you could have simply whitelisted the plugin. If you know that your code is purposefully breaking another plugin, that’s at the very least irresponsible, and at the worst malicious.

@foomagoo,

That’s simply not accurate. We did not go and completely disable your plugin like you’re doing.

Correct order of events:

1. Your plugin starts by breaking other plugin functionality. To be clear,
   yours broke other plugins first.
2. We added code (a long time ago) to prevent it from breaking WP-SpamShield functionality. Other plugin devs have have to do the same thing, because Plugin Organizer breaks theirs too. If you had added an opt-out/opt-in/whitelist functionality for other plugin devs, this would not be necessary.
3. A couple days ago, a user brought conflict issues to your attention. We tried to discuss with you professionally, and let you know that you were welcome to contact us and discuss compatibility solutions. You made it clear that you preferred an adversarial approach.
4. Yesterday you added code that breaks WP-SpamShield again.
5. We updated WP-SpamShield with code to prevent WP-SpamShield functionality from being broken.
6. Instead of simply whitelisting the plugin, since you know that it’s code needs to not be interfered with, you released yet another update that specifically and malicious disables WP-SpamShield.

You did not need to choose an adversarial route. We’ve had good experiences working with other plugin devs.

Hi @matt94gt,

Our tech support team will be happy to answer your questions.

@foomagoo

You have a partial understanding.

You are preventing plugin organizer from disabling your plugin on any page.

Yes, I already explained that.

By doing that you incorrectly restructured the posted data.

No, that’s where you don’t understand.

Jeff, you’re just running in circles here. If you keep posting false info about WP-SpamShield, I will respond and correct you. But, this does not help anyone.

Again, if you want to discuss like a professional, and work out compatibility issues, you are welcome to contact us.

– Scott

@matt94gt,

We’re trying to. ??

@foomagoo

Sorry. But I was responding to your “personal attacks” in kind.

Jeff, that’s simply not true, but you can choose to see it however you like. We were minding our own business. We’re going to respond if someone posts incorrect information.

Quote all the code you like, but when you take it out of context, it’s meaningless. I’m sorry that you don’t understand the functionality, but I don’t have enough time to explain it to you here.

Like I said, if you want to act like a professional, contact us in private, and we’ll be happy to discuss.