Support » Plugin: Easy Code Manager » A cropped version of CJT…

  • I’m glad to see this plugin is free and open source.

    I’m sad that the developers want us to forcefully purchase the paid version. They are removing options that were given out free. That makes this software a piece of ransom-ware: “If you want to keep your website working as it does you need to pay us”.

    Please, don’t remove the ability to assign this to tags, custom post types and the auxiliary. Please don’t take out the ability to assign it to a footer. Please don’t remove the ability to turn on/off a code block.


    Edit: I’m changing my calification, because i saw the developers positive reaction of the developer to my opinion. But i still want to see the future of this project and if it becomes a nice drop-in of the old CJT plugin.

    • This topic was modified 2 years, 3 months ago by cablop.
Viewing 8 replies - 1 through 8 (of 8 total)
  • You know, it’s inconsiderate leaches that think everything should be given to them for free that give not only the WordPress community a bad wrap but the entire world in general.

    So it’s not good enough that the Developer is keeping his original plugin active for you to use (for free) as well as providing ‘this plugin’, an improved version; that you and the WordPress community can use (for free)?? Seriously!!?

    Tell me @cablop, How do YOU feed YOUR Face??? What are YOU contributing to this community FOR FREE you pathetic ungrateful maggot?!

    You should be ashamed of yourself… You’re an embarrassment to everything this community stands for. Stop expecting your mommy to wipe your rear-end for you and get a job.

    • This reply was modified 2 years, 3 months ago by VentureCore.
    • This reply was modified 2 years, 3 months ago by VentureCore.

    I’m the main developer of CJT and ECM Plugin as well.

    We really studded this too much.

    The simple answer is NO, you’re wrong

    What do you say would be right in case of removing or deprecating CJT.

    CJT Plugin still there and supported for wordpress compatibility, you can sill use it but don’t expect any other new features.

    Plugin Author wipeoutmedia


    Hola Cablop,

    I wanted to reach out to you regarding a recent review you made for Easy Code Manager here.

    I just want to understand your concerns as to why you have given 1 star so I can try to receive a better outcome for you and me. Do you currently use CSS & JavaScript Toolbox on client websites? Are you concerned that it will be deleted? Do you rely on CSS & JavaScript Toolbox?

    I am not annoyed that you spoke your mind and were honest about it. I just need to understand. I have not removed CSS & JavaScript Toolbox from

    Another thing, although I have said that CSS & JavaScript Toolbox is no longer supported does not mean – bugs are never fixed. I feel the solution, which is being used on thousands of websites SHOULD still have bugs fixed and be fully compatible with the latest version of WordPress. What will never happen is any more NEW features!!!

    Please let me know your concerns as I do listen and want to understand everyones opinions as to try to do the right thing. This is important to me.

    I look forward to hearing from you.


    Damian Baker

    • This reply was modified 2 years, 3 months ago by wipeoutmedia.
    • This reply was modified 2 years, 3 months ago by wipeoutmedia.

    Hello. @wipeoutmedia and @xpointer.

    My intention is not to hurt your project. I really understand that a software project needs funding. But to make a decision that can break websites is a bad move.

    From my experience, clients don’t understand it. Place yourself in the customer’s shoes: they find a free feature, they built a nice website on top of it, then suddenly the feature becomes paid. They feel like betrayed, that that was just a bait to get them. I was in such a situation before, the site heavily depended on a free plugin, they updated it, but removed many many features moving it to the paid plugin, the site becomes broken and unusable. I told my client to purchase the pro plugin, but she plainly said “how i’m supposed to pay to the people who broke my website? go find another solution, i prefer to pay for a different solution but not these guys”. The trust was lost. She is not able to trust those developers anymore so we had to find other solutions and wipe everything related to that plugin out.

    This plugin is very useful and we used them also in e-shops. Clients with e-shops are so demanding and of course they hate when their source of profit can get hurt from a plugin. They’re not developers, they see the world from the point of view of money.

    And i say that because the CJT plugin says its development stopped. There was no reference saying the plugin will be updated, and we know what that means. In a matter of months, WP will be updated and CJT starts to fails once the changes made them uncompatible.

    I don’t know what else to say. I think there should be a way to keep your loyal base of current users… and not to make them look like they’re forced to upgrade, but make them want to upgrade.

    • This reply was modified 2 years, 3 months ago by cablop.

    @manakio2k i find your attitude highly out of place… you are just looking the situation from one side, not from the points of view of the many actors involved in a succesful plugin.

    When there are good websites that were built around some functionalities of a plugin and then that functionality becomes removed in the free version, websites break, even to the point of become unusable. Clients are eager to pay to developers of plugins that break their websites. You need to be responsibe with your loyal customers and CJT is a plugin that was here for many years and many major versions (8 in total) with many users and stable websites.

    The notice on the CJT plugin says “we have dropped support and updates for CSS & JavaScript Toolbox”. So is is a matter of months, even weeks, for the websites to break because the current CJT version will be not compatible with a future WP release. To move to ECM is impossible, because ECM has less features. To fork CJT is not practical, because that will directly hurt ECM interests.

    The webmaster who maintains the website, not made it, also worries about it. And he is not going to get more work just to keep CJT or ECM in the website. He’ll just look for another option and walk away. And you’ll lose customers that way.

    If you have a nice useful and working solution, you can involve your community and find a way to move forward for a better future, @wipeoutmedia and @xpointer.

    Plugin Author wipeoutmedia


    Hi cablop,

    Hope you are well.
    Thanks for taking the time to share your thoughts and personal feelings towards this issue. You have provided honest feedback and it means a lot, especially coming from a long-term user of our predecessor solution – CSS & JavaScript Toolbox. So I do really appreciate the effort you have put into this reply.

    To let you know, there was never any strategy or intention to bait and snare users into an unwavering reliance of CSS & JavaScript Toolbox free, only to force them (from worry) into purchasing the premium edition at a later stage. You see, I was never that scheming. Nor did I have a long-term business plan or strategy in place. Instead, I just did what I loved. Taking an idea into a tangible product that was useful to the world and helping others.

    I believe many plugin authors like myself start their journey like this. They enter the world of WordPress plugin development and get absolutely lost with it. They have no idea on where the solution will take them in a few years time, no idea on marketing or launching a premium version, no idea on price-points, and the list goes on. Many like myself learn as we go. We make plenty of mistakes, we almost give up, then get back on the horse and make more mistakes and almost give up again. I am sure you understand the cycle! After almost 7 years later, I am more confident than ever in the knowledge I have learned from the WordPress community, and I feel a lot more positive about the future both in a development and business perspective.

    Regarding your feedback, now I totally get where you are coming from. I understand that your intention is not to hurt the project but to help us stay on the right path so we can make right decisions. I know I made a mammoth mistake by providing every feature that a user would ever need in the free edition of CJT. By doing this, it was always going to be a struggle to get users to upgrade to the premium version. But with that said, I realise I should not make the community pay for my mistake by dropping all support for CJT free in order to entice a purchase of the new ECM PLUS. I know there are thousands (20,000+ active installs) that are relying on CJT free to work perfectly as it should on both the current version of WordPress and on future releases. Of course this is the right on most ethical thing to do.

    Anyway, here we are almost 3 months after the ECM launch and I know a lot of premium CJT PLUS customers are having issues with migrating across to the complimentary ECM PLUS. Due to the complexities of the plugin, it is almost impossible to achieve a perfect migration. Currently CJT Code Blocks and Templates can migrate, but CJT Assignments and Shortcodes do need to be rebuilt. It’s a real headache and it again seems like another lesson learn.

    The solution it seems is to continue supporting CJT free with bug fixes and ensuring WordPress compatibility. But that said, I emphatically will NOT be adding any new features to CJT free. Now although CJT PLUS customers have been offered a complimentary license for ECM PLUS, it may be in their best interests to stay on CJT PLUS due to those migration issues. So the answer will be to continue to develop CJT PLUS with fixes and new features.

    Easy Code Manager PLUS will still be the flagship solution and will stay at the forefront of our development efforts. Since both solutions are in competition with each other, it would be in our best interest if Easy Code Manager overtakes CSS & JavaScript Toolbox as the go-to code management solution in the long run.

    I foresee that supporting both CJT and ECM solutions is going to be challenging, but I personally feel this is the right thing to do. I can only hope the WordPress community can support us.

    Thanks again for your review and follow-up posts.

    Kind Regards,
    Damian Baker

    I like to see you are reading what we users have to say and to take those things into consideration.

    I’m sorry i have to give a short answer now, but i also want to provide an answer, and more deatils later.

    I understand it is hard to maintain such big plugin, but also it’ll be bad to lose the userbase the plugin already has. It is good to hear you’ll keep both plugins for some time in oder to make an easier transition. It’ll be good if you find a way to ask current users what are the most used features. But i’m afraid those are the features i mentioned, specially:
    – Entire Website, that help users to modify or extend themes.
    – Custom Post Types, tags and custom taxonomies, because this is what they use for things like products in e-shops.
    – The footer, because this is how we easily add things like the Google Analytics and other tracing codes, without touching themes and independently of any current, past or future theme the site will use.
    – The ability to turn blosk on and off… just because we cannot just delete and recreate code blocks during maintence time.
    – And maybe some auxiliary features.

    Is CJT open source and available in some repository? I think the way the community can contribute to the plugin is by coding. I know how to code and i can contribute to, at least, help in keeping CJT compatible with WP updates in order to help people with existing sites with CJT – like me – to keep those sites woring without issues. No need to add more features, just proposing some developers can help to keep the plugin alive and maybe trim it a little bit.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘A cropped version of CJT…’ is closed to new replies.