描述
Polylang与WordPress完全集成，只使用其内置的核心功能（分类法），可保持网站的稳定运行，并根据您的需要创建一个多语言网站，语言种类从一种到10种或更多。添加的语言数量不受限制，WordPress 的语言包会在准备就绪时自动下载。
功能
根据您已建立或计划建立的网站类型，您可能会对以下列表中的插件组合感兴趣。
所有插件都包含一个向导，只需点击几下即可完成设置。
Polylang
Polylang 和Polylang Pro共享相同的核心功能，例如
- 翻译帖子、页面、媒体、类别、帖子标签、自定义帖子类型和分类法、RSS 源；支持 RTL 脚本。
- 语言可以通过 URL 中的语言代码设置，也可以为每种语言使用不同的子域或域。
- 在创建新的帖子或页面翻译时，自动复制类别、帖子标签和其他元数据。
- Translating classic menus and classic widgets. Also accessible with Site Editor Classic Features in block themes.
- Customizable language switcher available as a classic widget or a classic navigation menu item.
- 与 Yoast SEO 兼容。
Polylang Pro
通过一些非常有用的额外功能（如），帮助优化翻译网站所花费的时间：
- 更好地集成到新的区块编辑器中。
- 语言切换器可作为区块使用。
- 部件块编辑器中可用的语言选项。
- 可在网站编辑器（FSE）中翻译的模板部分。
- 重复和/或同步各翻译职位的内容。
- 改进与ACF Pro 等其他插件的兼容性。
- 跨语言共享相同的帖子或术语 URL 标头。
- 类别、作者库、自定义帖子类型等的URL slugs翻译…
- Machine translation with DeepL.
- 导出和导入 XLIFF 格式的内容，用于外包专业翻译。
- 获得高级支持，获得个性化帮助。
Polylang for WooCommerce
与 WooCommerce 兼容的插件，提供以下功能：
- 直接在 WooCommerce 界面翻译 WooCommerce 页面（商店、结账、购物车、我的账户）、产品类别和全局属性术语。
- 翻译 WooCommerce 电子邮件，并以客户的语言发送给他们。
- 产品元数据同步。
- 与本地 WooCommerce CSV 导入和导出工具兼容。
- 与 WooCommerce Subscriptions、Product Bundles、WooCommerce Bookings、Shipment Tracking 等流行插件兼容。
- 能够使用 WooCommerce REST API（Polylang Pro 提供）。
- 获得高级支持，获得个性化帮助。
我们的其他免费插件
- WPML to Polylang允许从 WPML 迁移到 Polylang。
- Site Editor Classic Features allows to use classic widgets (including the Polylang language switcher) and menus in the site editor (FSE).
鸣谢
非常感谢所有帮助翻译 Polylang 的译员。
非常感谢Alex Lopez设计的标志。
Polylang 中包含的大部分标志来自famfamfam，属于公共领域。
凡使用第三方代码的地方，均已在代码注释中注明出处。
屏幕截图
Polylang 语言管理员面板 
字符串翻译 admin panel 
多语言 media library 
编辑文章屏幕带有Language metabox
安装
- Make sure you are using WordPress 6.2 or later and that your server is running PHP 7.2 or later (same requirement as WordPress itself).
- 如果您尝试过其他多语言插件，请在激活 Polylang 之前停用它们，否则可能会得到意想不到的结果！
- 像往常一样从 WordPress 的 “插件 “菜单中安装并激活插件。
- The setup wizard is automatically launched to help you get started more easily with Polylang by configuring the main features.
常见问题
-
哪里找到帮助？
-
- First time users should read Polylang – Getting started, which explains the basics and includes a lot of screenshots.
- Read the documentation. It includes a FAQ and the documentation for developers.
- 搜索社区支持论坛。您可能会在这里找到答案。
- 阅读浮动的文章在 社区支持论坛.
- 如果仍有问题，请在社区支持论坛上开设新主题。
- Polylang Pro 和 Polylang for WooCommerce用户可通过帮助台获得我们的高级支持。
-
Polylang 是否兼容 WooCommerce ?
-
- You need Polylang for WooCommerce, premium addon described above, which will make both plugins work together.
-
Where do I report security bugs found in this plugin?
-
- Please report security bugs found in the source code of the Polylang plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.
评价
2025 年 12 月 13 日
Polylang is hands down the best multilingual plugin for WordPress. It’s incredibly easy to set up, works perfectly, and doesn’t slow down my site at all.
2025 年 12 月 11 日
I like (and prefer) the “simplicity” of the setup of Polylang. Configuring a multilingual website properly can be challenging but Polylang keeps the configuration options clean and organized. The only thing I don’t like is when you enable translation for Media, any media uploaded for the default language is not visible in the media browser when working in a translation and for instance having to select an image from the media library.
2025 年 12 月 9 日
If I’m building a multilingual website, Polylang is always my first choice. I’ve used it for years on countless WordPress projects, and it has never let me down. Stable, intuitive, and incredibly effective. A solid 5-star plugin!
2025 年 12 月 1 日
El millor plugin de traducció, amb una molt bona opciò gratuïta i millor de pagament
2025 年 12 月 1 日
the Best for me
2025 年 11 月 28 日
2 回复
[Edit: After reading the reply from the plugin author, explaining that there’s another plugin which constitutes a workaround to install the language switcher within FSE, I raised my review from 1 star to 2 stars. I still think the current free version is a dire experience for anyone using FSE, but it’s not totally broken.]
After doing a lot of research on Multilingual plugins, Polylang seemed like a sensible choice for my project. I installed it on my site, which uses Twenty Twentyfive, to see how it works, but am completely stuck trying to get a language switcher to show so I can try out the free features of the plugin.
I knew in advance that “FSE support” was somehow a paid feature, but I wanted to see for myself if the free version was truly as useless as that implied.
I understand if there are FSE features you want to require payment for. I think it’s a bad idea to punish people for using the latest features of WP, but I understand you would want to differentiate that way, and find conveniences related to FSE that you withhold in the free version.
But not having ANY way to add a language switcher in the default theme? It’s disastrous to the user experience. I just want to try out the plugin on my personal site, but because I am using Twenty Twentyfive, I have to pay full price just to see how it would work.
Without the language switcher, the plugin is just confusing. I can’t see how my translated posts relate to each other, or test any of the features that in theory work in the free version. I also can’t test whether your support for FSE is any good without purchasing, so should I assume it works at all? Most reviews of Polylang don’t mention FSE at all because it’s new, being able to try it out myself is the only course of action.
Please: Make the free version compatible with FSE as a baseline, then find aspects of full FSE support that are reserved for the paid version.
FSE is normal now, it should be possible to try out the plugin with an FSE site and see if it works before paying for the full version.
Thank you and sorry for the negative review, but I think the experience of someone using the plugin with the default theme should be represented. I’ll be happy to change my review if the plugin starts working with the default themes.
贡献者及开发者
「Polylang」是开源软件。 以下人员对此插件做出了贡献。
贡献者
更新日志
= 3.7.5 (2025-11-10)
- Pro: Updated DeepL supported languages list
- Pro: Fix a regression in cross domain login
- Pro: Fix post object field not correctly translated
- Pro: Fix a fatal error in EDD plugin updater when the request to the server fails
- Pro: Fix locale fallback in WP 6.8+
- Pro: Add
pll_enable_acf_labels_translationfilter allowing to disable the translation of ACF labels - Pro: Fix ACF image field not correctly translated when media translation is active
- Pro: Fix ACF image field in reapeater not copied
- Pro: Fix ACF ajax request unexpectedly filtered by language when editing a field group
- Pro: Fix ACF blocks not translated when included inside a non-ACF block
- Pro: Add compatibility of the duplicate tool with Divi
- Fix Undefined array key “terms” in canonical.php #1691
- Fix some regressions in the WPML API used by YITH WooCommerce Wishlist #1684
- Fix LinkedIn site title preview with Yoast SEO #1686
- Fix HTML language attribute on login page #1601
- Fix conflict with WP Job Manager Application #1749
3.7.4 (2025-10-28)
- Pro: Security: Fix a ReDoS vulnerability reported by Janine Moreira.
- Security: Fix deserialization of untrusted data reported by Phat RiO – BlueRock via Patchstack.
3.7.3 (2025-06-16)
- Pro: Always display ACF translation settings for field groups formerly translated in versions older than 3.7
- Pro: Fix translation displayed in child fields of ACF layout fields when they should not
- Pro: Fix translation of the ACF field “Choice” when the translation is set to “Copy once” or “Synchronize”
- Pro: Fix a PHP warning when translating some blocks
- Pro: Fix impossibility to change the language of an empty post in the block editor
- Fix duplicate values in options #1672
- Fix JS error in media library (grid view) #1674
- Fix language dropdown not present in the media modal accessible from the media library grid view #1675
- Fix DB error introduce by WooCommerce 9.9 #1681
3.7.2 (2025-05-27)
- Pro: Require ACF 6.0+ to activate the integration to avoid fatal errors with older versions
- Pro: Add a new ACF field group setting to decide if translations instructions must be displayed
- Pro: Fix a fatal error when using ACF blocks with ACF < 6.3.0
- Pro: Fix regression preventing to translate Oembed, URL and Email ACF fields
- Pro: Fix ACF fields not translated when they have a default value
- Pro: Fix empty ACF fields values not copied when the field has a default value
- Pro: Fix ACF field default values not translated when copying a post
- Pro: Fix possible fatal error if invalid types of data are sent for machine translation
- Pro: Fix term meta removed when a term is machine translated
- Fix nav menu locations not saved if invalid data are stored in database #1659
- Fix parent relationship removed when a new translated term is created without parent #1671
3.7.1 (2025-05-05)
- Pro: Do not display ACF fields translations settings when language location is set.
- Pro: Fix ACF taxonomy field terms not synchronized when “Save Terms” and “load terms” settings are activated.
- Pro: Fix duplicate options when using numeric keys for ACF choice fields.
3.7 (2025-04-22)
- Requires PHP 7.2 as minimum version
- Pro: Add DeepL machine translation for strings
- Pro: Consider Polylang Pro as equivalent to Polylang for plugin dependencies
- Pro: Add the details block and several labels in other blocks to XLIFF files and machine translation
- Pro: Allow to translate metas stored as objects
- Pro: Enhanced multilingual support of archive template hierarchy
- Pro: Wrap the language switcher block in a nav tag
- Pro: Support automatic IDs translation in blocks with new filters
pll_sync_block_rules_for_attributesandpll_sync_blocks_xpath_rules - Pro: Complete rewrite of ACF integration
- Pro: Add support for ACF blocks, post types and taxonomies.
- Pro: Remove the possibility to translate ACF field groups
- Pro: Add languages in ACF locations
- Pro: Add translation of ACF labels in the strings translations page
- Pro: Fix incorrect count of translated strings when importing strings translations
- Pro: Fix incorrect translation when an XLIFF import updates a term sharing its slug
- Pro: Fix term hierarchy with machine translation
- Pro: Fix indented items of a list block not translated with machine translation
- Pro: Fix navigation block inserted in the wrong language
- Update plugin updater to 1.9.4
- Add translation of widgets custom html in strings translations #1423
- Refactor core to manage the plugin options in an object #1451
- Refactor core to give access to languages management in all contexts #1503
- Remove the language set from the content option for new installs #1517
- Allow numbers in language codes #1546
- Display empty fields in the translations table for untranslated strings (instead of duplicating the original) #1574
- Add REST API endpoints to manage options and languages #1505 #1569
- Improve performance by registering the language taxonomy only once #1359
- Add new API functions to insert and update posts and terms in a given language #1500 #1520
- Add compatibility with jQuery 4 (planned in core for WP 6.8) #1612
- Fix translations not loaded when the language is set from the content #1395
- Fix possible term duplication #1490
- Fix sanitization of translated options that may impact other strings #1571
- Fix home link block not translated #1647
- Fix a conflict with WooCommerce Price Based on Country #1638
查看 changelog.txt 用于老的改变日志