Why I’m no longer using this plugin.

  • Resolved Tekguild

    (@kcrusher)


    7 years, 3 months ago

    I’m quite disappointed that the update no longer encodes emails in areas that it did previously and that I’d have to pay for it to basically work like it did before.

    I have your plugin on dozens of sites and these updates and changes have been really painful when trying to explain to my clients, especially the emails about ‘not being protected’ being sent to non-admins (any email address on the site that was ‘scanned’ but no longer protected.).

    I get it – you need to make money, but removing features that worked previously and/or forcing someone into a paid model to get the same functionality is..well, it puts us into a difficult position when trying to explain to OUR clients what they’re paying for, not to mention the panic caused when they get notices about not being protected.

    I don’t really expect a reply, I simply wanted to have my say and move on. I’ll be using a different plugin on principle alone.

    • This topic was modified 7 years, 3 months ago by Tekguild.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    7 years, 3 months ago

    Hey @kcrusher,

    Sorry, you’re having issues. I never removed any features from the free version and never will. This must be a hiccup, probably with an update from another plugin or theme.

    Would you mind sharing a link to your site where the plugin stopped working so I can have a look?

    Thanks!

    Thread Starter Tekguild

    (@kcrusher)

    7 years, 3 months ago

    Thanks for the offer, but I’ve already moved on.

    Here’s the thing – if it was caused by another plugin or update, was it due to lack of testing? When you change the plugin so significantly I would expect some thorough beta testing.

    The fact that the plugin sent even a one-time notice to *anyone*, especially non-admin users, is simply unacceptable. It does not inspire confidence, no matter how good your intentions are.

    I’m not trying to be mean or difficult – I simply want you to understand that we, the users, often have a significant client base and errant behavior from a plugin takes time and effort out of our day, likely unbillable hours, to rectify with our clients.

    I’ve already spent too much time dealing with this. Again, I simply wanted to make a statement and be on with my day.

    • This reply was modified 7 years, 3 months ago by Tekguild.
    Plugin Author Till Krüss

    (@tillkruess)

    7 years, 3 months ago

    Here’s the thing – if it was caused by another plugin or update, was it due to lack of testing? When you change the plugin so significantly I would expect some thorough beta testing.

    Yes, it can be a lack of testing, but often isn’t.

    For example, when I added “automatic cache flushing” in v1.0.15 the plugin broke sites that were using PHP 5.2. Even tho this plugin only advertises PHP 5.3+ compatibility, a few sites broke and that sucks. I released v1.0.16 to fix it the same day.

    Sometimes it isn’t lack of testing, it’s simply a conflict. Here is an example I just stumbled across today.

    The “Ginger – EU Cookie Law” plugin completely breaks email obfuscation. It literally un-does the encoding and spits out the plain text email addresses.

    It shouldn’t do that, it’s a fucking cookie banner plugin, but it does. I’ve already released a fix for it to my premium customers on a Sunday.

    Now I’ll have to reach out to the author of the Ginger Cookie plugin or come up with a solution for the free version that won’t break the 100.000+ sites that are using it.

    The fact that the plugin sent even a one-time notice to *anyone*, especially non-admin users, is simply unacceptable. It does not inspire confidence, no matter how good your intentions are.

    Yes, that was a mistake and won’t happen again. The opt-in warnings are much better.

    I’m not trying to be mean or difficult – I simply want you to understand that we, the users, often have a significant client base and errant behavior from a plugin takes time and effort out of our day, likely unbillable hours, to rectify with our clients.

    I’ve already spent too much time dealing with this. Again, I simply wanted to make a statement and be on with my day.

    I appreciate the feedback. I myself have the plugin installed on 50+ sites.

    chuckzwood

    (@chuckzwood)

    7 years, 2 months ago

    The fact that the plugin sent even a one-time notice to *anyone*, especially non-admin users, is simply unacceptable. It does not inspire confidence, no matter how good your intentions are.

    Yes, that was a mistake and won’t happen again. The opt-in warnings are much better.

    I would like to try your plugin on several sites I maintain, however, ^^^ THIS scares me!!!

    I do not mind emails/notices to ME, the administrator of the site, but I will not use a plugin that contacts people on the website it is supposed to be protecting.

    Please confirm that the plugin only contacts the admin, and DOES NOT contact any emails/phone numbers on the website?? Thank you!!

    Plugin Author Till Krüss

    (@tillkruess)

    7 years, 2 months ago

    Hey @chuckzwood! The email warnings are now opt-in only, so not automated messages will be sent.

    chuckzwood

    (@chuckzwood)

    7 years, 2 months ago

    Thank you very much for the reply!!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Why I’m no longer using this plugin.’ is closed to new replies.