Support » Plugin: WP Broken Link Status Checker » Does not work with Wordfence, and other security / firewall plugins

  • ironfish2

    (@ironfish2)


    The Broken Link Checker plugin (This is a very popular plugin that has been around for years) seems to be no longer supported and so I took the time to search for and evaluate other plugins, including this plugin – WP Broken Link Status Checker.

    I took the time to read about it, check the devs, install and activate it, set it up, and run it.

    Then like this user and issue:
    https://wordpress.org/support/topic/doesnt-scan/
    I have the same problem – it does not scan.
    And in this issue the dev of the plugin says:

    Just one question, do you have installed any firewall or security plugin?

    We have problems with Wordfence firewall module, and All In One WP Security & Firewall plugin and its Brute Force module.

    I am giving this plugin 2 stars because:

    • It does not work with Wordfence, which currently has Active Installs: 1+ million. So many users will be using Wordfence and so many users will have this issue with your plugin.
    • I wasted about one hour of my time to eval, download, learn, and run the plugin, determine it is not running, look up issues, find that it does not work with Wordfence, etc., I think the dev should clearly state this plugin does NOT work with Wordfence etc on the plugin home page.
    • I do not want other users to waste a similar amount of time, so I hope my giving this 2 stars will let other users know of this issue BEFORE they waste their time if they have Wordfence
    • Up until this review, the plugin had a perfect 5 out of 5 star rating which to me implies the plugin is exceptional in its quality, and should not have any problems.
    • I have used Wordfence for years and never have had any issue where any other plugin would not work with Wordfence – so I think this is not a common issue.
    • The dev stated that there are issues with Wordfence 3 months ago but the plugin has not been updated for 4 months, meaning the issue has not been addressed in at least 3 months..
    • This topic was modified 3 years ago by ironfish2.
    • This topic was modified 3 years ago by ironfish2.
    • This topic was modified 3 years ago by ironfish2.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author SeedPlugins

    (@seedplugins)

    A short message in the support forum would have been enough. I don’t like your tone of punishment, that way does not help. Anyway I will update the plugin description.

    ironfish2

    (@ironfish2)

    This way may not help you, but it will help people who may be considering the plugin.
    Any one of the 1 million users/sites of Wordfence, plus millions of other users/sites using other security plugins, will save time and frustration by knowing what I said above. Helping even a small percentage of millions of potential people IS helpful.

    My post above is not about you, for you or whether you like it. It is a review of the plugin.

    When you state in a support post that the plugin has issues with security plugins, then that is the way it is – I do not need support, so I did not use the support forum.

    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    Plugin Author SeedPlugins

    (@seedplugins)

    Ok, I got it, that way does not help me and help others,

    so the developer does not matter in all of this process, right?

    so it is necessary a angry post and bad review as a punishment focused about your lost hours, not about the plugin quality, right?

    then you does not need support, but you found the solution in the support forum, right?

    Sorry, this is crazy. If the plugin is bad, please enter a bad review, I can assume it. But a bad review because an outdated description. Oh yes, that is the way for a free plugin with free support to encourage the developer.

    And why two starts? Why not one star then?

    As I said, a short message would have been enough.

    There are about 50.000 plugins in WP.org repository, do you want to help me to test the compatibility with all of these plugins before it will cause more problems and waste of users time?

    Thanks,
    Pau

    ironfish2

    (@ironfish2)

    I will address each of your comments:

    so the developer does not matter in all of this process, right?

    I did not make any bad comments about you – I made a review of the plugin – you are personalizing the review. I did not say anything about you, positive or negative. You need to realize that a user leaving a critical review of your plugin is not an attack on you.

    so it is necessary a angry post and bad review as a punishment focused about your lost hours, not about the plugin quality, right?

    My post it is not angry – if it was, I was just say it was crap and leave it at that. However, I think that is very unfair. That is why I took quite a bit of time to explain in point form, why I am leaving a 2 star review. Saying it is a bad review and that it is punishment is very distorted. Again, just becuase I have left a critical review and you may feel bad about that, does not mean the review is angry or that you are being punished.

    then you does not need support, but you found the solution in the support forum, right?

    That is correct – you clearly state in a support post that the plugin has problems with security plugins such as Wordfence. And I made effort to point that out in my original post. That was the solution to my issue. My issue was that your plugin was not working. The solution/cause was to learn that the plugin has problems with Wordfence. I have an issue and a clear cause, already explained by you, so there is no need to post another support issue.

    Sorry, this is crazy. If the plugin is bad, please enter a bad review, I can assume it. But a bad review because an outdated description. .

    My review is factual. There is nothing un-true about it. To call it crazy is crazy. Calling the plugin “bad” is not something I did – it is something you are labelling the plugin and my review as.

    Oh yes, that is the way for a free plugin with free support to encourage the developer

    If you depend on reviews for motivation, and you are going to be de-motivated by non 5 star reviews, then you will quickly be so demotivated you will not continue, because there will always be critical reviews. Do you think the devs of the most popular plugins get discouraged if they do not recieve perfect reviews? Take a look at Yoast’s SEO plugin – he has FOUR-HUNDRED ONE-STAR REVIEWS – Do you think he attacks his users because he feels they are not encouraging him because they are leaving one-star reviews? Do you think he bases his encouragement on reviews?

    Take a look at the most popular plugins. They have millions of users and 100’s of 1 star reviews. For example, WP Super cache has 125 1-star reviews. The developers do not see a 1 star review as demotivational. They do not attack users for leaving 1 star reviews and they do not depend on reviews for their motivation.

    And why two starts? Why not one star then?

    Again, this statement is reflective of someone who is angry, and is using sarcasm to express their anger. Don’t personalize it.

    There are about 50.000 plugins in WP.org repository, do you want to help me to test the compatibility with all of these plugins before it will cause more problems and waste of users time?

    It is not the responsibility of WordPress users to help you test your plugin, so your request is inappropriate.

    Also, yes, there are currently 48,586 plugins on WP.org. BUT only ~ TWENTYTHREE have 1+ million active installs and your plugin is NOT compatible with at least one of them. I did not say and I am not saying that your plugin should be compatible with ALL 48,586 plugins on WP.org. YOU are saying that because you are reacting. You saying I should help you test your plugin with all 48,586 plugins is ridiculous, not constructive.

    However, I think that if you release a plugin then it should be compatible with the most popular plugins, or if it is not, then say so. That is what my review is about.

    I would suggest that if you would like your plugin to be popular, then respond to critical reviews in a professional manner. The moment a dev attacks a person for leaving a critical review, the perception of the developer and the plugin is reduced.

    As an example, take a look at the 167 ONE star reviews of Jetpack – most of those reviews are responded to by the devs, and the devs do not introduce ideas like “bad”, “punishment”, etc – Instead they respond in a pro manner.

    No plugin is perfect, including yours.

    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    • This reply was modified 3 years ago by ironfish2.
    Plugin Author SeedPlugins

    (@seedplugins)

    I can assume bad reviews about the plugin, not about an outdated description.

    I have more plugins with occasionally bad reviews, and other projects not only here in WordPress with poor rating, I do not feel it personal and is Ok, very rarely I discuss because the user is usually right about the problems detected.

    This plugin has a lot of defects, a lot of missing features, and a long way to improve and discover new failures.

    This is a criticism about the way you have used to notice the lack of plugin description. I think it is not generous and ignores all the developer effort because you could have notified this fact without further instead of writing a bad review.

    Why not a message like “Hey, do not be lazy, update the plugin description explanining these issues”?

    About your answers I think you are right in all the cases, it is simple irony by my side to highlight that this is not the way, I did not expect detailed answers, but I’m glad if I caught the eye.

    For me bad reviews is generally something positive! Means that my work needs improvements or just I did a bad job. At the end it is good for me and for the users and helps me to improve the code.

    But if any present or future plugin incompatibility will generate a bad review because it is not explained in the plugin description, not just for me, in general, then the situation does not help anyone.

    Kind regards,
    Pau Iglesias

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Does not work with Wordfence, and other security / firewall plugins’ is closed to new replies.