Polylang 1.6

Although maybe not the most visible new feature, WordPress 4.0 introduced a new way to manage WordPress translations files. Polylang 1.6 takes profit of this new feature and makes it compatible with multilingual websites, thus allowing managing WordPress translations in a much clever way than it was with previous versions. This works also for default Twenty themes and a few plugins (Akismet, WordPress Importer, BuddyPress…), managed by the WordPress translation project. All these translations can now be updated from the updates panel in the WordPress dashboard.

Polylang 1.6 also introduces a few other features such as the possibility to translate a text widget in the strings translations panel (up to now you needed to use one widget per language), and the support of opengraph language and translations metadata for websites running Jetpack or WordPress SEO.

To avoid a common mistake, Polylang will now force users to choose a static front page translated in all languages.

Some US users complained about my choice to associate the British flag to English (en_US). With the introduction of a new WordPress English (en_GB) language pack, I decided to change this. This means that from now, the British flag is associated to en_GB and the US flag is associated to en_US. Old users who kept the default flag for en_US will thus see the flag associated to the English language change when updating to Polylang 1.6. There are 2 different ways to come back to the British flag:

1. Edit the English language and change the locale from en_US to en_GB. This will also impact the html ‘lang’ markup and the WordPress en_GB translation will be used.

2. Create a polylang directory in wp-content. Copy the British flag wp-content/plugins/polylang/flags/en_GB.png to wp-content/polylang/en_US.png. This will impact only the flag on frontend, not on backend side.

Another important change concerns the Belarussian language, for which the default locale was changed from be_BY to bel to follow the WordPress locale.

Finally, I would like to thank all translators who updated Polylang translations with special thanks to Bajro who provided a brand new Croatian translation.


10 thoughts on “Polylang 1.6

  1. cholakovdev1

    BuddyPress? Can we used it now? I am not able to assign two different pages for registration.

    1. Frédéric Post author


      Although I mentionned BuddyPress because the translations of this plugin are managed by the WordPress translation project, I don’t test it and thus don’t know how it performs together with Polylang.

    1. Frédéric Post author


      I don’t reproduce such issue. Could you make the usual verifications (check for conflicts with plugins or themes) and open a topic in the support forum?

  2. Lidia

    I’ve used polylang on my website since march this year with Tempera theme (made by cryout creations), and i was happy about both. I had 2 presentation pages, one in polish, one in english (not full translated, but as much as i wanted was fine). But later, don’t know when exacly, seems some of polylang updates stole my english presentation page.

    I’ve written about my problem on creators website (http://www.cryoutcreations.eu/forums/t/multilanguage-site-presentation-page-logo) but maybe you could help me as well.

    1. Frédéric Post author


      I believe that your pages are not linked together. Check this on admin side. If you don’t succeed to solve this, please create a new topic in the forum which is better place to handle support.

  3. Tarik Jari

    Hello , first i would like to thank you for this great job, it’s the most simple plugin to use, i have personally tested wpml and qtranslate, but i prefer polylang for me , it’s the smart one, and i will donate for that !
    i am posting this comment to ask about flags, everything work fine, I try to display the flags with a drop down menu but they aren’t appeared !

Comments are closed.