导航|地址|刷新
Plugin Developer FAQ – Plugin Handbook |…

Skip to content

WordPress.org

Showcase

Plugins

Themes

Hosting

News

Resources
Learn WordPress

Documentation

Education

Forums

Developers

Blocks

Patterns

Photos

Openverse ↗︎

WordPress.tv ↗︎

About
About WordPress

Make WordPress

Events

Five for the Future

Enterprise

Gutenberg ↗︎

Job Board ↗︎

Swag Store ↗︎

Get WordPress

Search in WordPress.org

Get WordPress

WordPress.org

WordPress Developer Resources

Plugin Developer FAQ

Developer Blog

Code Reference

WP-CLI Commands

Developer Blog

Code Reference

WP-CLI Commands

Home Plugin Handbook The WordPress.org Plugin DirectoryPlugin Developer FAQ

Search

Plugin Developer FAQ

In this article
Table of Contents

The Plugins Team
How do I contact the Plugins team?

Can I join the team?

Submissions and Reviews
Where do I submit my plugin?

What if my plugin is over 10 megs?

What happens after submission?

What will my plugin permalink (slug) be?

Why did I get a different slug than I was told?

Why is my submission failing saying my plugin name already exists?

Why am I getting an error that says I cannot begin my plugin name with a term?

Why am I getting an error that says I cannot use a term entirely in my plugin name?

How do I submit an official plugin?

What if I submitted the plugin with the wrong user ID?

How long does it take to get a plugin approved?

I sent in the fixes but no one replied. How long should I wait?

If my plugin has a problem, how long do I have to fix it?

Why was my plugin rejected after three months?

I finally fixed my plugin. Should I resubmit?

How many plugins can I submit for review at a time?

Why can’t I submit more than one plugin at a time?

Can I submit multiple plugins with multiple accounts?

I need my plugin approved by a specific date, what should I do?

Are there specific things that I should avoid doing?

Are there plugins you don’t accept?

I want to redo, upgrade, or rebrand my existing plugin. I just submit again, right?

I made a mistake with my submission. How can I fix it?

Are there things I can’t do in a plugin name?

Using The SVN Repository
Where do I put my files?

Can I put my files in a subdirectory of trunk/?

How should I name my tags (a.k.a. releases)?

How many old releases should I keep in SVN?

Can I include SVN externals in my plugin?

Can I put zips and other compressed files in my plugin?

Can I include minified JS?

Your WordPress.Org Page
When does my plugin go ‘live’?

Where does the WordPress.org Plugin Directory get its data?

Can I specify what version of my plugin the WordPress.org Plugin Directory should use?

What version of WordPress should the “Tested Up To” value be?

Do I need to release a new version of my plugin every time I update the readme?

Do I need to release a new version of my plugin every time I update the code?

What should be in my changelog?

How many versions should I keep in my changelog?

How do I include videos on plugin description pages?

Why does my plugin say it’s not been tested with the most recent WordPress versions?

How long does it take for the Plugin Directory to reflect my changes?

How do I make one of those cool banners for my plugin page?

How do I make a plugin icon?

Can I use official logos in my plugin banner/icons?

How many tags can I use in my readme?

Plugin Names
Can I change my plugin’s name after it’s approved?

Why can’t I use someone’s trademark/brand as my plugin name?

Can a company give me permission to use their trademark in my permalink?

Can I change my plugin’s URL/slug?

How do I change my plugin’s display name?

Can I make my display name anything?

Can I use WordPress or Plugin in my display name?

Should I use the trademark or registered symbol in my plugin name?

Search
How long will it take for my plugin to show up in search?

How do I rank higher?

What’s weighted more, my URL or my display name?

The Support Forums
How do I get notified for forums posts?

How do I get notified for all my plugins?

How do I give a support account access to my plugin?

Will you delete bad reviews or comments on my plugin?

What is ‘Sockpuppeting’?

Closed Plugins
How do I close my plugin?

What if I accidentally closed my plugin?

Why won’t it let me close my own plugin?

Can I temporarily close my plugin?

What happens when a plugin is closed?

Why was my plugin closed?

Why was someone else’s plugin closed?

Can I get someone else’s plugin closed?

Someone posted a copy of my plugin! What do I do?

What do I do if someone copied some of my code and didn’t credit me?

Will you close another plugin for violating a brand/trademark?

How can I send a security report?

Do you provide bounties for finding bugs in a plugin?

Do you help file or provide CVEs?

My plugin was closed, can I reopen it?

Why was my plugin closed when it was my employee/co-worker who violated guidelines?

All my plugins were closed! How can I get them back?

I just got a final warning. What do I do?

Plugin Ownership
How do I give someone else access to my plugin?

What happens to a plugin if the plugin owner gets blocked?

How do I remove someone’s access from my plugin?

How do I change the plugin owner?

I tried to transfer my plugin but it says I can’t. Why not?

How can I take over an abandoned plugin?

Are these offers to buy my plugin legit?

What happens when a plugin developer dies?

↑ Back to top

There are lot of ins and outs to hosting WordPress plugins. Please take a minute to see if your question is answered here before reaching out for assistance.

Last Updated: 30 June 2026

The Plugins Team

How do I contact the Plugins team?

You can contact us by email at plugins@wordpress.org – we reply to all emails within 7 business days.

If you’re contacting us about an existing case we’re already handling with you by email (such as an ongoing review or a plugin closure request), please reply directly to the original email thread rather than starting a new message.

Can I join the team?

Please take a look at this handbook page.

Submissions and Reviews

Where do I submit my plugin?

Go to the Add page and upload your file. You should make sure that:

It’s a .zip file and under 10Mb.

It’s in the common WordPress plugin format so that it can be installed using the ‘Upload Plugin’ feature in WordPress.

It’s production-ready: complete, without errors, without unnecessary logs, without development tools, and that all necessary files are properly compiled or generated.

We do not accept placeholders or plugins that aren’t ready to be used.

What if my plugin is over 10 megs?

Double check that you aren’t including unused files (like test folders, documentation, and full node/vendor folders). The majority of plugins who face this issue have included all sorts of development content that has no place in the final code.

What happens after submission?

You will receive an automated email confirming that your submission has been received. Your plugin will then be added to our review queue, and we’ll review it as soon as we reach it.

If we don’t find any issues related to security, compatibility, compliance with the guidelines, or overall presentation, your plugin will be approved.

If we identify any issues, we’ll send you an email explaining what needs to be addressed. The subject line will look like: [WordPress Plugin Directory] Review in Progress: {Your plugin name}
Please be sure to check your spam or junk folder if you don’t see this email in your inbox, as it may occasionally be filtered there.

What will my plugin permalink (slug) be?

When you submit a plugin, you get an automated email telling you what the slug will be. This is populated based on the value of your Plugin Name in your main plugin file (the one with the plugin headers).

For example:

Plugin name: Boaty McBoatface

Autogenerated Slug: boaty-mcboatface

If there is an existing plugin with your name or slug, then you’ll get a warning on the submission.

The slug will also determine the following:

The URL of your plugin’s WordPress.org public page: wordpress.org/plugins/boaty-mcboatface

The folder name of your plugin in the WordPress plugins directory: <wp-content-folder>/plugins/boaty-mcboatface

The address of your plugin’s SVN repository and trac: plugins.svn.wordpress.org/boaty-mcboatface and plugins.trac.wordpress.org/browser/boaty-mcboatface

Your plugin’s text-domain for internationalization functions: esc_html__('Hello', 'boaty-mcboatface');

Once your plugin is approved, this name cannot be renamed. Please chose wisely.

Why did I get a different slug than I was told?

If we have to change your permalink (slug) we will always email you to explain why. In general, we change your permalink when you have obvious typos or mistakes (foundre instead of founder, for example) or if there are conflicts with existing trademarks, project names or other plugins. Please make sure you read your review email carefully, as we do explain why we do things.

Why is my submission failing saying my plugin name already exists?

There are two reasons this happens:

You’re trying to use a plugin with a permalink that already exists on WordPress.org

You’re trying to use a plugin with a permalink that exists outside WordPress.org and has a significant user base.

The first one is obvious. You can’t have two plugins with the same permalink so you need to pick a new one.

The second one is confusing because it’s telling you that somewhere, not on WordPress.org, that permalink is in use. It’s important to understand that the way the plugin update API works is that it compares the plugin folder name (i.e. the permalink) to every plugin it has hosted on WordPress.org. If there’s a match, then it checks for updates and users are prompted to upgrade.

When that happens, users of the ‘original’ plugin (the one we don’t host) would upgrade to the one from WordPress.org and, if that isn’t what you actually wanted to do, you could break their sites.

Sometimes this situation develops when a company or person releases their plugin privately (via Github for example) and decides they want to re-release it on WordPress.org. In those cases, we recommend you email us and we’ll walk you through how to get past the error.

Why am I getting an error that says I cannot begin my plugin name with a term?

That error is to inform you that you may not begin your Display Name with someone else’s trademarked or common term. This is to protect you and the directory from legal issues regarding trademark abuse and to prevent confusion with 3rd party projects and plugins. To correct the issue, you must change the Display Name in your plugin’s readme and main PHP files.

Please do not try to ‘work around’ this by cleverly renaming your plugin (WuuCommerce for example). All that does is make us worry you’re not going to be able to follow guidelines in the future.

Why am I getting an error that says I cannot use a term entirely in my plugin name?

Some trademark owners have requested we no longer permit the use of specific terms in plugin names entirely. If you see this error, then you must remove the term from your plugin name.

To proceed with this submission you must remove “[TERM]” from the Plugin Name: line in both your main plugin file and readme entirely.

If you attempt to get around this by changing your term from ‘Facerange’ to ‘Face-Range’, we will pend your submission and reiterate that you cannot use the term. Please don’t try to be sneaky or clever to get past this restriction.

How do I submit an official plugin?

Log in as the official organization user account and submit with that account only.

How we will know that you are the official organization? Because of your email address mostly.

We cannot accept plugins that act in name of an organization submitted by individual developer accounts, unless they’re clearly company ones as well. For example, submitting your official plugin with a user that has a gmail address is likely to be flagged for trademark infringement.

What if I submitted the plugin with the wrong user ID?

Just reply to the email right away and let us know. We can transfer ownership for you. If you forget to do this, you can fix it yourself by adding the correct account as a committer and then having that account remove your own.

DO NOT resubmit your plugin. Just tell us right away and we’ll fix it.

How long does it take to get a plugin approved?

There’s no official average, as no two plugins are the same. If your plugin is small and all the code is correct, it should be approved within fourteen days of initial review.

If your plugin has any code issues, it will take as long as it takes for you to correct the issues. Either way, you will get an email from plugins@wordpress.org with the status, so please add that to your email whitelist and patiently wait for our response.

I sent in the fixes but no one replied. How long should I wait?

We aim to reply to all reviews within ten (10) business days. If it’s been less than that, it just means we’ve been really busy. If it’s been two days, like over a weekend or a holiday, then you should not reasonably expect a reply.

Remember the review team is made up of 100% volunteers, all of whom have full time day jobs, and other volunteer duties. We do reply promptly, but we also have lives outside of WordPress.

If my plugin has a problem, how long do I have to fix it?

There’s no timeline and as long as we know you’re working on it and we feel you’re making progress, we’ll leave the review open. Your plugin will be rejected after 3 months, but the review will remain open.

Why was my plugin rejected after three months?

If your plugin review is not complete after three (3) months, we will reject your submission in order to keep the queue maintainable. At any point in time, we have more than 3500 people mid-review, and we figure that 3 months is a pretty reasonable time frame.

I finally fixed my plugin. Should I resubmit?

If your plugin was rejected after three months, submit it again and reply to the email so we are aware that you wanna continue a previous unfinished review. Even if it’s been 18 months. The longest time to date has been 3 years. We don’t mind if it takes a while.

DO NOT resubmit your plugin if it was rejected for any other reason, just reply to the email.

How many plugins can I submit for review at a time?

Generally, just one. If you’re a plugin author with more than one million active plugin installations, we understand that you have more ongoing projects, so you would have a different limit of up to 10 plugin submissions at the same time.

Why can’t I submit more than one plugin at a time?

Allowing people to have multiple submissions at once was proven to be detrimental to the review process. Errors were regularly found in all the plugins, resulting in the same emails being sent multiple times. In addition, people often got confused as to which review they were working on, muddying the waters about what needed to be solved. By changing this to one-at-a-time, confusion in those matters dropped significantly.

In addition, many new users don’t know how to use SVN, and wound up submitting multiple plugins and never using any. That can be a drain on our resources, so we do limit people.

Since all plugins get an initial review within four weeks, this should not be a hardship.

Can I submit multiple plugins with multiple accounts?

No. And if you do so, we will suspend all your secondary accounts. Don’t try to get around the one-at-a-time rule please.

I need my plugin approved by a specific date, what should I do?

Submit it as early as possible. Unless the plugin is meant to address a security or legal issue, we don’t permit queue jumping. If it is related to one of those, please email plugins@wordpress.org and explain the situation.

Are there specific things that I should avoid doing?

We look for some pretty obvious things, all of which are listed in our guidelines. Most can be summed up as “Don’t be a spammer,” but to touch on the ones people do the most:

Not including a readme.txt file when acting as a service

Not testing the plugin with WP_DEBUG

Including custom versions of packaged JavaScript libraries

Calling external files unnecessarily

“Powered By” links

Phoning home

Again, this is a brief overview. Please read the guidelines, as the full list is quite detailed.

Are there plugins you don’t accept?

We do not accept plugins that have no meaningful purpose or provide no practical functionality.

We also do not accept plugins that facilitate illegal activity or encourage harmful behavior. This includes, but is not limited to, black-hat SEO tools, content spinners, fake content creators, scrappers, hate-related plugins, and similar software.

We also do not accept new plugins that allow arbitrary code insertion or execution. Examples include PHP or JavaScript editors, file managers, and AI tools that generate code intended to be executed on the site. HTML output is permitted, provided it is properly escaped and handled securely.

Plugins must not download or execute code from external sources or serve just as a tool to install other plugins. Please refer to Guideline 8 for more information.

Similarly we do not accept framework plugins or library plugins. If your plugin has to require other plugins or themes to edit themselves in order to use your plugin, it’s a library. If your plugin is a template from which more code can be built by customizing the files directly, it’s a framework or boilerplate. Frameworks and libraries should be packaged with each plugin (hopefully in a way that doesn’t conflict with other plugins using the framework or libraries). At least until core supports plugin dependencies.

We do not accept plugins that are essentially copies of existing work or that merely duplicate functionality already provided by WordPress Core. Your plugin should introduce new functionality, solve a specific problem, or provide a meaningfully different approach to an existing solution.

Likewise, we generally do not accept plugins whose functionality is already extensively represented in the Plugin Directory by hundreds of comparable alternatives, unless they provide clear, meaningful differentiation or introduce substantial innovation.

I want to redo, upgrade, or rebrand my existing plugin. I just submit again, right?

No, you should rewrite and upgrade the existing plugin. Make it a major version release. We can’t rename plugins or transfer users, so a new one wouldn’t carry over any existing users, reviews, support topics, ratings, downloads, favorites, etc. Basically you’d leave all your current users out in the cold, and that’s mean.

I made a mistake with my submission. How can I fix it?

You can update your plugin files from the submission page at any time.

You can update your slug once after submitting it.

Every submission gets an automated email with directions. If you have a different issue, please reply to that or email plugins@wordpress.org and explain the situation.

Regarding slugs if you need further changes, you’ll need to contact us. We also try to catch typos in names before we approve anything, but we make mistakes too.

Are there things I can’t do in a plugin name?

We have the following restrictions:

Plugins may not use vulgarities in the name or slug

Plugins may not use ‘WordPress’ or ‘Plugin’ in their slugs except under extreme situations

Plugins may not use version numbers in plugin slugs

Due to system limitations, only English letters and Arabic numbers are permitted in the slug

Plugins may not start or contain in a way that may be confusing a trademarked term or name of a specific project/library/tool
…(内容过长已截断)

------
导航页打开网址