Polylang 1.8 beta

I am glad to announce the availability of the beta version of Polylang 1.8.

The most visible changes are in the settings of Polylang. Indeed it is now possible to select the flag for each language directly from the admin interface.  Almost 250 flags are available. They are used on both admin and frontend side. However, it is still possible to use your own custom flags on frontend by putting them in the wp-content/polylang folder as before.

I totally revamped the settings tab. Choosing the default language or assigning this default language to the existing content is now done directly in the languages tab. Other options are now grouped by modules in a list table. This new interface mixes concepts from the plugins list table and the posts quick edit.

Advanced media users should be happy as I improved the compatibility with third party plugins using media taxonomies and custom fields. Indeed it is now possible to synchronize media taxonomies and custom fields as it was already the case for posts.

I attempted to work around an old bug in NextGen Gallery which prevents both plugins to work together. Although, a user proposed a fix, Nextgen Gallery has not been updated yet and I decided to include a workaround proposed by the Photocrati team. You might consider that it was a long time to wait, but this change is a bit risky and that’s the reason why I needed to wait for a major version. Hopefully Nextgen Gallery will fix its own bug in the future, as it’s always better to solve a problem at the source.

I also introduced a workaround for some WordPress locales which are not valid according to the W3C. Polylang will now automatically output the correct locale in the html source instead of the wrong one, normally outputed by WordPress.

A lot of changes occured under the hood. These changes could impact how third party plugins interact with Polylang. I will detail them in a separate post dedicated to developpers.

Polylang 1.8 includes a few other minor changes and fixes a lot of bugs detailed in the changelog.

There are a lot of new strings (most of them being country names). As explained a few days ago, translations of Polylang are now managed on Translating WordPress. A positive effect is that a lot of the new strings have already been automatically translated and validated for major languages (probably taken from other projects). It’s very easy to help translating in your own language.

My plan is to release the final version in January. Don’t hesitate to download Polylang 1.8 beta, test it and report bugs in the support forum. Thanks!

9 thoughts on “Polylang 1.8 beta

    1. Frédéric Post author


      Out of the box, Polylang is not sufficient to work comfortably with WooCommerce. It’s not that things break but you won’t be able to translate everything. There are already some third party plugins available to glue both plugins. And I am currently working on a new one.

      1. artesaniaswarovski


        That glue third party plugin that you are working..is available o has a project webpage?


      2. Gerd Neumann

        @Frédéric: That’s very interesting news! I just came here via google…

        Let us know as soon as something is available, e.g. a github repository or similar… Seems like https://wordpress.org/plugins/woocommerce-polylang-integration/ and https://wordpress.org/plugins/woo-poly-integration/ are not actively maintained anymore. We would love to use polylang to translate our website+shop, but a stable running polylang integration would be needed for this… If a plugin is done by the polylang developers then this would be great news and I would be very much convince that stabilty and quality of the software is great🙂

Comments are closed.