Welcome to ManageWP.org

Register to share, discuss and vote for the best WordPress stories every day, find new ideas and inspiration for your business and network with other members of the WordPress community. Join the #1 WordPress news community!

×

Why You Need To Discontinue Using Nulled WordPress Plugins On Your Site

wedevs.com | Aug. 14, 2018 | 12 min read

As a WordPress plugin owner it is nice to see such subject being discussed and dealt with. There are many implications to using "pirated" WordPress plugins, including security ones. Good read.

114 votes   Flag
Brian Jackson

Developers got families to feed too. Many users seem to forget this.

Reply
Sallie Goetsch (rhymes with 'sketch')

Headline rewrite: Why you need to STOP using nulled WordPress plugins. It's one thing to test a colleague's copy before you decide to buy, and quite another thing not to pay (or have your client pay) for something you're using to build your business with.

Reply
robert Abela

Thanks for your comment Sallie. I wouldn't even recommend testing a nulled plugin before buying a copy, it could also be infected. I would simply ask the developer for a trial of the plugin.

Reply
Sallie Goetsch (rhymes with 'sketch')

I'm not talking about a "nulled plugin" from some random place, but a practice I've used myself: I have a legitimate license for one site and while doing local build-out use my copy of the plugin to make sure it's the right one, before asking the client to purchase a license. Likewise, people who work together often might pass a copy of the plugin to a colleague to test. Of course, if a developer is reachable and you can ask the dev, you should reach out, but there are devs it's not that easy to get hold of personally, and sometimes if you need to test several items at once, setting those up can be time-consuming.

I absolutely advocate paying the original developer for the plugin, but the fact of the GPL is that what you are really paying for is updates and support, not software. People do have the right to reuse the code if they choose to do so.

If you file a trademark on your brand name, logo, etc., you can protect the trademark and prevent anyone from reselling your plugins/themes USING YOUR BRAND NAME AND REPUTATION. But your code is not "copyrighted," not when you are working with open source software.

If you haven't released it under GPL or equivalent, of course, you might have copyright on it, but it's not going to be listed in the WordPress repo and it's probably still hopeless. Adobe and Microsoft, two large and well-known makers of proprietary software, switched to a subscription model precisely because software itself is just too hard to make money selling.

Reply
robert Abela

Totally agree Sallie :)

Reply
Arjun Singh Thakuri

Yes, and many authors should start filing DMCA takedown notices where applicable.

Reply