Polylang

Since WPML went from a GPL free license to a commercial one, the oid left in the WP i18n market has been hard to fill.

Polylang provides a different approach than the classic WPML interface, easy to get your head around and start using right away.

The plugin currently allows translating any kind of content inside the WordPress system, from posts, to pages, categories, custom post types, etc..

This counts as a good WPML replacement in our eyes.

Installation:

Unpack and upload it to the /wp-content/plugins/ directory.
Activate the plugin through the 'Plugins' menu in WordPress.

What is new in this release:

• Fix:
• Wrong redirection when using a static front page and replacing the page name by the language code (introduced in 1.7).

What is new in version 1.7.2:

• Fix:
• Wrong redirection when using a static front page and replacing the page name by the language code (introduced in 1.7).

What is new in version 1.6.5:

• Fixed:
• HTTPS issue
• Stop displaying an error when adding en_US as new language (translation not downloaded)
• Infinite redirect loop on (unattached) attachment links
• Impossible to add tags in post quick edit (introduced in 1.5)
• The customizer does not land to the right page when cumulating: static front page + page name in url + default language code not hidden
• Read parent theme wpml-config.xml before child theme
• Added protection to avoid empty language
• Page preview link again

What is new in version 1.6:

• Add Croatian translation contributed by Bajro
• Add new languages to predefined languages list: Azerbaijani, English (Australia), English (UK), Basque
• Add flag in front of the language select dropdown for posts and terms
• Add widget text translation
• Add opengraph support for locale and translations when WordPress SEO or Jetpack are activated
• Add error message if attempting to assign an untranslated page as static front page
• Add 'pll_sanitize_string_translation' filter to sanitize registered strings translations when saved
• Fix: change the en_US flag to US flag. The UK flag is now associated to en_GB
• Fix: change Belarussian locale from be_BY to bel to in agreement with translate.wordpress.org
• Fix home pages duplicate urls when using domains or subdomains
• Fix rewrite rules with front

What is new in version 1.5.5:

• Fixed:
• Missing argument 4 in icl_translate
• Conflict with Vantage theme
• Possible issue with cookie domain on 'localhost'
• Filtering string translations does not work when the group name contains a space
• Possible 404 error for attachments
• PHP notice when a shared term is not translated in all taxonomies

What is new in version 1.5.1:

• Added:
• Filter 'pll_settings_tabs' and action 'pll_settings_active_tab_{$tab}'
• Possibility to add a path when using multiple domains (same path for all languages)
• Fixed:
• Bad redirection if /language/ is added to urls (introduced in 1.5)
• Nav menu locations are not saved in customizer (introduced in 1.4)
• Unable to unset nav menu locations
• Incorrect link for date archives in language switcher (introduced in 1.5)
• Fatal error when using featured content in Twenty Fourteen
• Posts bulk edit broken (introduced in 1.5)
• Polylang does not play nice with switch_to_blog

What is new in version 1.5:

• Refresh translation metaboxes (again): now translated posts are chosen from an autocomplete input field
• Categories and post tags translations are also chosen in an automplete input field
• Better error management on languages pages
• Use Dashicons instead of Icomoon icons for WP 3.8+
• Check if translated post is readable by the current user before displaying the language switcher
• Minimum Twenty Fourteen version is now 1.1
• Code cleaning
• Add support for Quick draft introduced in WP 3.8
• Add support for object cache plugins for recent posts and recent comments widgets
• Add support for pages with modified query in the language switcher (ex: when multiple post types queried on the same page)
• Add new API functions: pll_languages_list, pll_set_post_language, pll_set_term_language, pll_save_post_translations, pll_save_term_translations, pll_count_posts
• Add new filter pll_the_languages_args
• Add support for ICL_LANGUAGE_CODE == 'all' on admin side

What is new in version 1.4.4:

• Added:
• Compatibility with widgets customizer introduced in WP 3.9
• Fixed:
• No post in translation dropdown after switching the language in edit post (introduced in 1.4.3)
• No canonical redirection when there is no language code in URL and the language code is not hidden for the default language
• Suppress language cookie when using multiple domains

What is new in version 1.4.2:

• Added:
• Check multiple post types in PLL_Model::count_posts
• Fixed:
• Error 404 on category links when setting the language by content (introduced in 1.4.1)
• PHP notices in frontend-nav-menu.php with Artisteer themes
• Decrease the memory usage of untranslated posts list

What is new in version 1.4.1:

• Fixed:
• The language switcher does not display the correct link for translated parent categories if only children have posts
• 3rd parameter of icl_object_id is not optional
• Issue when combining multiple domains and browser detection -> the combination is now forbidden
• Conflict Shiba Media Library: link between media translations is lost when using media quick edit
• Notice when using taxonomies in wpml-config.xml
• Incorrect post format link
• Twenty Fourteen Ephemera widget strings are not translated
• Bad gateway experienced by users hosted by wpengine.com

What is new in version 1.3:

• Improved performance by optimizing some queries for WP 3.5+
• The user biography in default language is now stored in default WordPress usermeta
• Add language parameter in API function pll_home_url and allow to call it on admin side
• Calling 'get_terms' with the 'lang' parameter now uses a cache object per language
• Bug correction: conflict with unstranslated taxonomies
• Bug correction: possible malformed translation archive url in language switcher
• Bug correction: a wrong language may be displayed in quick edit dropdown
• Bug correction: it is possible to add multiple translations (in the same language) for a single taxonomy term
• Bug correction: non public post types and taxonomies are visible in Polylang settings
• Bug correction: the language is always chosen from cookie (or browser preferences) in some installations
• Bug correction: Firefox language preference is not recognized when comparison is made on locale (instead of ISO 639-1 language code)
• Bug correction: incorrect tax_query in PLL_Auto_Translate

What is new in version 1.2.4:

• Bug correction: admin bar search does not filter by language
• Bug correction: possible conflict on secondary query when querying taxonomies or single page
• Bug correction: post type is not included in URL when editing or adding a term translation
• Bug correction: various warnings and PHP notices

What is new in version 1.2.2:

• Remove Jetpack infinite scroll compatibility code as it seems useless with new Polylang 1.2 code structure
• Bug correction: fatal error when doing ajax on frontend
• Bug correction: ICL_LANGUAGE_CODE incorrectly defined when doing ajax on frontend
• Bug correction: ['current_lang'] and ['no-translation'] indexes disappeared from pll_the_languages raw output
• Bug correction: invalid argument supplied for foreach() in /polylang/include/mo.php on line 57
• Bug correction: cookie may not correctly set

What is new in version 1.2:

• Major rewrite with new structure
• Change the language and translations model from meta to taxonomy (no extra termmeta table created anymore)
• Move the strings translations from option to a custom post type
• Add support for language code in subdomain and for one different domain per language (experimental)
• Add support of WordPress importer plugin. Export must have been done with Polylang 1.2+ (experimental)
• Add support for theme navigation customizer (was de-activated by Polylang since WP 3.4)

What is new in version 1.1.6:

• Add the possibility to display the upgrade notice on plugins page
• Bug correction: Illegal string offset 'taxonomy' in polylang/include/auto-translate.php
• Bug correction: user defined strings translations are not loaded on admin side
• Bug correction: untranslated post types are auto translated

What is new in version 1.1.4:

• Added simplified Chinese language.
• Added Indonesian language.
• Bug correction: nav menu locations are lost when using the admin language filter.

What is new in version 1.1.3:

• Added Venetian language contributed
• Bug correction: wrong rewrite rules for non translated custom post type archives
• Bug correction: 'post_id' parameter of pll_the_languages does not work
• Bug correction: warning in wp_nav_menu_objects with Artisteer generated themes
• Bug correction: warning when used together with theme my login plugin

What is new in version 1.1.1:

• Add the filter 'pll_redirect_home'
• Automatically translate ids in 'include' argument of 'get_terms' (useful for the menus in the Suffusion theme)
• Add compatibility with Jetpack infinite scroll
• Bug correction: rtl text direction not set when adding the language code to all urls (introduced in 1.1)
• Bug correction: hide again navigation panel in theme customizer as it still doesn't work
• Bug correction: is_home not set on translated page when searching an empty string
• Bug correction: fatal error when creating a post or term from frontend (introduced in 1.1)
• Bug correction: attachments may load a wrong language when media translation was enabled then disabled
• Bug correction: warning when querying posts before the action 'wp_loaded' has been fired (in auto-translate.php)
• Bug correction: potential issue if other plugins use the filter 'get_nav_menu'
• Bug correction: interference between language inline edit and search in admin list tables
• Bug correction: auto-translate breaks queries tax_query when the 'field' is set to 'id'
• Bug correction: search is not filtered by language for default permalinks (introduced in 1.1)

What is new in version 1.1:

• When querying posts and terms, ids are now automatically translated
• Add the possibility to group string translations
• Add the possibility to delete strings registered with 'icl_register_string'
• Move the option 'polylang_widgets' in general polylang options
• Better integration of the multilingual nav menus (everything is now integrated in the menus page of WordPress
• The language switcher is now a menu item which can be placed everywhere in a nav menu
• Posts or terms created from frontend are now assigned the current language (or another one if specified in the variable 'lang')
• Bug correction: continents-cities-xx_XX.mo not downloaded
• Bug correction: a gzipped 404 page is downloaded when a mo file does not exist on WordPress languages files repository
• Bug correction: post_date_gmt not synchronized together with post_date (can break Jetpack infinite scroll)

What is new in version 1.0.3:

• Added the possibility to create a custom wpml-config.xml file in wp-content/polylang/
• Bug correction: custom menus are not displayed on search page (introduced in 1.0.2)
• Bug correction: sql error when filtering terms by language (introduced in 1.0.2)
• Bug correction: SSL doesn't work properly
• Bug correction: php notice on IIS servers
• Bug correction: clicking on the radio buttons in the admin language switcher does not work in Chrome
• Bug correction: on multisite, the signup page is redirected to the home page
• Bug correction: date archives are not correctly filtered for the default language when hiding the language code and using date and name permalinks
• Bug correction: only one wpml-config.xml file is parsed

What is new in version 1.0.2:

• Add the possibility to query comments by language
• Add the possibility not to set a cookie by defining PLL_COOKIE to false (Polylang may not work as expected on some pages)
• Now a returning visitor is redirected to its preferred language when visiting the front page in the default language
• Add compatibility with the plugin Custom field template (copy and synchronize custom fields)

What is new in version 1.0.1:

• Added 2 new API functions : 'pll_is_translated_post_type' and 'pll_is_translated_taxonomy'.
• Bug correction: when using a static front page, the posts page is not filtered by language (introduced in 1.0).
• Bug correction: disable translation for hard coded menu as it creates more problems than it solves (introduced in 1.0).

What is new in version 0.9.7:

• Bug correction: the admin language filter does filter non translatable post types
• Bug correction: again the canonical redirection
• Bug correction: fatal error when Polylang is used together with 'Author Avatars List'
• Bug correction: widget titles uselessly appear in the strings translations table when the widget is set for only one language

What is new in version 0.9.5:

• The user can now choose the number of languages and strings translations to display
• Added compatibility with the 'icl_object_id' function and ICL_LANGUAGE_CODE and ICL_LANGUAGE_NAME constants from the WPML API
• Add 17 languages to the predefined list (automatic download and update of language files won't work)

What is new in version 0.9.3:

• Add Bulgarian translation.
• Add compatibility with WPML API for strings translations.
• Bug correction: dates are not translated (introduced in 0.9.2).

What is new in version 0.9.2:

• Support new WordPress (WP 3.5+) convention for js and css files naming
• Improve performance, mainly on frontend
• Bug correction: the category language is not set when creating it in the post editor (introduced in 0.9)
• Bug correction: unable to add a query string when using a static front page
• Bug correction: ajax tag suggestion in "edit post" conflicts with the admin content language filter
• Bug correction: ugly notices when trying to access a static front page which has not been translated
• Bug correction: the language code is added to custom post types and taxonomies permalinks even if they are not translatable

What is new in version 0.9:

• Add media translation support
• Add a persistant content language filter on admin side (WP 3.2+ required)
• Add biographical info translation
• Add multiline support for string translations
• Add the possibility to clean the strings translation database
• Add quick edit and bulk edit support for posts and pages
• Add quick edit support for categories and tags

What is new in version 0.8.10:

• Bug correction: empty string translation issue
• Bug correction: 'wp_list_pages' does not filter custom post types
• Bug correction: warning if posts are queried before the action 'wp_loaded' has been fired
• Bug correction: notice in twentyten when resquesting a date archive with no posts

What is new in version 0.8.9:

• Added Portuguese translation.

What is new in version 0.8.7:

• Add ta_LK to predefined languages list
• Bug correction: search form is broken when using a static front page
• Bug correction: admin bar search does not work
• Tests done with WordPress 3.4 RC2

What is new in version 0.8.6:

• Improve robustness (less PHP notices)
• Bug correction: Menus not showing in preview mode
• Bug correction: fatal error when customizing a theme in WP 3.4 beta 4
• Bug correction: second page of search results returns 404 when using pretty permalinks

What is new in version 0.8.5:

• Bug correction : sites using static front page are messed in v0.8.4.

What is new in version 0.8.3:

• Added Danish translation
• Added Spanish translation
• Added the possibility to add a content in a different language than the current one by setting explicitely the lang parameter in the secondary query
• Added support of PATHINFO permalinks
• Bug correction: secondary queries not correctly filtered by language
• Bug correction: wrong archives links when using permalinks with front

What is new in version 0.7.2:

• Add Polish translation.
• Add 5 new languages to predefined list.

Requirements:

• WordPress 3.1 or higher