Welcome to the official blog for the Plugins Team.
The team acts as gate-keepers and fresh eyes on newly submitted plugins, as well as reviewing any reported security or guideline violations.
Quick Links
The team acts as gate-keepers and fresh eyes on newly submitted plugins, as well as reviewing any reported security or guideline violations.
Quick Links
tl;dr – If you use a tool to generate code (be that a website that generates settings pages, or something complex like an AI to build the whole pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party), remember that YOU are responsible for licensing.
All code hosted on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ has to be GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. Compatible. This is not in doubt. More and more people are using tools to build code for them, based on bare-bones input. With the advent of ChatGPT, this has become more popular.
To be clear here: There is no guideline AGAINST using generated code.
You’re welcome to use whatever tool you want to build plugins. That said, you are 100% responsible for that code if you chose to host it here. This is not a change to any guideline, merely a reminder that if you claim it’s your code, you are responsible for it.
But the important bit here is that if means if ChatGPT, for example, built your plugin, you have to verify that all the code used is GPL compatible. Just like you are expected to validate licenses on libraries and code-snippets, everything in your plugin has to be GPL compatible. Should we determine that your code is a copy of someone else’s or includes code from non-GPL plugins, your submission will be rejected and any live plugins will be closed.
Sadly this has already become a small issue, as people asked an AI to build a ‘scroll to top’ plugin and it literally copied code from another, existing, plugin hosted on WordPress.org. Actually five times. And they were all rejected since it was pretty obvious.
Now before someone asks, yes it’s fine to fork code. You have to credit them, however, and that’s something those AIs have been pretty bad at doing. Also remember that the AI can tell you how to submit a plugin and be wrong. And by wrong I mean totally, 100%, that was really some bad advice someone got wrong. Make sure you double check. Robots won’t take our jobs yet.
If you submit code, it’s your responsibility. Nothing’s changed.
tl;dr? If you get a final notice from the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party team, please take it seriously. That really is you reaching your final chance with us.
There has been some confusion about what a ‘final notice’ means with regards to plugins or what it means to be banned.
The Plugin Team does not capriciously ban anyone. Actually we hate banning people. It’s a lot of work, it’s frustrating, it comes with anger no matter how we do it, and people always get hurt, especially users. That’s why we’ve established a warning system and do our best to ensure all developers are aware of infractions and allowed to course-correct.
A final warning, like it sounds, is an email with a rather stern content telling you that you’re on your very last chance.
The plugin directory emails out final warnings to developers/companies/groups who have either demonstrated a repeatable, constant, habit of violating guidelines, or who have committed an incredibly egregious violation. Those emails contain a reminder (usually in the form of a list of all existing problems) and a notice that if the plugins team has to contact them for any reason other than security related, the developer/company will be banned and all plugins closed.
If you keep making the same mistakes, and you keep violating forum, plugin, theme, WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more., or any other official guideline of WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, we will cease to host your plugins here anymore. You would have repeatedly proven that you aren’t able (or willing) to follow the guidelines, and we feel it’s unfair to put the burden of monitoring you on the volunteers, as well as subject your users to that kind of behavior.
In general, people are quite responsive to those emails. They recognize the issue, modify their behavior, and it doesn’t come up ever again.
The warnings are a wake-up call as to the risks involved, as well as our expectations, and while they can scare people, it’s somewhat of a needed scare. By the time someone gets to that point, we have usually sent multiple warnings about various issues (be they fake reviews, asking for admin access, spamming users, or sharing developer accounts) prior to the final-notice, in the hopes that people will change their behavior before we have to get to the final notice.
Sadly, there are always people who don’t take those emails seriously, or think that if enough time has passed, the finality has faded and it’s okay to make the same mistakes and we will forget about it and forgive everything.
Given the size and scale of WordPress, it’s impractical to have to keep reminding people over and over that they actually do have to comply with the guidelines they agreed to, and it takes away time from frankly more important matters, like security.
Most of the time, yes. The rare exception is if something is so terrible, we have to pull the plug right away. Usually that means someone snuck back in after being banned, or made a death threat.
But the majority of users get an email with the subject [WordPress.org Plugin Directory] Notice: (your plugin name) and that contains a warning of a specific behavior.
Unless the email said “This is your final warning” then no.
We regularly warn people about issues, from trademark abuse to fake reviews. Those are just warnings. As long as they don’t repeat, we don’t have any issues. People make mistakes and it’s okay, as long as you learn from them and stop making them.
No, not a plugin one. That just means the forum moderation are concerned about your actions and want to keep tabs on you. That could be anything from asking to admin access to swearing or jumping on other people’s topics all the times.
That said, if the forum team flags you like that, and you keep making the same mistakes, they may come to the plugin team for backup.
Usually it’s not a single event, but a demonstrable pattern of violations. By that we mean the person(s) involved have broken many guidelines, over and over, for a sustained period of time.
Just for an example, let’s think about asking someone for admin access. That is prohibited in the forum guidelines for safety. Asking once is a mistake, and we know mistakes happens, so the person will get a warning from the forum mods. If they happen to ignore (or miss) the warning and do it again, their account gets put into a ‘moderated’ status, and all posts have to be approved by a moderator. That moderation flag is not a punishment. It’s there to make sure the mistakes stop, and to help protect the developer from harming themselves. After that, though, if it keeps happening, the plugin team is asked to step in and issue a warning.
But even so, our first warning is not a final notice! It’s a first warning.
From them on, if the person keeps violating the guideline, that is when that they will get that dreaded ‘final warning’ from plugins.
That means you did something really bad, but not quite ban-worthy yet.
Sometimes it happens when someone gets a warning (like ‘don’t ask for admin access’) and replies “I cannot be held responsible for what my staff does.” That gets a final warning right away and a reminder that you absolutely will be held responsible for the people who represent you and your product. If you cannot trust your people, don’t let them represent you.
Other times, it’s a mistake so large, and so fraught with danger or concern, we feel that the only proper recourse is to jump directly to the final notice. Those are incredibly rare, and I’ll explain a little more about that later in this post.
Besides ‘never violate the guidelines,’ the easiest way would be to acknowledge and rectify any issue that a moderator or plugin rep brings up. If someone tells you not to ask for admin access? Stop asking for admin access. If they tell you not to call users vulgar names? Stop calling people names.
Basically listen to the warnings, take them all seriously, learn from them, and change your behavior as needed.
We know that everyone makes mistakes, and we will forgive a lot. But at the same time, that kind of forgiveness requires you to make changes. If you apologize and just do it again, we’re not going to be able to trust you, and that’s how you end up with a final warning.
If that happens, it means you’ve somehow failed to impart on your support staff the reality that they have to follow the guidelines too. They are your responsibility, and if you cannot ensure they follow the guidelines, we simply won’t allow them to use the forums at all anymore, and you will be told why.
As for how to fix it? You need to address the issue on your end. Why are you staff not aware they have to follow the guidelines? Why are they not listening to the warnings issued? Why are they continuing to have this kind of problem?
Make sure everyone who represents you (in the forums, on social media, wherever) knows that their actions reflect on your whole company, and they have to follow the guidelines too. After all, if your intern violates Twitter’s guidelines using the company account, it’s your company account that gets suspended.
They probably are, actually.
We respect everyone’s privacy and we don’t blast anyone on socials, so all conversations are in confidence as much as can be. After all, if you make mistakes and change your ways, you wouldn’t want the whole world knowing how much you messed up, right? It would be terrible embarrassing! Instead, we treat you like an adult, take you to the side, and talk to you privately.
Most people actually listen to the first warnings. If a forum mod tells them to please stop doing a thing, they apologize and stop. The plugins team never gets involved, and honestly that’s the best way.
Luck? Or maybe we saw you made it once, and never again.
Mistakes happen. Most mistakes, as long as they aren’t repeated, are recoverable. Don’t panic if you made one mistake. As long as you keep learning, adjust as needed, and don’t do it again, you’re going to be fine.
Most of the time, that means we changed the guidelines since the first one, and felt it would be inhumane to not warn you about them. We will do this even if your violations are unrelated to the changes to the guidelines.
The other time would be if we think you really did change enough since the last notice, but you’re running down another wrong path. Basically? We think you are capable of change based on your historical behavior, and we want to give you another chance.
Normally we warn but yes, in some specific cases, we won’t. They include, but are not limited to:
In those cases, we will always email and tell you exactly why you were banned.
The people who get those insta-bans are often ones who got a plugin review and replied with vulgarities or suggestions of sexual activities involving a cactus. Not a joke. It was in response to being told to not include their own jQuery, to boot. We do get that people have bad days, and we try to help them get back from it, but that kind of abuse is untenable. If you’re willing to talk to us like that, we shudder to think how you’d behave to users!
Honestly? Not a whole lot. It’s incredibly hard to make anyone trust you after you reached that point.
If you got the final warning and kept violating guidelines, then you just squandered your last chance. The whole reason you got that warning, and not an instant ban, was that we were trying really hard to get you to correct your behavior. When you don’t listen to those warnings, we believe you are who you act like, and we ban you.
Now of course there are always exceptions. They are incredibly rare, and come with a lot of provisions and caveats. If you really think you should be given a second final-chance, reply to the email and explain why. Just be aware that the odds are against you, since you have already demonstrated you cannot (or will not) follow guidelines.
Historically because we don’t want to keep hurting them.
Angry people lash out see, and while we’re ‘fine’ with taking it on the chin when people lash at us because we don’t explain the details about a ban (except in very rare cases), if we made things public that mob would go after the banned dev.
See, if everyone knew that a person or even a company was banned after we argued with them every few months for three years about not asking people for admin access on the forums, or not tracking users in their plugins, they would have a very different view of the developers.
If everyone knew a company was banned for telling the plugin team they could perform sexual acts on their parents (wish I was joking), then what? Making that public in a place where they cannot refute means they have no ability to make amends. And yes, sometimes people do come back and apologize sincerely for that behavior.
We don’t disclose because of a kindness, and a desire not to destroy someone’s reputation (or livelihood). Perhaps we’re now at the point where that policy needs to change, in order to minimize the false narratives running around, but I’m really divided about that one, personally.
I can’t answer that for you.
Personally, I would take their explanations with a grain of salt. Everyone (and this includes the Plugin Team) tends to tell a story to paint themselves in a better light. If someone is arguing they did no wrong and were banned, they’re probably leaving some information out. Then again, there are developers who tell people they messed up and got banned and deserved it.
I know this is a lot to think about, and some of it sounds incredibly petty.
No one on the plugin team wants to close plugins, especially the well-known ones. It’s harmful to the community as well as the developers. At the same time, there is a practical limit as to how much the volunteers on WordPress.org are willing to put up with someone’s misbehavior. That’s why we have taken to formally warning people that they are on their last chance.
It’s our fervent hope that with the information in the final warning, people will correct their behavior and stop violating guidelines.
tl;dr: If you put a website as the official developer or pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org and it does not exist (or is under construction), your review will be pended.
We know that sounds really weird, but yes, we’re saying if you tell us that your domain is XYZ and that domain doesn’t exist, or isn’t public, your review is going to be paused until you finish the site.
The primary reason for that is because those URLs will be seen by all your users, and if a user sees a great looking plugin with an incomplete website, they will not trust you. That’s actually something that scammers do on the regular, and you’ve made yourself look like that.
So to protect you from an undeserved bad-rep, we check your domains.
The secondary reason is, if you’re a service, we really do need that live so we can review the website and ensure it and the plugin are compatible with our guidelines.
Most of the time, yes.
However if you’re a service and the service runs through that website, then not only will you be required to make the site public, but you will also need to include a terms of use and/or privacy page on your site.
Reply to the email with “Ooops, I typoed, the real URL is …” We’ll ask you to update the code and your account, so your users don’t get confused, and all will be well.
Then you used the wrong account to submit the plugin. Remember ALL official plugins have to be owned by the official company. If you were hired to make a plugin for BoogieDownBlues (a fake company) and the domain is boogiedownblues.com then the account that submits the plugin has to use that domain for their email.
That protects you and them from any legal action later on.
No. Again, we’re trying to protect you from being seen as an untrustworthy developer. Also we want to make sure your site isn’t violating rules.
This generally happens with service plugins, and if that’s the case, we will tell you no. The site has to exist so we can validate the service.
You do not, but we do recommend it. People prefer to know there are real humans behind things.
Maybe. It depends on what you put on the placeholder page and (again) if you’re a service. If the placeholder says ‘Coming soon!’ then no.
If your domain is filled with placeholder, we consider it to be incomplete and will point out the problem. Same goes for clearly fake addresses and those about pages that all have the same face.
Because you told us (and by extension all your users) “this is who I am!” If your personal site is ‘coming soon’ or has a placeholder, no one can make a judgement on you save to say you’re a dev who can’t make a website. And yes, that is patently unfair, we know, but that’s what people will think. Heck, they complain to us every time we miss it. We would rather you not start in a bad place.
Because using a trademark in the domain name violates trademark law.
Using a company’s trademark in a URL as a domain name in whole (or in part like wordpress-example.com) may constitute a violation of the company’s trademark rights. See Brookfield Communications, Inc. v. West Coast Entertainment Corp., 174 F.3d 1036 (9th Cir. 1999).
What you can do instead is have example.com/trademark/ — that is generally allowed.
Keep in mind, some organizations (like WordPress) will allow the ‘short’ versions so wpexample.com would be fine. Others (like WooCommerce) have more restrictions, and actually prohibit wooexample.com
Always check the trademark guidelines first!
#remindertl;dr: Don’t make reviews for your own pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party(s) using other people’s accounts. We will remove them and warn you first, and if it keeps happening, your plugin will be closed.
There have been a lot of reviews being removed for being invalid in ways beyond a ‘normal’ sockpuppetSockpuppet A false online identity, typically created by a person or group in order to promote their own opinions or views. Generally used to promote or down-vote plugins en masse..
We know this is messy and scary because any time we say ‘Do bad things, and your plugin(s) will be closed!’ is a terrifying prospect. We really do know that. We really don’t want to do it, which is why we warn people instead of just closing everyone who makes mistakes. Our goal is, and has always been, to make a place where users can download functional, safe, plugins that solve the problems faced by users.
At the same time, we know that developers want people to use their plugins, and one of the ways that happens is by being popular. And yes, one of the ways to become ‘popular’ is to get a lot of good reviews. Which is how we get here. Sometimes people leave reviews for their own plugins. Actually, a lot of the time.
We’re not talking about an individual developer using their developer account to leave a review on their own plugin. While that’s weird and pretty pointless in the long run, it’s not currently prohibited and we leave those alone unless you’ve been flagged for fake reviews in general. Instead we recommend you not review your own plugins since it doesn’t help you out. People generally assume you like your own plugin, so your users won’t learn anything from the review, and since you left it yourself, you won’t learn anything either, making it a net-loss.
The kinds of reviews we’re talking about is when someone (or a group of someones) makes multiple accounts with which to leave reviews about plugins. And this is a global issue. Fake reviews are a huge problem not just on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. Amazon in particular is filled with fake reviews, and they’re getting harder and harder to spot. It’s an ongoing battle to spot them before they get ‘too bad.’ We aren’t perfect, and that’s why the first time we see someone leaving fake reviews, we warn them. What happens after that is usually pretty telling.
One big thing to keep in mind, reviews are for two purposes:
Both of those things, when they’re positive, can help your plugin become more popular. And of course, if they’re negative, it can hurt you. Which is why people work so hard to earn and merit positive reviews.
A fake review is a review made by someone who is not your actual user.
Sounds simple, right? If you write a review for someone else about your own product and hide who you are, that’s fake. The most common reason this happens is that an intern or a marketer gets the bright idea to share customer stories on the WordPress.org review system. The problem? They’re posting for the customer, which is making a fake review.
Another common way to make fake reviews is to use sockpuppets.
A sock puppet or sockpuppet is an online identity used for purposes of deception. The term references the manipulation of a simple hand puppet made from a sock, and was originally referred to a false identity assumed by someone to hide who they are and talk up themselves.
For example, if you make a second account and post a question about your plugin and then reply as your normal account? You’ve made a sockpuppet.
Sockpuppet accounts are very commonly used to leave positive reviews on plugins.
An invalid review is one that was made under duress or other promotional encouragement, or one that was made on behalf of a real person.
For example, if you offer a discount for your products if a user leaves a review, then you’ve actually just bribed them for a review, which makes it an invalid review. When people are compensated for a review, they generally leave better ones than they might if you just asked. Related to this, if you tell someone you won’t refund their money unless they leave a positive review, you’ve blackmailed them, and that too is invalid.
As another example, if someone leaves a great review for you via email or on your website, and you help them make a user account on WordPress.org (or make it for them) just to leave that review, you have invalidate their review. We have no way to be sure you didn’t alter the review, and your involvement could have altered the review content simply by being there.
Another kind of invalid review would be one made by someone with a personal, or professional, relationship to you. In other words, if you ask your parents or co-workers or people who share a co-working-location to leave a review, you’ve inadvertently asked them to make invalid reviews. This is a little touchy, since sometimes they are your users. The issue here is that people who know you are more include to leave favorable reviews, but also they can tell you to your face (virtual or otherwise) how they feel. You don’t actually need their review, and they can be more honest by talking to you via your existing connections.
A counter to this is sometimes your friends do legitimately use your plugin and see the note “Please review!” in wp-admin and leave you a review. Those are totally fine and rarely raise red flags.
More or less the same way people know when a term paper is plagiarized.
There are significant tells in most reviews that give away the actual author. We also take into account things like the age of the user (that is, how long ago did they create their account), what their other actions were, where they logged in from, what their digital footprint is, what their email is, etc etc. Then we compare that to all the other reviews made for that plugin and for other plugins and themes around the same time.
Or, as we tell people, we have a complex set of heuristics, as well as researchers who are experts with tracking down users.
Two reasons which sum up as privacy and security.
First, the more we let on about exactly how we do this, the more people will learn about how to get around them. It’s like spam. The more spammers know about how they’re caught, the more they work to get around those limits.
Second, and this is more important, some of that information is private. Telling people exactly who did the bad thing, how we know, and sharing IPs and emails, is a privacy violation. It would run afoul of GDPR related laws, which by the way is also the case in some states in the US (like California).
Because it wasn’t.
The majority of reviews reported as ‘fake’ come from developers reporting a brand new user whose only post in the forums is a negative review on their product.
This does not mean the account is fake. It doesn’t even mean the review is invalid. It means someone was angry enough to make an account and leave a review. That’s a pretty painful thing to get, I know, but just because someone doesn’t like your work doesn’t mean they or their comment is invalid.
We use our tools to check on the account and will remove anything that we can prove is fake, but a lot of the time it’s really just angry users.
No, we don’t track VPN usage, but we do take its use into consideration.
There’s nothing wrong with using a VPN. I’m writing this post on one. What’s wrong is people using VPNs to get around things like bans or to hide their accounts. That’s why flagging the use of a VPN (and which specific VPN it is) is a part of our process, but it’s not the ultimate be-all and end-all of things.
Keep in mind, there are certain VPNs utilized heavily by malicious actors. Some specifically exist to be used to generate fake reviews. If your company is using a VPN, make sure it’s a legit one (not one of those free, fly by night, ones).
First of all, you’ll get a warning. In general this is how everyone finds out about being flagged. We will make a note in your plugin as well as on the accounts used.
In that warning email, you will be told why you got flagged, that we saw the reviews and they’ve been removed, and that all suspect accounts have been suspended. We have read-receipts on our emails, so we know if/when someone read it. That means the situation persists, and no one read the email, we will close your plugins to force you to pay attention. If it keeps happening after that, you will find your plugins and account closed.
The email also explains that all we want is for the fake reviews to stop. Mistakes happen, please don’t do it again.
That means either you noticed before you got the email or (more common) we figured out someone else was trying to frame you. We usually don’t tell you so as not to scare you. Removing invalid reviews is a regular occurrence for every single review-platform, and if we told you every time we removed a spam or fake review, you’d get real tired of it real fast.
In most cases, you won’t.
We know that the reviews appear valid to you, but we can see things you cannot. Just for an example, a real user of yours wouldn’t use a VPN from Russia and a disposable email address to leave that glowing review which is identical to another review also left from Canada and a different VPN at the same time. Also some users think it’s a great idea to make fake accounts to promote you. We have no idea why they think that, but we will remove those and the user will be banned, so all their reviews become invalid.
There’s also a common trend where companies make reviews for people. They get a good testimonial and make a review using that. Sounds smart, but it’s still spamming.
As horrible as this sounds… Are you sure? Double check. Do you work with anyone else? Do you share a co-working place with others? Do you and your company all use the same VPN? Did you ask a bunch of people at an in-person event to leave a review? Did your spouse tell you how cool your plugin was and leave a review? All those things can set up warning flags because they mimic suspicious actions.
If any of those sound familiar, fess up. Just tell us “Hey, I’m sorry, I asked my coworkers/spouse/family to leave reviews. I didn’t realize how that looks.”
If you’re still certain you didn’t do it, just tell us. “I don’t work with anyone else, and I know I didn’t do this.” We’ll check again. It’s possible that someone’s trying to attack you, and while we make every effort to be as certain as we can be that it’s not that, we’re not perfect any more than you.
We are very well aware how painful and scary the email is, and we’ve worked on the language to try and make sure it’s less so.
Apologize and don’t do it again. Seriously, that’s it. Mistakes happen, and it’s okay if you make one. Just don’t repeat it. We absolutely, totally, forgive honest mistakes.
We do remind you to make sure everyone who works with you on the plugin knows this. You are responsible for the actions your employees/coworkers/etc take on your behalf. If they spam, you are on the hook for their actions. Usually we see repeat infractions come from that.
In most cases, yes. However you will be asked to formally take responsibility for all of that person’s actions on WordPress.org for as long as they represent your company. That means everything they do is your responsibility and if they violate any guidelines, you will be on the hook for that infraction.
In some cases, the person is permanently banned and that generally means it’s related to previous guideline issues. If that is the case, we will explain that, under no circumstances, are you to help this person regain access. We recognize that sometimes employees or staff go rogue, and we are attempting to insulate your from their behavior.
Glad you asked! Besides the obvious (don’t hire people to boost your review rating), you should be aware of the following:
You can (and should) ask your users! Put a notice on your plugin settings page. Make a dismissable alert that asks people to review. Post on Twitter or your website. But really? It’s down to asking your users in a kind, and non spammy, way. Those people will leave the reviews you need.
I understand why people get confused about this one. Asking people for reviews is fine, but then to say asking people you know isn’t? Yeah that sounds weird. But the crux is to think about what a review is for in the first place.
A review is someone’s experience with your plugin. For good or ill, it’s them using the plugin and sharing their story.
If you’re asking people to leave reviews to learn about what they do and don’t like about your plugin, then there’s no point to asking folks you know since you can just … ask them. In turn, they can just tell you to your face how they feel. Also they’re generally more inclined to leave good reviews, though I will admit we’ve seen someone leave a 1-star review for their spouse.
Interestingly, that review was invalid, as the review was a personal attack on the developer.
Have a shout.
tl;dr: Never test vulnerabilities on someone else’s live site without their permission.
By now, a lot of you have read the post about the so-called “WordPress Plugin Confusion” whereby a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party hosted on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ can ‘override’ a plugin not hosted here, by using the same name/permalink. Someone even made a CVE for it.
Please stop ‘testing’ this vulnerability with us.
This is not a new issue by any means. Heck, this has been something people report on now and then for years. In the past, the plugin team coordinated a release of a plugin to intentionally do that and protect users from a significantly dangerous plugin. We’ve locked out permalinks to prevent abuse and so on.
Sadly, the post conflated a couple of issues, which have to do with social engineering and a misunderstanding of why we have those permalink-checks for trademarks. Also it’s entirely incorrect with this one claim:
and the whole approval process is automated
This could not be further from the truth. All new plugins submitted go through human review. When you submit a plugin, somebody reads your plugin code, your submitted slug and name, checks on the history of the plugin, checks that the developer isn’t a returned banned user, etc. The process is by no means “automated” and while it has some automated pre-flight checks, they’re really there to weed out things that would end with a pended review, to make the process faster for everyone. While we have some tools we run, they don’t actually approve or reject anything, they’re just fancy code-sniffers, customized to look for specific patterns or known bad behavior, outside of the overall quality like PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. (you are using that, right?). Submitting things to test out what you think is an “automated” system is wasting the time of our volunteers and reviewers.
See, that trademark ‘blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.’ isn’t actually there to protect trademarks for the owners. We have them to make our life easier and to protect you, the developers, from making some pretty common mistakes. Just for an example, we block ‘akismet’ not because we were asked to by Automattic, but because over 50 people a year tried to submit a copy of Akismet instead of uploading it to their own site.
As the post (properly) notes, you can’t submit a plugin with a permalink that’s already in use, be it on WordPress.org or if it has a notable user-base outside of WordPress.org. Even if a name gets by those checks, the review team can see if the permalink is being used and by (roughly) how many people. That’s a large part of why we have humans checking these things. A human can look at an email and a plugin and check for proper ownership.
By the way, as a number of people have complained about, this is why we require official plugins to be owned by demonstrably official accounts (like with an email address that uses the right domain, and so on). It’s not just to prevent trademark abuse, it’s to ensure that kind of thing is less likely to happen.
Now. Do you need to test this? No. All you’re doing is making things more stressful and more likely to be missed, which doesn’t solve a problem. Do you need to add your trademark to the blocked list? Again, no. Unless it’s being actively abused, or there’s a high-risk situation that it might be, it’s just adding more work for a low (to negligible) risk in the first place.
How DO you protect your own, non-org hosted plugins, from this?
Use the UPDATE URI flag.
We check for it on .org, and won’t allow you in with it (since… why?) but for plugins we don’t host, well that’s literally why it exists 🙂 Use it. Love it. But please, remember the first step in ethical hacking is never trying out a vulnerability on someone else’s site without their permission.
Hi Devs!
We’re getting nearer to WordPress 5.9, and that means the email will be headed out soon.
This is the perfect time to double check the email on your accounts, especially if it’s a group email/mailing list. Make sure external emails (like … us) can contact you without bounces or autoreplies.
You also should check everyone who has commit access to your pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party! Did someone leave? It’s okay to remove their access, and in fact is great to do so for security 🙂
And as a regular reminder: Never share accounts! Every individual human should have their own individual account. That lets you (and us) keep tabs on who did what.
The field guide is out and the email has been sent.
If you find your pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party has been closed, it would be for one of the following reasons:
If your plugin is still open? Please re-read the field guide. It has some pretty cool stuff 🙂
Update from the PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Review Team: This post is no longer being updated, so please use the guidelines and FAQ for any information you’re looking for.
Caveat: While this topic always brings up people arguing that the GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. means they can (and yes, you can copy GPL plugins and do whatever you want with them), we wish to remind developers that just because the GPL allows something doesn’t mean we will host it here. Our guidelines are considered above and beyond the GPL. After all, the GPL doesn’t say you can’t punch someone, but if you get into a fistfight at a WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more., we’re not going to host your plugins.
Taking someone’s pay-for code and re-releasing it as free-of-charge is considered (by us — the Plugin Review Team) to be a form of piracy and is not welcome here. It doesn’t matter if the code is GPL, it matters that When you do that, when you copy and re-release someone’s code without any changes, you’re stealing the opportunity of the original developers to make a living, and we feel that is detrimental to the community. In addition, it’s often in violation of the terms you agreed to when you downloaded the plugin from the developer in the first place.
By you doing that, and rehosting here, you put the entire directory in peril. Arguably we become responsible for your actions. As such, we do not permit plugins that are sold off WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ to be re-hosted here.
The only exception to this (besides it being your own plugin) is if you have made a significant fork, properly credited in the readme and inline code, and everything was 100% GPL compatible, including the terms from where you bought the plugin. If you pirated a plugin, or if you violated the license purchasing terms (which may say things like you cannot resell it), then we cannot host the code.
Edit: It’s important to note that adding non-GPL compliant terms to a license may in fact invalidate the license, which means we can’t host it here anyway. The above comment is not in support of people violating licenses nor are we attempting to protect and help those people in any way. We are trying to point out that even if a license says it’s GPL, if it’s sold with terms that violate the GPL, it cannot be hosted here either. tl;dr? If the license or terms are sus, we can’t host it.
If the plugin is your own plugin and you just want to re-host here, we will do our best to validate that claim, and may pend your plugin while this is researched. We appreciate your patience when that happens.
If you feel someone took your plugin and hosted a copy of it here, please email plugins@wordpress.org with a link to the plugin as it’s hosted here, a link to your original plugin, and (if the plugin is hosted outside WordPress.org) attach a zip of the plugin so that we may compare the two.
Edited to add: This post is not about the GPL. This is only about the existing WordPress.org Plugin Developer Guidelines. You should not, under any circumstances, use this post to frame your understanding or interpretation of the GPL as it is not intended as such. Again, this post is about the plugin guidelines, the ones all plugin devs already committed to following, which have long since stated that immoral or ethical practices are not permitted here.
Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613504342","hasChildren":false,"userLogin":"adegans","userNicename":"adegans"},{"type":"comment","id":"43977","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-mnelson4 even depth-2","parentID":"43976","contentRaw":"\ud83d\udc4d thanks! This sounds like a fair policy.","contentFiltered":" \ud83d\udc4d thanks! This sounds like a fair policy.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43977","unixtime":1613507373,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43977&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" \u2026violated the license (which may say things like you cannot resell it)<\/p><\/blockquote>\n Is a \u201ccannot resell\u201d clause even possible with GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613507467","hasChildren":false,"userLogin":"tivnetinc","userNicename":"tivnetinc"},{"type":"comment","id":"43979","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-ipstenu bypostauthor even depth-2","parentID":"43976","contentRaw":"2-3 years ago isn't today, and expecting us to never change or improve policy is sort of unreasonable, isn't it?\n\nEmail again, with the details. I promise it will get a second look.","contentFiltered":" 2-3 years ago isn\u2019t today, and expecting us to never change or improve policy is sort of unreasonable, isn\u2019t it?<\/p>\n Email again, with the details. I promise it will get a second look.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43979","unixtime":1613507679,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43979&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" I don\u2019t think so, but since I\u2019m not a lawyer, and since people do all sorts of weird things, it\u2019s better to be safe than sorry and spell that out for people. Usually it\u2019s in the terms of \u201cIf you buy this from us, you agree not to resell\u201d which is arguably unenforceable since it\u2019s a GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613507847","hasChildren":false,"userLogin":"Ipstenu","userNicename":"ipstenu"},{"type":"comment","id":"43981","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-mattlee even thread-odd thread-alt depth-1","parentID":"0","contentRaw":" Taking someone\u2019s pay-for code and re-releasing it as free-of-charge is considered to be piracy<\/p><\/blockquote>\n This just sounds like a Red Hat Enterprise Linux\/CentOS situation. That\u2019s not considered piracy.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43981","unixtime":1613509540,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43981&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Cool. Nice to know you guys are taking the extra time to be the PluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party<\/span><\/span><\/span> police as needed. \ud83d\ude09<\/p>\n Thanks<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43982","unixtime":1613509840,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43982&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Finally! thumbs up.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43983","unixtime":1613510144,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43983&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" It certainly could be, and back in 2000, it totally was fought about. And I will not, it\u2019s considered to be piracy and is not welcome here<\/em>. Which means .org, in this moment and with the expectations being what they are.<\/p>\n Forking is one thing. These aren\u2019t people forking and changing code, these are literally people making a copy, where the only changes are to hide who they took the code from. No new features, nothing.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43984","unixtime":1613510718,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43984&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" I think the wording of the post is problematic, whilst I generally agree with the sentiment, its references to the GNU GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613512083","hasChildren":false,"userLogin":"SimonRWaters","userNicename":"simonrwaters"},{"type":"comment","id":"43986","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-ipstenu bypostauthor odd alt depth-4","parentID":"43985","contentRaw":" \u201cstole\u201d (no one lost anything they were entitled to)<\/p><\/blockquote>\n I would disagree. If you sell a thing and someone takes it and gives it away, without your permission, then the potential purchases (i.e. the money) was stolen from you. Your opportunity to make a living is being actively harmed. That is a net-negative to the community.<\/p>\n Whomever supplies a pluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party<\/span><\/span><\/span> CAN\u2019T add additional terms under WordPress\u2019s own choice of license\u2026.<\/p><\/blockquote>\n Assuming that those plugins are GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613513023","hasChildren":false,"userLogin":"Ipstenu","userNicename":"ipstenu"},{"type":"comment","id":"43988","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-jrf even depth-4","parentID":"43985","contentRaw":"Quite apart from GPL, it is still piracy. Open source licenses do not supersede copyright. The original author(s) still has that and if someone misrepresents the code as their own, while it is ripped off - or politely put \"forked\" - from someone else's code, they *are* violating the author's copyright.\n\nA fork of code, in itself, doesn't violate copyright as the original commits crediting the original author(s) are still in place.\nAs soon as the original commits are \"destroyed\" by committing the code under your own name in another type of repo, you violate copyright though.","contentFiltered":" Quite apart from GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613526127","hasChildren":false,"userLogin":"jrf","userNicename":"jrf"},{"type":"comment","id":"43989","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-khalilu odd alt thread-even depth-1","parentID":"0","contentRaw":"Dear Mika\n\nThank you so much for the fair policy. Very happy to see your email today in my inbox. :)","contentFiltered":" Dear Mika<\/p>\n Thank you so much for the fair policy. Very happy to see your email today in my inbox. \ud83d\ude42<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43989","unixtime":1613535302,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43989&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" or politely put \u201cforked\u201d \u2013 from someone else\u2019s code, they *are* violating the author\u2019s copyright.<\/p><\/blockquote>\n If they keep the author, license and copyright (and only add their own) it\u2019s not piracy. Calling LEGAL copying of code piracy is an oxymoron.<\/p>\n As soon as the original commits are \u201cdestroyed\u201d by committing the code under your own name in another type of repo, you violate copyright though.<\/p><\/blockquote>\n What are you saying? That you need to have the need of the original commit history intact to have a valid fork? If so you are wrong. All you need it keep the copyright, original author(s) and you can commit it in a new repo however you like. If there is a trademark involved then you need to rename it. You should like you have no clue. Even if you \u201cdestroy\u201d as you put it by committing in under and a new repo you do NOT violate the copyright.<\/p>\n Never mind if I just misunderstood you. But you sound like you do not understand the GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613546683","hasChildren":false,"userLogin":"nico23","userNicename":"nico23"},{"type":"comment","id":"43991","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-nico23 odd alt depth-3","parentID":"43984","contentRaw":"It's not piracy and you clearly do not understand the GPL, put that on display here.\n\n It\u2019s not piracy and you clearly do not understand the GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613583413","hasChildren":false,"userLogin":"nico23","userNicename":"nico23"},{"type":"comment","id":"43992","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-nico23 even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"I am not really against this. I certainly would not like to see my premium addons forked and released for free on wp.org BUT<\/strong>\n\n I am not really against this. I certainly would not like to see my premium addons forked and released for free on wp.org BUT<\/strong><\/p>\n Taking someone\u2019s pay-for code and re-releasing it as free-of-charge is considered to be piracy<\/p><\/blockquote>\n Calling any<\/em> GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613583512","hasChildren":false,"userLogin":"nico23","userNicename":"nico23"},{"type":"comment","id":"43993","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-nico23 odd alt depth-2","parentID":"43992","contentRaw":"1. You can not claim your software is GPL and then say. \"Terms: you can not resell it\".\n2. You can not \"dual license\" like this. When your software is GPL people can do almost whatever they want with it as you point out at the very top! You can not have it both ways and say its GPL and then say \"You can not resel because of 'license' \". The GPL specifically allows reselling! So what is this about?\n3. You know for a fact that like 99% of even the premium stuff for WP is 100% GPL so do NOT make it sound like it's not legitimate to make something up like you can not sell it. You call people who copy legally \"pirates\" and then defend GPL violators<\/strong> who make stuff up to scare off naive people. With no right to do so!\n\nYou even tagged this with #theft - laughable!","contentFiltered":" 1. You can not claim your software is GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613583530","hasChildren":false,"userLogin":"nico23","userNicename":"nico23"},{"type":"comment","id":"43994","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-nico23 even depth-3","parentID":"43993","contentRaw":"The beginning of your post was OK, but you quickly went downhill. If you have rules for wp.org that go beyond the GPL that is perfectly fine but do not misrepresent the GPL and tell the truth about it. Make it clear what the differences are between what is legal and what is allowed on wp.org and point out that other \"terms and licenses\" that restrict anything that the GPL allows DO NOT APPLY!<\/strong> outside of wp.org.\n\nI have seen this b4 in the WordPress space, a German theme seller for example I saw them going after someone in a blog post who copied their theme and in some disgusting way the misrepresented the GPL and used scare words and tried to make it seems its misconception that you can copy it. They did not straight forward say that all you have to do is keep the license with author in their and rename the thing!\n\nI saw I theme shop take \"GPL\" out of their FAQ because customers should not actually know the truth of it. Many people in this space do not actually believe in the GPL. They just go with it because PHP code has to be because it hooks into WP and CSS does not actually have to if I remember this correctly from the Thesis case. It's thankfully just such an established default that everything is 100% GPL in this space that all the selling platforms ... just require it. But if people could many-many people would actually NOT use it. You certainly sound like someone who does not actually believe in the GPL.","contentFiltered":" The beginning of your post was OK, but you quickly went downhill. If you have rules for wp.org that go beyond the GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613583557","hasChildren":false,"userLogin":"nico23","userNicename":"nico23"},{"type":"comment","id":"43995","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-nico23 odd alt depth-4","parentID":"43994","contentRaw":"And full disclosure: I sell \"licenses\" for sites and support. I do not go out of my way to explain in detail that people can use the plugin they auto update with the single site license on as many sites they want by just manually copying it there. (Well they would need to know how to flip a switch in the database as well, or clone the DB from an activated site). They essentially buy the auto updates and the support from me. Many of them probably would still but licenses for multiple sites for convenience or just because they think it's fair. Like 90% if they buy single lite licenses anyway. I just went over my own terms that I just copied from EDD (with permission) and the term license always relates to the key used for the auto updates. Like reselling the KEY is forbidden and \"sublicensing\" the KEY ... I do not know the legality of this and would not write it like this myself. But they do not say BS like that you can not resell the code itself. Of course, they also carefully avoid explaining how the GPL works, just \"It's licensed under GPL\". I will probably reword and add something at some point.\n\nOK \/rant\n\n(I split this into pieces because previously my comment was hold back and not approved later but then I saw other comments of me getting through)","contentFiltered":" And full disclosure: I sell \u201clicenses\u201d for sites and support. I do not go out of my way to explain in detail that people can use the pluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party<\/span><\/span><\/span> they auto update with the single site license on as many sites they want by just manually copying it there. (Well they would need to know how to flip a switch in the database as well, or clone the DB from an activated site). They essentially buy the auto updates and the support from me. Many of them probably would still but licenses for multiple sites for convenience or just because they think it\u2019s fair. Like 90% if they buy single lite licenses anyway. I just went over my own terms that I just copied from EDD (with permission) and the term license always relates to the key used for the auto updates. Like reselling the KEY is forbidden and \u201csublicensing\u201d the KEY \u2026 I do not know the legality of this and would not write it like this myself. But they do not say BS like that you can not resell the code itself. Of course, they also carefully avoid explaining how the GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613583647","hasChildren":false,"userLogin":"nico23","userNicename":"nico23"},{"type":"comment","id":"43996","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-ipstenu bypostauthor even depth-2","parentID":"43992","contentRaw":"You appear to be conflating a couple points in the post.\n\nThis will be the last time I repeat this: This is not about the GPL<\/em>. \n\n You appear to be conflating a couple points in the post.<\/p>\n This will be the last time I repeat this: This is not about the GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613584641","hasChildren":false,"userLogin":"Ipstenu","userNicename":"ipstenu"},{"type":"comment","id":"43997","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-aitpro odd alt depth-4","parentID":"43991","contentRaw":"I have an actual case, lawsuit that lasted 2 years, which I won for someone who claimed they were just \"forking\" my premium plugin. I didn't actually really \"win\" anything, but unfortunately the person who \"borrowed\" my premium plugin was pretty much ruined because the judge decided it was theft or software piracy or whatever term you would like to use. That person paid damages to me and the courts and a significant fine and was charged and convicted for a felony. So yeah even though my software works under the WP GPL license my premium plugin is not free for someone to do anything they want with it. ;)","contentFiltered":" I have an actual case, lawsuit that lasted 2 years, which I won for someone who claimed they were just \u201cforking\u201d my premium pluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party<\/span><\/span><\/span>. I didn\u2019t actually really \u201cwin\u201d anything, but unfortunately the person who \u201cborrowed\u201d my premium plugin was pretty much ruined because the judge decided it was theft or software piracy or whatever term you would like to use. That person paid damages to me and the courts and a significant fine and was charged and convicted for a felony. So yeah even though my software works under the WP GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613585074","hasChildren":false,"userLogin":"AITpro","userNicename":"aitpro"},{"type":"comment","id":"43998","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-aitpro even depth-5","parentID":"43997","contentRaw":"Another funny case is many years ago someone \"forked\" my free plugin and was selling it on Code Canyon. Needless to say that person was banned for life from Code Canyon. ;)","contentFiltered":" Another funny case is many years ago someone \u201cforked\u201d my free pluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party<\/span><\/span><\/span> and was selling it on Code Canyon. Needless to say that person was banned for life from Code Canyon. \ud83d\ude09<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-43998","unixtime":1613585815,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-43998&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":5,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" You appear to be conflating a couple of points in the post<\/p><\/blockquote>\n Well YOU mixed it all together without properly distinguishing the two things and you for sure make it is sound like you misunderstand the GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613586028","hasChildren":false,"userLogin":"nico23","userNicename":"nico23"},{"type":"comment","id":"44000","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-nico23 even depth-4","parentID":"43999","contentRaw":"I can not edit or delete my own comments here? ...","contentFiltered":" I can not edit or delete my own comments here? \u2026<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2021\/02\/16\/reminder-forked-premium-plugins-are-not-permitted\/#comment-44000","unixtime":1613586135,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2021%2F02%2F16%2Freminder-forked-premium-plugins-are-not-permitted%2F%23comment-44000&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":4,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Pardon me, I should clarify, \u201cFor the purposes of THIS SPECIFIC discussion, it does not matter how anyone interprets or understands the GPLGPL<\/span> GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1613586849","hasChildren":false,"userLogin":"Ipstenu","userNicename":"ipstenu"},{"type":"comment","id":"44002","postID":"1677","postTitleRaw":"Reminder: Forked Premium Plugins Are Not Permitted","cssClasses":"comment byuser comment-author-nico23 even depth-4","parentID":"43985","contentRaw":"Thank god someone else who thinks and is able to put it more calmly and nicer than I right now.\n\nBut Thank god someone else who thinks and is able to put it more calmly and nicer than I right now.<\/p>\n But <\/p>\n problematic<\/p><\/blockquote>\n...violated the license (which may say things like you cannot resell it)<\/blockquote>\n\nIs a \"cannot resell\" clause even possible with GPL?","contentFiltered":"
Taking someone\u2019s pay-for code and re-releasing it as free-of-charge is considered to be piracy<\/blockquote>\n\nThis just sounds like a Red Hat Enterprise Linux\/CentOS situation. That's not considered piracy.","contentFiltered":"
\u201cstole\u201d (no one lost anything they were entitled to)<\/blockquote>\n\nI would disagree. If you sell a thing and someone takes it and gives it away, without your permission, then the potential purchases (i.e. the money) was stolen from you. Your opportunity to make a living is being actively harmed. That is a net-negative to the community.\n\n
Whomever supplies a plugin CAN\u2019T add additional terms under WordPress\u2019s own choice of license....<\/blockquote>\n\nAssuming that those plugins are GPL to begin with (many are not) I repeat: Our guidelines are considered above and beyond<\/em> the GPL. <\/strong>\n\nI did not claim (nor will I) that it's a GPL issue. I said it's a beyond-GPL restriction here.","contentFiltered":"
or politely put \u201cforked\u201d \u2013 from someone else\u2019s code, they *are* violating the author\u2019s copyright.<\/blockquote>\nIf they keep the author, license and copyright (and only add their own) it's not piracy. Calling LEGAL copying of code piracy is an oxymoron.\n\n
As soon as the original commits are \u201cdestroyed\u201d by committing the code under your own name in another type of repo, you violate copyright though.<\/blockquote>\n\nWhat are you saying? That you need to have the need of the original commit history intact to have a valid fork? If so you are wrong. All you need it keep the copyright, original author(s) and you can commit it in a new repo however you like. If there is a trademark involved then you need to rename it. You should like you have no clue. Even if you \"destroy\" as you put it by committing in under and a new repo you do NOT violate the copyright.\n\nNever mind if I just misunderstood you. But you sound like you do not understand the GPL either.","contentFiltered":"
it\u2019s considered to be piracy and is not welcome here.<\/blockquote>\nBy whom? You? Mullenweg? It's fine if you do not want it here but do not call it piracy and do not make false claims like you can add \"Terms and Licenses\" on top of the GPL and claim \"illegal to sell\".\n\n
It certainly could be, <\/blockquote>\nNOT for WP stuff that is pretty much all over the place 100% GPL, even the premium stuff.\n\nYou keep conflating things like people forking legally and people removing the copyright on purpose. It makes no sense to do so and only yourself up for legal battles if all you have to do it keep the author+license on place and rename it if a trademark is involved. \n\nI like to hear about some actual cases and how often literally that happens that people remove the license and claim a plugin their own. These are probably people who also do not understand the GPL.","contentFiltered":"
Taking someone\u2019s pay-for code and re-releasing it as free-of-charge is considered to be piracy<\/blockquote>\n\nCalling any<\/em> GPL code copying piracy is the one of the most disgusting oxymorons I ever heard. Coin your own term, call it something else, but it's not piracy!<\/strong>\n\n
The only exception to this (besides it being your own plugin) is if you have made a significant fork, properly credited in the readme and inline code, and everything is 100% GPL compatible, including the terms from where you bought the plugin. If you pirated a plugin, or if you violated the license (which may say things like you cannot resell it), then we will not host the code.<\/blockquote>\n\nWhat is a \"significant fork\"? You contradict yourself here. You say in the TLTR; that you will not host forks of premium plugins, then you say all you need to do it credit them in the readme and show that you did some work on it, I guess that is what you mean with \"significant\". How is that determined? Again you speak of piracy here that makes absolutely no sense. It' hard to believe that you do not understand the GPL, so why are you acting like you can put a bu1lsh1t license or terms on top of the GPL?
100% GPL compatible, including the terms from where you bought the plugin.<\/blockquote>. You mention this together like that is something legitimate to do. The facts are (and you know it):","contentFiltered":"
If you have rules for wp.org that go beyond the GPL that is perfectly fine but do not misrepresent the GPL and tell the truth about it. <\/blockquote>\n\nWe did not. You misunderstood, and I do I understand why people like you read it that way. At this point, though, you can keep on ranting or you can stop and think about the intent here.\n\nSee, it doesn't matter how I, or you, understand the GPL, when I tell you that to be hosted here<\/em> on WordPress.org, you cannot take someone's premium code and present it as your own work. That's just me reminding<\/em> you of an existing guideline.\n\nThere isn't a 'better' word to use, as far as I'm aware, but I'm happy if someone can figure out how to say \"You took someone else's code and lied to everyone, presenting it as your own original creation, with no added or removed features.\" without saying or even implying 'theft.' \n\nAlso, you asked why would I possibly mention terms and GPL, when one could conflict with another? Specifically because<\/em> people do that with a rather disturbing regularity. So I figured I'd cover my bases. Sorry that it confused you.","contentFiltered":"
You appear to be conflating a couple of points in the post<\/blockquote>\n\nWell YOU mixed it all together without properly distinguishing the two things and you for sure make it is sound like you misunderstand the GPL.\n\nSo what you call piracy is removing the copyright, org author and license on purpose? And only that? What do you call a fork that does absolutely nothing by add a new author (not removing the org author) and renaming it? Is that piracy to you as well?\n\nAnyway like I said you go on, and you make it sounds like it's legitimate to claim \"other Terms or other licenses\". You clearly act like you think this is legit. It's not and that is not my Opinion that is fact!\n\n
See, it doesn\u2019t matter how I, or you, understand the GPL<\/blockquote>\n\nI totally disagree and am disappoint to see you and other people not understanding it. Especially people in positions like you.\n\n
when I tell you that to be hosted here on WordPress.org, you cannot take someone\u2019s premium code and present it as your own work. That\u2019s just me reminding you of an existing guideline.<\/blockquote>\n\nThat is all fine and great, no complaints there from me. It's just the part where you act like people can claim to additional restrictions apply to their software and that you respect these illegitimate<\/strong> conditions. Just say you do not like it morally or whatever, that is all fine, it's just the wording is so horrible that you make me think you actually believe that people can do that. And that is why it does<\/strong> matter what you personally think about it.","contentFiltered":"
It\u2019s just the part where you act like people can claim to additional restrictions apply to their software and that you respect these illegitimate conditions. <\/blockquote>\n\nAh, thank you for explaining what confused you!\n\nThe issue is that when you mess up the GPL with illegitimate conditions, you may invalidate the license, which means there's a high probability your code is not GPL compatible anymore, which means we can't host your code anyway. But for the layman, it's easier to say \"Even if the license says GPL, if the terms of your purchase say you cannot re-sell or give it away, then you cannot host that code here.\"\n\nIn addition? We don't want to steal money from you.\n\nSeparate, but intertwined.","contentFiltered":"
problematic<\/blockquote> isn't really cutting it for me. So many people in this space actually do not understand or hate the GPL. If the opportunity presented itself lots of companies would go legally after every single person who dared to copy their GPL software in a heartbeat.\n\nPosts like this would be a great opportunity for Mika to actually explain the GPL to people and point out the exact and legal differences between wp.org policies and GPL in the wild, on people own sites.\n\n
Whomever supplies a plugin CAN\u2019T add additional terms under WordPress\u2019s own choice of license. <\/blockquote>\n\nExactly this! And Mika makes it sound like the exact opposite here. She makes it sound additional terms like \"you are not allowed to sell\" are legit. She fails to point out that are NOT<\/strong> legit but that WordPress.org chooses<\/strong> to have terms that kind of go along those lines because of some moral code or whatever. I think its perfectly fine just not how<\/em> its justified here.","contentFiltered":"