What’s new in the world of Polylang?

WooCommerce 3.0 introduced major changes in its structure. The main goal was to be able to use custom tables for products and orders in the future. This did not impacted Polylang for WooCommerce very much because WooCommerce mostly kept the backward compatibility with its previous versions. As Polylang for WooCommerce strongly relies on the underlying…

It is possible that most of the changes included in this new version won’t be visible to most users. The previous versions focused on new features. It is however as important to spend time to improve the plugin foundations. The synchronization process of taxonomy terms and custom fields was designed quite a long time ago…

When we released our last version of Polylang for WooCommerce, we were very proud to be just in time for the new CSV importer introduced in WooCommerce 3.1. But things don’t always run as expected and we missed an important issue with SKUs that was reported a few weeks later. Even worse, it was not…

Let’s imagine that you have a site in English and in Arabic. WordPress allows you to choose your backend language. But if, for example you choose English, your editor will be in English too, meaning that you have to write your post from left to right, even if you are writing a post in Arabic….

Probably, the most important feature introduced by WooCommerce 3.1 is the possibility to export and import products with a CSV file. During the past weeks, we worked hard to make Polylang for WooCommerce compatible with this feature. How does it work? When you will export your products with the new export tool, you will get…

A few days ago, we released Polylang for WooCommerce 0.6. Of course, we don’t expect it to be totally bug free, but we consider it to be fairly stable and that it decently covers all expected features for a multilingual WooCommerce shop. After more than 7 months of in-situation tests on hundreds of sites, we have…

Let’s imagine that you have to manage a site for US and UK. Some pages may be different for both countries – for example a store’s directory or local news – but it could happen that some pages could be the same for both countries – for example a documentation page or global news. In…

Polylang Pro 2.0 comes with major features for users having multiple domains: Another major improvement for Polylang Pro users is the integration of Advanced Custom Fields Pro: Custom fields are automatically copied when you create a new translation. Some new features are common to both versions of Polylang: Also some major changes, interesting mainly developers,…

I am glad to announce that the long awaited Polylang extension for WooCommerce is now available to allow you to create a multilingual shop. It is already tested by a few Polylang Pro customers for more than one month, some of them already using it on a production site. This extension can work either with Polylang…

Almost five years ago, I started writing a multilingual plugin for my personal needs. Three months later, I made it available to the public and released Polylang 0.1 on wordpress.org. To my great surprise, the number of users grew very rapidly. I started adding more features. Synchronization in 0.7, media in 0.9, WPML config file…

WordPress provides a lot of filters (and actions) to allow plugins or themes to modify the WordPress comportment. Among them, ‘get_search_form’ can be used to modify the search form. If a theme author codes a search form which does not pass through this filter, no plugin is aware of this search form and thus no plugin can…

Quite often, I see plugins calling WordPress functions before the action ‘plugins_loaded’ has been fired, i.e. before all plugins are loaded. Thus, plugins which are loaded after can’t make use of available filters. Among the most frequent functions called as soon as the plugin is loaded are the function ‘load_plugin_textdomain’ and the function ‘get_option’. For…