Polylang

Description

Features

Polylang allows you to create a bilingual or multilingual WordPress site. You write posts, pages and create categories and post tags as usual, and then define the language for each of them. The translation of a post, whether it is in the default language or not, is optional.

  • You can use as many languages as you want. RTL language scripts are supported. WordPress languages packs are automatically downloaded and updated.
  • You can translate posts, pages, media, categories, post tags, menus, widgets…
  • Custom post types, custom taxonomies, sticky posts and post formats, RSS feeds and all default WordPress widgets are supported.
  • The language is either set by the content or by the language code in url, or you can use one different subdomain or domain per language
  • Categories, post tags as well as some other metas are automatically copied when adding a new post or page translation
  • A customizable language switcher is provided as a widget or in the nav menu

The author does not provide support on the wordpress.org forum. Support and extra features are available to Polylang Pro users.

If you wish to migrate from WPML, you can use the plugin WPML to Polylang

If you wish to use a professional or automatic translation service, you can install Lingotek Translation, as an addon of Polylang. Lingotek offers a complete translation management system which provides services such as translation memory or semi-automated translation processes (e.g. machine translation > human translation > legal review).

Credits

Thanks a lot to all translators who help translating Polylang.
Thanks a lot to Alex Lopez for the design of the logo.
Most of the flags included with Polylang are coming from famfamfam and are public domain.
Wherever third party code has been used, credit has been given in the code’s comments.

Do you like Polylang?

Don’t hesitate to give your feedback.

Screenshots

  • The Polylang languages admin panel
  • The Strings translations admin panel
  • Multilingual media library
  • The Edit Post screen with the Languages metabox

Installation

  1. Make sure you are using WordPress 4.7 or later and that your server is running PHP 5.2.4 or later (same requirement as WordPress itself)
  2. If you tried other multilingual plugins, deactivate them before activating Polylang, otherwise, you may get unexpected results!
  3. Install and activate the plugin as usual from the ‘Plugins’ menu in WordPress.
  4. Go to the languages settings page and create the languages you need
  5. Add the ‘language switcher’ widget to let your visitors switch the language.
  6. Take care that your theme must come with the corresponding .mo files (Polylang automatically downloads them when they are available for themes and plugins in this repository). If your theme is not internationalized yet, please refer to the Theme Handbook or ask the theme author to internationalize it.

FAQ

Where to find help ?
Is Polylang compatible with WooCommerce?
  • You need a separate addon to make Polylang and WooCommerce work together. A Premium addon is available.
Do you need translation services?
  • If you want to use professional or automatic translation services, install and activate the Lingotek Translation plugin.

Reviews

Does it – but far from perfect.

!First: be warned! It spoils the page in any case before everything is translated!

* Menu editing – pain. I had to install menu dulicator plugin to get menus working multilanguage. But then the settings are quite fine and good.

* Contents of basic language are not copied when making a copy in another language. Very annoying. And the flags (pencil, checked) in the content listings are not clear at all.

* PICTURES!!!! The whole pictures have to be duplicated?! Seriously?! With each language? Who invented that?

Yes it works in the frontend somehow and it is the only free tool that really works somehow. But let’s be honest. Even with all kinds of “multilanguage” plugins – still WordPress and multilanguage is a pain in the …
(try to install a plugin after the multilanguage tool, just one bad idea of many)

Disappointed … I would have hoped for better like a translation layer that jumps in on text and has it’s own translation tables in the database and the basic page is defined with a base language. Which then is translated by the database on the fly.

But … nope. Well take what they’ve made because there is no better one. So thanks to the makers in any case, because all in all it is an evolving tool.
Please keep up developing. THANKS!

Read all 719 reviews

Contributors & Developers

“Polylang” is open source software. The following people have contributed to this plugin.

Contributors

“Polylang” has been translated into 30 locales. Thank you to the translators for their contributions.

Translate “Polylang” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

2.5 (2018-12-06)

  • Add compatibility with WP 5.0
  • Fix custom flags when the WP content folder is not in the WP install folder
  • Fix PHP notice if a language has no flag

2.4.1 (2018-11-27)

  • Pro: Add compatibility with REST API changes made in WP 5.0
  • Pro: Fix sticky posts in the REST API
  • Pro: Fix overwritten custom post slug when the post is updated with the REST API
  • Pro: Fix bulk translate for media
  • Fix a conflict with Custom sidebars and Content aware sidebars
  • Fix a conflict with the theme Pokemania
  • Fix PHP notices when using the function ‘icl_link_to_element’ for terms
  • Fix title slugs for posts written in German

2.4 (2018-11-12)

  • Minimum WordPress version is now 4.7
  • Pro: Add the possibility to bulk duplicate or bulk synchronize posts.
  • Pro: Add compatibility with Admin Columns
  • Pro: Add synchronized posts to the REST API
  • Pro: Fix variations messed when changing WooCommerce attributes slugs
  • Pro: Fix incorrect language for ajax requests made on front by The Events Calendar
  • Pro: Fix term not duplicated correctly when the language is set from the content
  • Refactor the core to activate on front and for the REST api actions that were previously available only in the backend (language checks, synchronizations…).
  • Add flags to widgets displayed in only one language (Props Jory Hogeveen) #257
  • Honour the filter ‘pll_the_language_args’ for all options in menus #237
  • Add better filters for default flags and custom flags
  • Custom flags can now be stored in the polylang directory in the theme
  • Custom flags can now use SVG
  • Add compatibility with Jetpack featured content module
  • Fix Twenty Fourteen featured posts possibly not filtered per language
  • Fix home url not working with WordPress MU Domain mapping
  • Fix Assigning a parent category breaking the hierarchy of translated category
  • Fix: Accept 0,1 and 1.0 as q factors in browser preferred language detection (Props Dominic Rubas)
  • Fix performance issue when using hundreds of widgets
  • Fix translations possibly wrong if the post language is changed without saving the post after

See changelog.txt for older changelog