WordPress.org

Plugin Reviews

Polylang

Making WordPress multilingual

Average Rating
4.8 out of 5 stars
You are currently viewing the reviews that provided a rating of 3 stars. Click here to see all reviews.
Good but lots of work to be done
By , for WP 4.4.2

When adding the languages if you don't translate ALL the posts, labels, categories, tags, etc. the website breaks completely.
Also lots of problems showing the language switch on the menu and on the sidebar.
Maybe it's all down to the fact that I'm using WooCommerce, not sure, but for now I've removed it.

Unclean Uninstall
By , for WP 4.4.1

I tested this plugin on a live website and didn't find it suiting my needs. I had added two languages, and after I had uninstalled it (I checked the "delete all data" option in the plugin settings), all of my taxonomy terms were double, one with and one without "-en" ending.

If I didn't have a recent backup, it would have been a pain in the ass to fix that manually since I have several hundred terms in different taxonomies. Would be nice if you could make sure this gets cleaned up when removing the plugin.

Found error after adding a social link
By , for WP 4.3.1

I really like this plugin, but I found the error after I added a social link in my web page. I use the theme 'Hueman'. The following is the error displayed :

Warning: Illegal offset type in isset or empty in /home/content/p3pnexwpnas07_data03/48/2849348/html/wp-content/plugins/polylang/include/cache.php on line 53

Warning: Illegal offset type in isset or empty in /home/content/p3pnexwpnas07_data03/48/2849348/html/wp-includes/pomo/translations.php on line 85

Warning: Illegal offset type in /home/content/p3pnexwpnas07_data03/48/2849348/html/wp-content/plugins/polylang/include/cache.php on line 41

Warning: Illegal offset type in isset or empty in /home/content/p3pnexwpnas07_data03/48/2849348/html/wp-content/plugins/polylang/include/cache.php on line 53

Warning: Illegal offset type in isset or empty in /home/content/p3pnexwpnas07_data03/48/2849348/html/wp-includes/pomo/translations.php on line 85

Warning: Illegal offset type in /home/content/p3pnexwpnas07_data03/48/2849348/html/wp-content/plugins/polylang/include/cache.php on line 41

This is the link screenshot
Screenshot

Could not complete pagination with activated polylang
By , for WP 4.2.2

I could not done the pagination with activated polylang. It always makes one of issues bellow
- 404
- PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 130968 bytes) in /wp-includes/canonical.php on line 532
- PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8208 bytes) in /wp-content/plugins/polylang/include/model.php on line 397
Deactive the plugin , it should work.

Good functionality but crashed my site very often
By , for WP 4.1.1

I'm experimenting problems every time I update this plugin as is taking my blog down.
It's very good in functionality but today it's the fourth day my site is down and I don't know how to fixed :s

Needs some work for Chinese use cases
By , for WP 3.6

This plugin lists Chinese languages as follows:
中文 (Locale: zh_CN; Language Code: zh)
香港 (Locale: zh_HK; Language Code: zh)
台灣 (Locale: zh_TW; Language Code: zh)

In English this would read:
Chinese
Hong Kong
Taiwan

"Hong Kong" and "Taiwan" are places, not languages. A better way to name these would be:
中文 (中国)
中文 (香港)
中文 (台灣)

In English this reads:
Chinese (China)
Chinese (Hong Kong)
Chinese (Taiwan)

Aside from the naming, the language codes need to be unique in Polylang and by default they are all "zh". You could substitute a bogus two-letter language code, but then it shows in the URL permalinks. The better and industry standard way to do this is to use the locale code (zh-CN, zh-HK, zh-TW, en-US, etc.) in the URL and everywhere else instead of just the two-letter language code like Polylang.

Until these roadblocks for Chinese language integration are dealt with, I think I'll have to look for an alternate multilingual solution.

Good work!
By , for WP 3.6

Pretty good, I've tried it but It doesn't support the Buddypress 1.8.1 installation.

As soon as I created custom pages por Activity page it broke it so, I'll try next time when it supports that Buddypress version.

Another comment is that, it would be much better if shouldn't have to create a new page per language, it's really uncomfortable, instead, it should be one page for all languages.

I loved the /language/ at the url.

Good work guys.

You must log in to submit a review. You can also log in or register using the form near the top of this page.