• This is only a clone of Jetpack Lite 2.3.4.1 with name changed.

    Just an attempt from this plugin “author” to get some attention.

    By the way, very funny to see how he put the “PLEASE DO NOT POST YOUR ISSUES VIA THE WORDPRESS FORUMS” when he used the same forums to lie about Jetpack Lite and claim support and attention.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Samuel your attitude stinks! people only have to read the forum you are referring too to see. For some reason it seems like you are attacking nearly all of the people who have been using your plugin – marking threads as resolved when they’re not, blaming your plugin users for your mistakes, and generalizing some of us a stupid!

    I’ve moved on from JetPack lite after your forum thread performance and have uninstalled it from over a dozen of my sites and I have now started to NOT recommend your plugin to my clients (before I did actually praise it as being the next best thing to sliced bread)

    I’m sure i’m not the only one!

    Good luck Samuel with your future endeavors

    Plugin Author Pieter Bos

    (@senlin)

    Thanks for your comment in support @morphman, I appreciate it.

    To Samuel I can only say this:
    First of all, thanks for using the review system to fight your personal vendetta. I don’t think it was meant to be used in this way, and you give a perfect example of the reason why.

    Second I am not sure whether you have read the description of this plugin at all, because I think I make it very clear that I have forked your 2.3.4.1 version of Jetpack Lite.
    I actually did change a few things around, but since you have not bothered to have a look anyway, there is no need for me to go deeper into that.

    Fact of the matter is that there were a lot of people who totally loved what you did with Jetpack Lite! No need to install over-bloated Jetpack for only getting the stats. You made that possible and that has reflected in the number of downloads of your plugin.

    Perhaps you can therefore imagine that there are many users that just do not understand why you all of a sudden have opted for making Jetpack Lite an extension, i.e. depending on Jetpack.

    We don’t want to install Jetpack, it is that simple! Why is that so difficult to grasp for you?

    The only way for us users to keep what we had is to keep your version 2.3.4.1 installed with a change of version number. The risk of that however is that over time things can start falling apart.
    So what better way then to do something that the WordPress GPL license fully supports? Fork your 2.3.4.1 version of Jetpack Lite to ensure future development!

    For the support of my own plugins I prefer to use Github instead of the WordPress forums for the simple reason that collaboration is far easier there. That is my choice and since I re-released the good old working version of your plugin, I think I am entitled to make such a choice.

    You support your plugin(s) through the WordPress Forums, that is your choice and because I respect that choice I have left several replies in the thread you were referring to.

    I don’t think I have ever lied about Jetpack Lite, but if the readers of your review are interested to find out, they can decide for themselves. I am just very happy that with your 3.0.2 release you finally seem to have picked up on the idea to add some kind of notice to your plugin that makes the users of your plugin aware of the new dependancy on Jetpack after they have upgraded your plugin. It took a while to get that message through to you, but better late than never 🙂

    Let me end my reply in style (credits MorphMan):
    Good luck Samuel with your future endeavors

    A big thank you to Piet for continuing with this plugin.

    It is a real shame that Samuel decided to go on the attack after making some mis-guided changes to his plugin. His attitude is truly reprehensible.

    Cheers.

    Plugin Author Pieter Bos

    (@senlin)

    Thanks for your support Jonathan and please let me know (preferably via Github) if there is anything that I have missed while forking the plugin and removing some of the other unnecessary stuff.

    Just to second the thinks for this new (or indeed old) fork. It got me out of the situation I found myself in with Jetpak Lite and is appreciated.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘A clone not needed’ is closed to new replies.