wp-plugin-directory-guidelines

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Overview

概述

Authoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming/trademark rules, trialware restrictions, and all other submission requirements.

WordPress.org插件目录18条指南的权威参考资料。涵盖GPL许可证、插件命名/商标规则、试用软件限制以及所有其他提交要求。

When to use

使用场景

Use this skill when you need to:

Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines
Check GPL license compatibility for a plugin or its bundled libraries
Verify license headers in plugin files
Identify common guideline violations before submission
Answer questions about what is or is not allowed on WordPress.org
Evaluate premium/upsell flows, license checks, or freemium positioning
Review "teaser" or "preview" UI for trialware violations

当你需要以下操作时，可使用本技能：

审核WordPress插件是否符合WordPress.org插件目录指南
检查插件或其捆绑库的GPL许可证兼容性
验证插件文件中的许可证头
在提交前识别常见的指南违规情况
解答关于WordPress.org允许或禁止内容的问题
评估付费/增值销售流程、许可证检查或免费增值定位
审核“预告”或“预览”UI是否存在试用软件违规情况

Inputs required

所需输入

Plugin source code (or specific files to review)
Optional: plugin readme and plugin header metadata for naming and license checks

插件源代码（或需审核的特定文件）
可选：插件readme文件和插件头元数据，用于命名和许可证检查

Procedure

流程

Check the plugin's license header against the Valid License Headers section below.
Walk through the 18 Guidelines checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.
Confirm trialware/freemium compliance using the checklist in guideline-review-checklist.md (Guideline 5 section).
For bundled third-party code, verify license compatibility against GPL-Compatible Licenses (Quick) below.
Flag matches from Common GPL Violations (Quick) below.
For edge cases, consult the detailed references and the GNU GPL FAQ.

根据下方的有效许可证头部分检查插件的许可证头。
按照18条指南清单逐一检查，重点关注指南1、4、5、7、8和17。
使用guideline-review-checklist.md（指南5部分）中的清单确认试用软件/免费增值模式的合规性。
对于捆绑的第三方代码，根据下方的**GPL兼容许可证（速查）**验证许可证兼容性。
标记下方**常见GPL违规情况（速查）**中的匹配项。
对于边缘情况，查阅详细参考资料和GNU GPL FAQ。

18-Guideline Review Checklist

18条指南审核清单

Use the detailed, per-guideline checklist in guideline-review-checklist.md. Load this reference file only when a full guideline audit is requested.

使用guideline-review-checklist.md中的详细逐条指南清单。仅在要求进行全面指南审核时加载此参考文件。

GPL Compliance (Guideline 1 in Detail)

GPL合规性（指南1详细说明）

Use gpl-compliance.md for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.

如需完整的许可证表格、兼容性细节和示例，请使用gpl-compliance.md。本内联部分作为快速决策辅助工具。

Verification (Licensing)

验证（许可证相关）

Every licensing-related issue must cite Guideline 1 and include the file path and exact license string.
Confirm compatibility claims against GPL-Compatible Licenses (Quick) and escalate ambiguous licenses.

所有与许可证相关的问题必须引用指南1，并包含文件路径和确切的许可证字符串。
根据**GPL兼容许可证（速查）**确认兼容性声明，对模糊的许可证进行升级处理。

Failure modes (Licensing)

失败模式（许可证相关）

If a license is not clearly GPL-compatible, do not guess. Check the GNU license list.
For dual-license packages, verify both licenses and redistribution terms.

如果某许可证未明确显示为GPL兼容，请勿猜测。请查阅GNU许可证列表。
对于双许可证包，验证两个许可证和再分发条款。

Quick Reference: WordPress GPL Requirements

速查：WordPress GPL要求

WordPress is GPLv2 or later.
Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).
Include a valid
```
License:
```
header and
```
License URI:
```
in the main plugin file.
Do not add restrictions that conflict with GPL freedoms.

WordPress采用GPLv2或更高版本。
在WordPress.org分发的插件必须100%兼容GPL（代码和资源）。
主插件文件中需包含有效的
```
License:
```
头和
```
License URI:
```
。
不得添加与GPL自由相冲突的限制条款。

Valid License Headers

有效许可证头

GPL Versions Summary

GPL版本概述

Version	Year	Key Addition
GPLv1	1989	Base copyleft: share-alike for modifications
GPLv2	1991	"Liberty or death" clause (Section 7), clearer distribution terms
GPLv3	2007	Anti-tivoization, explicit patent grants, compatibility provisions

WordPress uses GPLv2 or later, meaning plugins can use GPLv2, GPLv3, or "GPLv2 or later".

For full license texts, see:

版本	年份	关键新增内容
GPLv1	1989	基础Copyleft：修改后的代码需共享相同许可证
GPLv2	1991	“不自由毋宁死”条款（第7节），更清晰的分发条款
GPLv3	2007	反Tivo化条款、明确的专利授权、兼容性规定

WordPress采用GPLv2或更高版本，这意味着插件可使用GPLv2、GPLv3或“GPLv2或更高版本”许可证。

如需完整许可证文本，请查看：

License Compliance Checklist

许可证合规性清单

When reviewing a plugin, verify:

Main plugin file has a valid

License:

header (e.g.,

GPL-2.0-or-later

GPL-2.0+

GPLv2 or later

)

Main plugin file has a
```
License URI:
```
header pointing to the GPL text
If bundled libraries exist, each has a GPL-compatible license
No "split licensing" (e.g., code GPL but premium features proprietary)
No additional restrictions beyond what GPL allows
No clauses restricting commercial use, modification, or redistribution
No obfuscated code (violates the spirit of source code availability)

审核插件时，请验证：

主插件文件包含有效的
```
License:
```
头（例如：
```
GPL-2.0-or-later
```
、
```
GPL-2.0+
```
、
```
GPLv2 or later
```
）
主插件文件包含指向GPL文本的
```
License URI:
```
头
若存在捆绑库，每个库均具有GPL兼容许可证
无“拆分许可证”（例如：代码采用GPL但付费功能为专有）
无超出GPL允许范围的额外限制
无限制商业使用、修改或再分发的条款
无混淆代码（违反源代码可用性的精神）

Valid License Headers for WordPress Plugins

WordPress插件的有效许可证头

License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

text

License: GPL-3.0-or-later
License URI: https://www.gnu.org/licenses/gpl-3.0.html

text

License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

text

License: GPL-3.0-or-later
License URI: https://www.gnu.org/licenses/gpl-3.0.html

text

License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

GPL-Compatible Licenses (Quick)

GPL兼容许可证（速查）

Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.
Commonly accepted permissive families: MIT/Expat, BSD, ISC, zlib, Boost.
Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).
For full accepted and rejected identifiers, use gpl-compliance.md.

安全默认选项：GPL-2.0-or-later、GPL-3.0-or-later。
普遍接受的宽松许可证家族：MIT/Expat、BSD、ISC、zlib、Boost。
条件兼容性需谨慎：Apache-2.0和MPL-2.0（验证使用场景）。
如需完整的可接受和拒绝许可证标识符，请使用gpl-compliance.md。

Common GPL Violations (Quick)

常见GPL违规情况（速查）

Split licensing that restricts distributed code.
Obfuscated or non-corresponding source distribution.
Restrictive clauses (non-commercial, no-resale, forced backlink).
Bundling GPL-incompatible libraries or assets.

拆分许可证限制分发代码。
混淆或不对应的源代码分发。
限制性条款（非商业使用、禁止转售、强制反向链接）。
捆绑与GPL不兼容的库或资源。

Plugin Naming Rules (Guideline 17)

插件命名规则（指南17）

Use naming-rules.md for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.

如需完整的商标列表、slug禁用词和命名示例，请使用naming-rules.md。本内联清单用于快速筛选。

Naming Checklist (Quick)

命名清单（速查）

Name is not a placeholder and has at least 5 alphanumeric characters.
Header name and readme name match.
Name is specific and function-related; avoid keyword stuffing.
Trademark/project names appear only after connectors like
```
for
```
,
```
with
```
,
```
using
```
,
```
and
```
.
No banned/discouraged terms or trademark portmanteaus.
Slug is lowercase, hyphenated, <= 50 chars, and avoids blocked terms.

名称不是占位符，且至少包含5个字母数字字符。
插件头名称与readme文件名称一致。
名称具体且与功能相关；避免关键词堆砌。
商标/项目名称仅在连接词（如
```
for
```
、
```
with
```
、
```
using
```
、
```
and
```
）之后出现。
无禁用/不推荐术语或商标混合词。
Slug为小写、连字符分隔、长度≤50字符，且避免使用禁用词。