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: All representatives of 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 are required to comply with the Community Code of Conduct.
One of the longstanding open tickets for the Plugin Guidelines has been adding in the Community Code of Conduct.
With the announcement of the Incident Team, we have updated the guidelines to indicate that all representatives of a plugin must comply with the Community Code of Conduct.
The updates can be found in the “Developer Expectations” (where we list out the guidelines/CoCs you must comply with) and in Guideline #9 (Developers and their plugins must not do anything illegal, dishonest, or morally offensive.)
Effectively? Yes, you actually do have to follow the Community Code of Conduct if you want to be part of the community.
This shouldn’t be a surprise to anyone.
tl;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: Using someone else’s trademarked logo in 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 icons or banners is a trademark violation, and they have the right to have us remove your plugin at any time.
We’ve posted about this before, and it’s apparently time for a reminder. Logos for brands are generally trademarked. Those logos cannot be used in your plugins banners or icons unless you have their express permission.
Trademark infringement is the unauthorized use of someone else’s registered trademark. This means you are using their logos without permission. When we talk about misuse, it’s more clear to think about it in terms of physical products. Lets say you make electronic gizmos and they happen to work with MacOS. If you put Apple’s logo on your products, you would be infringing on their trademark. Basically you’re misrepresenting yourself in a way that implies or suggests that the trademark owner approves of your work when this is not true.
If you got an email from us (either a warning or a closure notice) about this sort of matter, please address it promptly. Check your banners and icons, and your display names, to make sure you aren’t in violation. Remove all trademarked logos from your plugin banners and icons (yes, even social media ones), and make sure it’s clear that your plugin is not an official plugin (unless it is, and then you don’t have to worry).
Some quick questions:
Trademark owners who do not protect their trademark usage end up being unable to enforce it legally later on. So it’s in their best interests to monitor the use and prevent misuse. Also, customers often get confused about the origin of the plugins, and will complain to the wrong people if there’s an issue. Finally, you are essentially profiting from the goodwill that the trademark owner has generated.
A lot of people, actually. A high number of people complain to companies and the companies come back to us and say we’re encouraging the behavior which causes confusion with users and a loss of trust in the trademark owners. After all, if your unofficial plugin breaks someone’s site, and they blame the trademark owner? Well that wasn’t fair at all.
They aren’t. They’re just living on borrowed time, as the saying goes.
We have getting close to 100k plugins. They are all monitored by humans (not automated for this one yet) and a human has to check if you had permission or not, if you’ve been warned or not, if your plugin merits a grace period or not, and if the trademark owner has officially demanded we close your plugin immediately. Plus a large number of people argue about this, which eats up time. We do things in batches to try and stay sane.
Also … we strongly recommend you never use that excuse. It makes you sound like ‘sour grapes’ or childish to argue that someone else didn’t get caught yet, so you should be allowed to keep breaking the rules. That just makes this process take longer for everyone.
Unless it’s your trademark, we generally don’t do anything right away because, again, we have close to 100,000 plugins. The number of violations is high, and in order not to ‘play favorites’ we do them in the order we’ve got them. We don’t bump people higher (or lower) on the list just because someone complained or is our friend. That would be terribly unfair!
If it was your trademark, we probably did bump them to the top of the list. We do try to get the developers to fix things before we close (especially for larger plugins that would have a massive negative impact on the community), but this isn’t always possible.
No. Besides the fact that ‘fair use’ doesn’t apply to trademarks, it’s a matter of how you’re using it. Social media companies usually give permission to use their logos on your website as a direct link to your presence on their ecosystem. So a bird links you to Twitter. However. That is not the same as using a logo for advertising which is what many of them consider banners and icons to be. Their argument is that 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/ is not your site. We’ve argued about this, but some companies have slapped us with legal threats so there we are.
Some trademark owners demand we prevent that too, some don’t. I wish we had a clearer answer here, but just to grab an example, there is a certain social media company who doesn’t want to see you use the logos in screenshots. Meanwhile, there are other credit card companies who don’t mind. Keeping track of those is incredibly hard! We recommend you not use them in screenshots.
Then you’re probably going to get a legal demand from the owner to stop because you broke their usage guidelines for the logo. We should note here, when you intentionally try to get around trademark law, you are effectively confessing guilt. You know what you’re supposed to be doing and you’re actively trying to get away with something? The trademark lawyers will be able to take you down in seconds.
First and foremost, the directory isn’t for promoting anything, it’s for listing. If you’re doing all this to basically be a big “Click Here!” method, you’re going about it the wrong way.
Now if you’re really asking “How can I improve my usage by getting people to click on my plugin?” then you start by making a great banner that is memorable.
Stop treating a banner or an icon as a billboard. You don’t need to show off what your plugin can do, you need to be memorable and noticeable. The best banners are the ones that stick in people’s minds, and the odds are not a single person remembers “Oh you’re the one with the logos in this order…”
But no, you don’t need all the examples of the possible social media uses on your plugin banner.
In general, you can use “For [Trademark]” in your display name. There are some vendors who are particular and won’t even let you do that. We do our best to try and warn you ahead of time, but sometimes vendors change things on us without notification. Most are pretty cool about working out a plan so we don’t have to close plugins, some are not. I wish I had a better answer there.
Over the years we’ve gone from always showing all plugins in searches to devaluing plugins that aren’t updated in a time span to devaluing them if they’re not compatible with the latest few releases of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. All of this is done to improve the user experience and to ensure they only find plugins that are actively maintained and compatible with the versions of WordPress they use.
As part of this, when 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 is closed we currently require the ‘tested up to’ value to be, at least, the latest stable version of WordPress core. We have updated our emails for closures and re-scans to reiterate that, but it’s for a slightly different reason than helping users.
We want to help you developers. If no one can find your plugin, because it’s not compatible with (say) WP 5.5, then no one uses your plugin. Presumably, if your code is hosted here, you want people to use it. To help you and ensure your plugins can be found and used, we are requiring you update that, should we have any reason to close your plugin.
Just like you have to bump the plugin version so people get notified of updates, you need to make sure that “tested up to” value is current 🙂
So! Please keep that up to date! It’ll help people find your plugin, give them confidence in your work, and help make you more successful! Wins all around 🙂
Many of you have received an email from us regarding 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 closures for trademark violations. These emails were absolutely not made in error.
Due to recent demands by trademark owners, we will now be more strictly enforcing trademark abuse when it comes to plugins. While it should be sufficient to tell you “Don’t abuse someone’s trademarks.” the reality is that those things are complex and confusing.
We will have altered our system to prevent the submission of those plugins that violate trademarks. This is not something we do lightly, however we have been compelled to close a great many plugins recently. It’s more efficient to prevent potential abuse than to clean it up after the fact.
Trademarks apply to the following aspects of your plugin:
We do our best to take care of the first one – the slug – when you submit your plugin. Plugins approved pre 2015 with trademarks in the URL are ‘grandfathered’ in and permitted to remain. All plugins approved after 2015 are required to meet this restriction. All plugins, no matter when they were approved, must comply with trademark usage in display names and images.
We also keep our eye on similar names. There’s a concept known as brand confusion, so naming your company or plugin similar to another company (like Facerange, say) you can still be legally compelled to change the name. This is why, for example, you cannot use ‘pagespeed’ in your URL for a site optimization tool, even though Google’s only trademark is on ‘page speed’ (two words). The name is similar enough that we have been required to close plugins.
In addition to the above, many brands have an above-and-beyond requirement. You must also avoid representing the brand in a way that:
Also many have statements like this when regarding applications specifically:
This is where it all gets crazy weird. But an example would be the brand Facerange. With the above restrictions, naming your plugin (which is an application) “WordRange” or “FacePress” and having it be a plugin to work with Facerange would be a violation of their terms.
It all comes back to making it painfully clear that you and your work have NO relationship to their products. Some allow you to use their product name wherever you want, and some won’t permit it at all. When in doubt, the best course of action is to assume you don’t have permission and not to use it.
Can I use ‘for BRAND’ in my plugin display name?
Sometimes. It depends on the brand. We don’t have a complete list, which makes this very complex. It’s important to pay attention to the rules for brand usage and application uses. Some brands have separate rules. In general, if they’ve trademarked their wordmark then no, you cannot use it for an application. And yes, a plugin is an application.
What’s a wordmark?
That’s the name. So Facerange’s wordmark would be “FACERANGE.”
I have permission from PayBuddy to use their wordmark/logo, is that okay?
We’d rather you not use it on your PLUGIN pages. It’s impossible for us to verify, and many agreements with brand owners are rescinded. Brand your webpage all you want, but leave their official logos and word marks off your plugin.
A brand contacted me directly and asked me to change things. Is that a real demand?
More than likely they are. They’ll usually include links and directions and contact information. Use that and comply with them, because if you don’t, they’ll come to us.
What about existing violations?
We’re handling them in batches. You don’t need to report them to us.
But if you haven’t closed them, why are you closing my plugin?
Because there are thousands of plugins and we do them in small batches for sanity. Also brand owners sometimes give us a priority list, and you just happened to be higher than someone else.
Don’t they get an SEO boost?
No. Write a better readme that uses the brands properly and contextually, and you’ll be fine.
Someone’s infringing on MY brand, what do I do?
Contact them first. Ask them to stop (nicely please). Link them to your brand documentation. If they ignore you, email us the same. We’ll close the plugin until they fix it.
We recommend you BE CLEAR about what you require. Remember, most people aren’t familiar with trademark laws and their intricacies, so it’s very easy for them to get confused.
This post is a proposal of changes to be made to 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 Guidelines.
The majority of changes are intended to address significant issues faced by ESL (English as a Second Language) developers. This proposal also contains a significant rewrite to the lamented 11th Guideline (hijacking the admin dashboard).
This proposal will remain open until after 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. EU 2019, at which point it will be closed and either re-proposed (if there are significant changes), implemented, or scrapped.
The rest of this post will go over an overview of intent, the proposed changes (with summary), and information as to how to contribute. All community members are welcome to participate.
Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1557855283","hasChildren":false,"userLogin":"pputzer","userNicename":"pputzer"},{"type":"comment","id":"43698","postID":"1474","postTitleRaw":"Proposal to Modify Plugin Guidelines","cssClasses":"comment byuser comment-author-swissspidy even depth-2","parentID":"43697","contentRaw":"English as a second language","contentFiltered":"English as a second language<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43698","unixtime":1557855306,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43698&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Please exclude Notices that have something to do with harming website if ignored. For instance upgrading ACF (Advanced Custom Fields) to major version and updating database. Those Notices have to be persistent unless Owner updated database to implement new ACF changes. Thanks.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43699","unixtime":1557855391,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43699&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Thanks.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43700","unixtime":1557855397,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43700&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":3,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" I definitely think making #11 more clear in respect to upsells for premium versions and addons for developers who are using freemium model would be very helpful.<\/p>\n I myself had a situation in which i was not able to easily interpret #11 in relation to 2 conjoined projects which i am responsible for, and had to contact the repo to ask about them. With these clarifications, freemium devs will avoid this conundrum. And it could help such projects better finance themselves and gain future stability.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43701","unixtime":1557855620,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43701&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Do you have a suggestion for better wording? I agree it could be better, but there\u2019s a limit to what\u2019s obvious to me and not to everyone else \ud83d\ude42<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43702","unixtime":1557856827,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43702&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" You mean ACF tells you to update the DB after you upgrade to the new version? That sounds like they\u2019re trying to prevent harm so it would be a reasonable alert. Keeping your DB non-updated means it\u2019s not in sync with the new version, which could have unforeseen complications.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43703","unixtime":1557856899,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43703&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Updated post to add that, thank you Untrash<\/a><\/li><\/ul><\/nav>","mentions":["swissspidy"],"mentionContext":"","commentCreated":"1557857018","hasChildren":false,"userLogin":"Ipstenu","userNicename":"ipstenu"},{"type":"comment","id":"43705","postID":"1474","postTitleRaw":"Proposal to Modify Plugin Guidelines","cssClasses":"comment byuser comment-author-davidanderson odd alt depth-2","parentID":"43701","contentRaw":"I'm somewhat nervous (as a plugin developer) of the whole concept of the guidelines starting to become detailed and prescriptive about things like that. Though in one sense, it's a natural extension, and there are hundreds of grey areas, in another sense, it seems like the guidelines starting to become very opinionated (about things that aren't clear-cut harm to the user, e.g. lack of privacy, mis-use of data, mis-use of resources). And the precedent that the guidelines can be very opinionated is potentially dangerous new ground. In my view, it'd be better, in things that go beyond user harm (and after allowing reasonable ground for grey areas) to allow users to decide. If they think that a plugin had gone too far, let them unleash endless 1-star reviews. But banning is too much.","contentFiltered":" I\u2019m somewhat nervous (as 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> developer) of the whole concept of the guidelines starting to become detailed and prescriptive about things like that. Though in one sense, it\u2019s a natural extension, and there are hundreds of grey areas, in another sense, it seems like the guidelines starting to become very opinionated (about things that aren\u2019t clear-cut harm to the user, e.g. lack of privacy, mis-use of data, mis-use of resources). And the precedent that the guidelines can be very opinionated is potentially dangerous new ground. In my view, it\u2019d be better, in things that go beyond user harm (and after allowing reasonable ground for grey areas) to allow users to decide. If they think that a plugin had gone too far, let them unleash endless 1-star reviews. But banning is too much.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43705","unixtime":1557857281,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43705&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Is \u201clook like a Las Vegas roadside\u201d meaningful to those who haven\u2019t seen what a LV roadside look like?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43706","unixtime":1557857340,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43706&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Yes, that. ACF is only example. WooCommerce does this often too.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43707","unixtime":1557857883,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43707&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":3,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" No, which is why it\u2019s not in the actual guideline, and just be trying to explain what I mean. Would \u201c1990 Geocities Site\u201d be any more helpful?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43708","unixtime":1557857961,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43708&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" In that case, the message is important, and ignoring it could cause your site to break. So \u2026 as annoying as it is, you should probably make a backup and update the DB \ud83d\ude42<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43709","unixtime":1557858000,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43709&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":4,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" I am asking to leave it permanent unless DB is updated, not demand \u201cClose (forever)\u201d option. \ud83d\ude42<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43710","unixtime":1557858407,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43710&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":5,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" I am asking to leave it permanent unless DB is updated, not demand \u201cClose (forever)\u201d option. <\/p><\/blockquote>\n You can.<\/p>\n This may be done either by a user\u2019s direct action (clicking a \u2018dismiss\u2019 button) or by self-removal when an issue is resolved<\/strong>. <\/p><\/blockquote>\n Bolded the important part. If the alert removes itself when you do the needful, then it\u2019s fine.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43711","unixtime":1557858784,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43711&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":4,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Having the notices \u201cpermanently dismissable\u201d implies storing more data, per user? Is that considered personally identifiable for GDPR?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43712","unixtime":1557861840,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43712&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Not at all. The data is all included in 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>, no phoning home allowed, remember? So it\u2019s like any other message in WP that you dismiss. Those aren\u2019t transmitted anywhere, so there\u2019s no data being sent, so no GDPR issues.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43713","unixtime":1557861952,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43713&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" all users the freedom and ability to maintain agency<\/strong> over their own website.<\/p><\/blockquote>\n I haven\u2019t heard agency being used in this context before \u2013 is it synonym of control?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43714","unixtime":1557862829,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43714&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Probably not. Most of the current users of the web weren\u2019t necessarily have been alive in 1990. But definitely missed the glorious 90s phase of the net.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43715","unixtime":1557863346,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43715&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":3,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Yes. It goes wider, for example it needs to mean that someone is in control, and feels in control. This is a good in depth article on it: Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1557863495","hasChildren":false,"userLogin":"javorszky","userNicename":"javorszky"},{"type":"comment","id":"43717","postID":"1474","postTitleRaw":"Proposal to Modify Plugin Guidelines","cssClasses":"comment byuser comment-author-ipstenu bypostauthor odd alt depth-4","parentID":"43715","contentRaw":"Stop making me feel old! \ud83d\ude02\n\nFor a more practical (and easily searchable) example, look up \"Times Square NYC\" and see how many electronic billboards you see. It's a horrifying experience IMO :)","contentFiltered":" Stop making me feel old! \ud83d\ude02<\/p>\n For a more practical (and easily searchable) example, look up \u201cTimes Square NYC\u201d and see how many electronic billboards you see. It\u2019s a horrifying experience IMO \ud83d\ude42<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43717","unixtime":1557864733,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43717&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":4,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" That is indeed the definition. Thank you Untrash<\/a><\/li><\/ul><\/nav>","mentions":["javorszky"],"mentionContext":"","commentCreated":"1557864791","hasChildren":false,"userLogin":"Ipstenu","userNicename":"ipstenu"},{"type":"comment","id":"43719","postID":"1474","postTitleRaw":"Proposal to Modify Plugin Guidelines","cssClasses":"comment byuser comment-author-javorszky odd alt depth-4","parentID":"43718","contentRaw":"with a +z ;)","contentFiltered":" with a +z \ud83d\ude09<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43719","unixtime":1557865192,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43719&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":4,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" I don\u2019t think this is \u201cnew ground\u201d. 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> repository on WordPress.orgWordPress.org<\/span> 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. Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1557866376","hasChildren":false,"userLogin":"diddledani","userNicename":"diddledani"},{"type":"comment","id":"43721","postID":"1474","postTitleRaw":"Proposal to Modify Plugin Guidelines","cssClasses":"comment byuser comment-author-alexdenning odd alt thread-even depth-1","parentID":"0","contentRaw":"Would these two points on #11 open a possible loophole?\n\n- \"Included advertisements for add-ons, upsells, or services must directly relate to the plugin and\/or developer.\"\n- \"Advertisements for unrelated products (such as a favored forms plugin when it has no relationship to the active plugin)\"\n\nA single developer could be involved in multiple plugins which are unrelated; would the first point let them include advertisements even if these other plugins are unrelated, or is the intent that this is okay?","contentFiltered":" Would these two points on #11 open a possible loophole?<\/p>\n A single developer could be involved in multiple plugins which are unrelated; would the first point let them include advertisements even if these other plugins are unrelated, or is the intent that this is okay?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43721","unixtime":1557908568,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43721&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Not sure if \u2018opening\u2019 a possible loophole is the correct terminology, since currently both are done and run pretty rampant.<\/p>\n But yeah, I\u2019d also like clarification whether this behavior would be allowed under the new guidelines.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43722","unixtime":1557913558,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43722&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" I think you\u2019ve overlooked the nuance of what I wrote.<\/p>\n There\u2019s a balance, a trade-off. There needs to be a lot of care in changing that trade-off over time. If developers are enticed in under one relationship (a balanced relationship), and then the relationship changes (we don\u2019t care about being friendly to developers), then there will be \u201cbait and switch\u201d concerns there. As I wrote, in one sense these changes can be justified as a natural extension \u2013 but in my view, they are a lot more detailed and prescriptive than previously, and it is a notable change.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43723","unixtime":1557921550,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43723&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":4,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Just wanted to first off thank Untrash<\/a><\/li><\/ul><\/nav>","mentions":["ipstenu"],"mentionContext":"","commentCreated":"1557930655","hasChildren":false,"userLogin":"justlevine","userNicename":"justlevine"},{"type":"comment","id":"43725","postID":"1474","postTitleRaw":"Proposal to Modify Plugin Guidelines","cssClasses":"comment byuser comment-author-ipstenu bypostauthor odd alt depth-2","parentID":"43721","contentRaw":" would the first point let them include advertisements even if these other plugins are unrelated<\/p><\/blockquote>\n Yes, but within the other restrictions. That is, if I make a Rickroll 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 a Ban IP plugin, I can advertise them on each other, but only one at a time etc etc. Yes, I could have a rotating check and just cycle through all 40 plugins I work on. And yes, I\u2019m sure someone will do exactly that. It would have created an unfair situation to say they could only advertise related plugins, if the developer works on disparate products. They\u2019d never be able to cross link anything, while the BooCommerce only author can link everything \ud83d\ude15<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43725","unixtime":1557933000,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43725&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" You know it\u2019s funny people always point at the larger plugins. It\u2019s actually the mid-sized ones who make me want to drink.<\/p>\n Limiting by relevance is something I like in theory but couldn\u2019t think of how to practically monitor and enforce it in reality. It would be easily missed and thus easily abused, which IMO is worse than no guideline because then it\u2019s up to the review team to choose where to enforce it. A solid line of \u201c1\u201d is easily determined and enforced, without cause for people to claim favouritism.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43726","unixtime":1557933147,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43726&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" Both valid points \ud83d\ude0e<\/p>\n Just to clarifyz does that mean the definition of \u2018shared\u2019 pages applies to any page created by someone other than 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> author or that only coreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> dashboard pages would be protected from \u2018abuse\u2019? While there\u2019s pros and cons for both (there are legitimate, non \u2018promotional\u2019 notifications that my hypothetical WC extension should be displaying to the user vs. my hypothetical WC plugin spamming every non-Core page), either way id suggest this proposal clarify the definition.<\/p>\n Re enforcement of relevance limitations: *But* I obviously have no idea regarding the real-world workflow let alone cognitive load of reviewing and approving plugins, so my imagined implementation ain\u2019t worth :expletive: \ud83e\udd37\u200d\u2642\ufe0f.<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43727","unixtime":1557935157,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43727&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":3,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":" How about requiring<\/strong> the use of dashicons or own icon fonts for the menu? Very often 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> developers just test with the default color scheme and their own images are missing the necessary color contrast for different color schemes (blue icon on blue color, etc.) Just to clarifyz does that mean the definition of \u2018shared\u2019 pages applies to any page created by someone other than 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> author or that only coreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> dashboard pages would be protected from \u2018abuse\u2019? <\/p><\/blockquote>\n If your plugin hooksHooks<\/span> In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.<\/span><\/span><\/span> into someone else\u2019s page (say a WooCommerce add-on using a default Woo page for settings) then that would be a SHARED page to you. That would be the author\u2019s page to Woo, however. It\u2019s a little hair splitting.<\/p>\n Any advice on how to rephrase it?<\/p>\n","permalink":"https:\/\/make.wordpress.org\/plugins\/2019\/05\/14\/proposal-to-modify-plugin-guidelines\/#comment-43729","unixtime":1557940367,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fplugins%2F2019%2F05%2F14%2Fproposal-to-modify-plugin-guidelines%2F%23comment-43729&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":4,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"I am asking to leave it permanent unless DB is updated, not demand \u201cClose (forever)\u201d option. <\/blockquote>\n\nYou can.\n\n
This may be done either by a user's direct action (clicking a 'dismiss' button) or by self-removal when an issue is resolved<\/strong>. <\/blockquote>\n\nBolded the important part. If the alert removes itself when you do the needful, then it's fine.","contentFiltered":"
all users the freedom and ability to maintain agency<\/strong> over their own website.<\/blockquote>\nI haven't heard agency being used in this context before - is it synonym of control?","contentFiltered":"
\n
would the first point let them include advertisements even if these other plugins are unrelated<\/blockquote>\n\nYes, but within the other restrictions. That is, if I make a Rickroll plugin and a Ban IP plugin, I can advertise them on each other, but only one at a time etc etc. Yes, I could have a rotating check and just cycle through all 40 plugins I work on. And yes, I\u2019m sure someone will do exactly that. It would have created an unfair situation to say they could only advertise related plugins, if the developer works on disparate products. They\u2019d never be able to cross link anything, while the BooCommerce only author can link everything \ud83d\ude15","contentFiltered":"
\nIn my mind it\u2019s a cursory glance at the conditionals with an actual review\/request for developer justification if users report the violation.<\/p>\n
\nI\u2019ve blogged about this for years: Untrash<\/a><\/li><\/ul><\/nav>","mentions":[],"mentionContext":"","commentCreated":"1557937049","hasChildren":false,"userLogin":"zodiac1978","userNicename":"zodiac1978"},{"type":"comment","id":"43729","postID":"1474","postTitleRaw":"Proposal to Modify Plugin Guidelines","cssClasses":"comment byuser comment-author-ipstenu bypostauthor odd alt depth-4","parentID":"43727","contentRaw":"Just to clarifyz does that mean the definition of \u2018shared\u2019 pages applies to any page created by someone other than the plugin author or that only core dashboard pages would be protected from \u2018abuse\u2019? <\/blockquote>\n\nIf your plugin hooks into someone else's page (say a WooCommerce add-on using a default Woo page for settings) then that would be a SHARED page to you. That would be the author's page to Woo, however. It's a little hair splitting.\n\nAny advice on how to rephrase it?","contentFiltered":"