WordPress.org

Venezuela

Consigue WordPress
WordPress.org

Plugin Directory

Polylang

Polylang

Por Chouby
Descargar

Descripción

With Polylang fully integrated to WordPress and using only its built-in core features (taxonomies), keep steady performances on your site and create a multilingual site featuring from just one extra language to 10 or more depending on your needs. There is no limit in the number of languages added and WordPress’ language packs are automatically downloaded when ready.

Características

Depending on the type of site you have built or are planning to build, a combination of plugins from the list below might be of interest.
All plugins include a wizard allowing to setup them in just a few clicks.

Polylang

Polylang and Polylang Pro share the same core providing features such as:

  • Translating posts, pages, media, categories, post tags, custom post types and taxonomies, RSS feeds; RTL scripts are supported.
  • The language is either set by the language code in URL, or you can use a different sub-domain or domain per language.
  • Automatic copy of categories, post tags and other metas when creating a new post or page translation.
  • 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.
  • Compatibility with Yoast SEO.

Polylang Pro

Helps optimizing the time spent translating your site with some very useful extra features such as:

  • Better integration in the new Block Editor.
  • Language switcher available as a block.
  • Language options available in the widget block editor.
  • Template parts translatable in the site editor (FSE).
  • Duplicate and/or synchronize content across post translations.
  • Improved compatibility with other plugins such as ACF Pro.
  • Share the same URL slug for posts or terms across languages.
  • Translate URL slugs for categories, author bases, custom post types and more…
  • Machine translation with DeepL.
  • Export and import of content in XLIFF format for outsourced professional translation.
  • Access to a Premium Support for personalized assistance.

Polylang for WooCommerce

Add-on for the compatibility with WooCommerce which provides features such as:

  • Translating WooCommerce pages (shop, check-out, cart, my account), product categories and global attribute terms directly in the WooCommerce interface.
  • Translating WooCommerce e-mails and sending them to customers in their language.
  • Products metadata synchronization.
  • Compatibility with the native WooCommerce CSV import & export tool.
  • Compatibility with popular plugins such as WooCommerce Subscriptions, Product Bundles, WooCommerce Bookings, Shipment Tracking and more.
  • Ability to use the WooCommerce REST API (available with Polylang Pro).
  • Access to a Premium Support for personalized assistance.

Our other free plugins

Agradecimientos

Muchas gracias a todos los traductores que ayudan a traducir Polylang. Muchas gracias a Alex Lopez por el diseño del logotipo. La mayoría de las banderas incluidas en Polylang provienen de famfamfam y son de dominio público. Sea cual sea el código de terceros que se haya usado, el crédito se ha señalado en los comentarios del código.

Capturas

  • El panel de administración de idiomas de Polylang
  • El panel de administración de traducciones de cadenas
  • Biblioteca de medios multilingüe
  • La pantalla de edición de entradas con la sección de idiomas

Instalación

  1. 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).
  2. Si has probado otros plugins multilingües, desactívalos antes de activar Polylang, de lo contrario, ¡puedes obtener resultados inesperados!
  3. Instala y activa el plugin como es habitual desde el menú «Plugins» de WordPress.
  4. The setup wizard is automatically launched to help you get started more easily with Polylang by configuring the main features.

Preguntas frecuentes

¿Dónde encontrar ayuda?

¿Polylang es compatible con WooCommerce?

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.

Reseñas

It just works and support is great

12 de noviembre de 2025
I manage two projects, one with WPML and one with Polylang. WPML might have more features, but these come at a price, because WPML is slow and needs constant monitoring – to be honest, 90 % of issues the site has are created by WPML updates and feature changes. Polylang on the other hand just works. It’s fast, reliable and includes most features you’d want, especially with Polylang Pro and the WooCommerce addon. Support is super fast and helpful as well. Highly recommended!

Very useful!

10 de noviembre de 2025
Thank you that’s a great plugin. Easy to set, very user friendly and no major issues.thanks for developing!

Our Honest Experience with Polylang — and Why We Feel Deeply Disappointed

30 de octubre de 2025
We feel extremely alienated by the company’s business practices. We used the free Polylang plugin and manually translated numerous pages, investing a great deal of time and effort. Later, we wanted to automatically translate additional pages, translate the menu, duplicate pages, manage SEO — simply the features that the Pro version was supposed to provide. So we purchased the Pro plugin. After installation, however, we discovered that the Pro features are not compatible with the Breakdance Builder editor we use. There is no mention anywhere on the company’s website that Polylang does not work with third-party editors like Breakdance. As a result, the Pro plugin is completely useless for us, and we requested a refund and cancellation. The Pro plugin has since been uninstalled. We were told that a refund would only be possible if we also stopped using the free standard version. Even after several rounds of back-and-forth communication, Polylang insists on this condition — citing flimsy arguments such as being a small company and suggesting that if we don’t like Polylang, we should delete it entirely. There is a total lack of understanding that the incompatibility with Breakdance is not our fault as customers. Instead, they seem offended and are essentially trying to force us to pay for the Pro version just to be allowed to keep using the free one. We have never experienced anything like this before. We will continue to use the free version, as we have already translated a lot of content with it. The Pro version has been paid for but deleted, as it is unusable with Breakdance. We hope our payment helps them get through the next month — or whatever else it may be. :-(PS: We could have simply uninstalled the free plugin, requested the refund, and then reinstalled it afterward. But unlike them, we’re an honest company — even though we’re also small and have a limited budget.
Leer todas las 2.871 reseñas

Colaboradores y desarrolladores

«Polylang» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«Polylang» ha sido traducido a 54 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «Polylang» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

= 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_translation filter 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_attributes and pll_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

See changelog.txt for older changelog

Meta

Valoraciones

4.7 out of 5 stars.

Añadir mi reseña

See all reviews

Soporte

Problemas resueltos en los últimos dos meses:

9 de 28

Ver el foro de soporte

Donar

¿Te gustaría apoyar el progreso de este plugin?

Dona a este plugin