| 1 |
=== Polylang === |
| 2 |
Contributors: Chouby |
| 3 |
Donate link: https://polylang.pro |
| 4 |
Tags: multilingual, bilingual, translate, translation, language, multilanguage, international, localization |
| 5 |
Requires at least: 4.0 |
| 6 |
Tested up to: 4.7 |
| 7 |
Stable tag: 2.0.12 |
| 8 |
License: GPLv2 or later |
| 9 |
|
| 10 |
Making WordPress multilingual |
| 11 |
|
| 12 |
== Description == |
| 13 |
|
| 14 |
= Features = |
| 15 |
|
| 16 |
Polylang allows you to create a bilingual or multilingual WordPress site. You write posts, pages and create categories and post tags as usual, and then define the language for each of them. The translation of a post, whether it is in the default language or not, is optional. |
| 17 |
|
| 18 |
* You can use as many languages as you want. RTL language scripts are supported. WordPress languages packs are automatically downloaded and updated. |
| 19 |
* You can translate posts, pages, media, categories, post tags, menus, widgets... |
| 20 |
* Custom post types, custom taxonomies, sticky posts and post formats, RSS feeds and all default WordPress widgets are supported. |
| 21 |
* The language is either set by the content or by the language code in url, or you can use one different subdomain or domain per language |
| 22 |
* Categories, post tags as well as some other metas are automatically copied when adding a new post or page translation |
| 23 |
* A customizable language switcher is provided as a widget or in the nav menu |
| 24 |
* The admin interface is of course multilingual too and each user can set the WordPress admin language in its profile |
| 25 |
|
| 26 |
> The author does not provide support on the wordpress.org forum. Support and extra features are available to [Polylang Pro](https://polylang.pro) users. |
| 27 |
|
| 28 |
If you wish to migrate from WPML, you can use the plugin [WPML to Polylang](https://wordpress.org/plugins/wpml-to-polylang/) |
| 29 |
|
| 30 |
If you wish to use a professional or automatic translation service, you can install [Lingotek Translation](https://wordpress.org/plugins/lingotek-translation/), as an addon of Polylang. Lingotek offers a complete translation management system which provides services such as translation memory or semi-automated translation processes (e.g. machine translation > human translation > legal review). |
| 31 |
|
| 32 |
= Credits = |
| 33 |
|
| 34 |
Thanks a lot to all translators who [help translating Polylang](https://translate.wordpress.org/projects/wp-plugins/polylang). |
| 35 |
Thanks a lot to [Alex Lopez](http://www.alexlopez.rocks/) for the design of the banner and the logo. |
| 36 |
Most of the flags included with Polylang are coming from [famfamfam](http://famfamfam.com/) and are public domain. |
| 37 |
Wherever third party code has been used, credit has been given in the code’s comments. |
| 38 |
|
| 39 |
= Do you like Polylang? = |
| 40 |
|
| 41 |
Don't hesitate to [give your feedback](http://wordpress.org/support/view/plugin-reviews/polylang#postform). |
| 42 |
|
| 43 |
== Installation == |
| 44 |
|
| 45 |
1. Make sure you are using WordPress 4.0 or later and that your server is running PHP 5.2.4 or later (same requirement as WordPress itself) |
| 46 |
1. If you tried other multilingual plugins, deactivate them before activating Polylang, otherwise, you may get unexpected results! |
| 47 |
1. Install and activate the plugin as usual from the 'Plugins' menu in WordPress. |
| 48 |
1. Go to the languages settings page and create the languages you need |
| 49 |
1. Add the 'language switcher' widget to let your visitors switch the language. |
| 50 |
1. Take care that your theme must come with the corresponding .mo files (Polylang automatically downloads them when they are available for themes and plugins in this repository). If your theme is not internationalized yet, please refer to the [Theme Handbook](https://developer.wordpress.org/themes/functionality/internationalization/) or ask the theme author to internationalize it. |
| 51 |
|
| 52 |
== Frequently Asked Questions == |
| 53 |
|
| 54 |
= Where to find help ? = |
| 55 |
|
| 56 |
* First time users should read [Polylang - Getting started](https://polylang.pro/doc-category/getting-started/), which explains the basics with a lot of screenshots. |
| 57 |
* Read the [documentation](https://polylang.pro/doc/). It includes a [FAQ](https://polylang.pro/doc-category/faq/) and the [documentation for developers](https://polylang.pro/doc-category/developers/). |
| 58 |
* Search the [community support forum](https://wordpress.org/search/). You will probably find your answer here. |
| 59 |
* Read the sticky posts in the [community support forum](http://wordpress.org/support/plugin/polylang). |
| 60 |
* If you still have a problem, open a new thread in the [community support forum](http://wordpress.org/support/plugin/polylang). |
| 61 |
* [Polylang Pro](https://polylang.pro) users have access to our helpdesk. |
| 62 |
|
| 63 |
= Is Polylang compatible with WooCommerce? = |
| 64 |
|
| 65 |
* You need a separate addon to make Polylang and WooCommerce work together. [A Premium addon](https://polylang.pro/downloads/polylang-for-woocommerce/), currently in beta stage, is available. |
| 66 |
|
| 67 |
= Do you need translation services? = |
| 68 |
|
| 69 |
* If you want to use professional or automatic translation services, install and activate the [Lingotek Translation](https://wordpress.org/plugins/lingotek-translation/) plugin. |
| 70 |
|
| 71 |
== Screenshots == |
| 72 |
|
| 73 |
1. The Polylang languages admin panel |
| 74 |
2. The Strings translations admin panel |
| 75 |
3. Multilingual media library |
| 76 |
4. The Edit Post screen with the Languages metabox |
| 77 |
|
| 78 |
== Changelog == |
| 79 |
|
| 80 |
= 2.0.12 (2016-12-19) = |
| 81 |
|
| 82 |
* Fix plugin not loaded first (introduced in 2.0.11) |
| 83 |
* Fix wrong translations files loaded when the language is set from the content in WP 4.7 #76 |
| 84 |
* Fix notice when a tax query has no terms (using EXISTS or NOT EXISTS) |
| 85 |
|
| 86 |
= 2.0.11 (2016-12-12) = |
| 87 |
|
| 88 |
* Pro: Fix shared term slugs broken by a late change in WP 4.7 #73 |
| 89 |
* Pro: Fix media taxonomies lost when creating a media translation when taxonomies sync is activated #72 |
| 90 |
* Fix fatal error in customizer when Twenty Seventen is activated and another theme is previewed #71 |
| 91 |
* Fix wrong plugin language on admin if user locale is different from site locale in WP 4.7 |
| 92 |
|
| 93 |
= 2.0.10 (2016-12-05) = |
| 94 |
|
| 95 |
* Add support for front page panels of Twenty Seventeen |
| 96 |
* Remove draft posts from the language switcher even when the user is logged in |
| 97 |
* Fix: Make argument 2 of icl_object_id optional |
| 98 |
* Fix a conflict with the Divi theme (#67) |
| 99 |
|
| 100 |
= 2.0.9 (2016-11-15) = |
| 101 |
|
| 102 |
* Fix javascript error in some ajax requests |
| 103 |
|
| 104 |
= 2.0.8 (2016-11-14) = |
| 105 |
|
| 106 |
* Disable admin language feature in WP 4.7+ |
| 107 |
* Pro: fix case where a media could lose its parent post when translated on the fly by the content duplication |
| 108 |
* Pro: fix on the fly media created at content duplication attached to parent page instead of child page |
| 109 |
* Fix translations input fields not populated in languages metabox when creating a new translation in WP 4.7 |
| 110 |
* Fix possibility to delete the translations of the default category in WP 4.7 |
| 111 |
* Fix tag search not filtered per language in Quick edit in WP 4.7 |
| 112 |
* Fix dropdown language switcher not working for untranslated pages |
| 113 |
|
| 114 |
= 2.0.7 (2016-10-18) = |
| 115 |
|
| 116 |
* Fix issues with static front pages introduced in version 2.0.6 |
| 117 |
|
| 118 |
= 2.0.6 (2016-10-17) = |
| 119 |
|
| 120 |
* Pro: Fix translated paged slug not working on paged static front page |
| 121 |
* Add support for WPML filter 'wpml_language_form_input_field' |
| 122 |
* Fix PHP notice when using the WPML filter 'wpml_current_language' |
| 123 |
* Fix cases where the admin language filter is not correctly taken into account |
| 124 |
* Fix paged static front pages in plain permalinks |
| 125 |
* Fix paged static front pages for multiple domains (#43) |
| 126 |
* Fix warning occuring when a 3rd party plugin attempts to register anything but a string in the strings translations panel |
| 127 |
* Fix cross domain http request for media when using multiple domains or subdomains |
| 128 |
* Fix error 404 on pages when no language has been created yet |
| 129 |
|
| 130 |
= 2.0.5 (2016-09-22) Five years after! = |
| 131 |
|
| 132 |
* Pro: Fix conflict with WPBakery Visual Composer |
| 133 |
* Pro: Fix conflict between multiple domains SSO and FORCE_SSL_ADMIN |
| 134 |
* Pro: Fix duplicated fields not displayed in new translation in ACF Pro 5.4+ |
| 135 |
* Add Tibetan and Silesian to the predefined languages list |
| 136 |
* Remove duplicated strings from the strings translations (even when they have a different name or group) |
| 137 |
* The languages and translations of custom post types and taxonomies are no more activated by default at activation |
| 138 |
* Allow to deactivate auto translation in secondary by setting 'lang' to an empty value |
| 139 |
* Fix: invalidate the cache of PLL_MO ids when adding a new language |
| 140 |
* Fix: don't filter secondary queries when editing a post in an untranslated post type |
| 141 |
|
| 142 |
= 2.0.4 (2016-09-06) = |
| 143 |
|
| 144 |
* Add Gujarati to the predefined languages list |
| 145 |
* Fix conflict with Page Builder. Other parts of the conflict are fixed in Page Builder 2.4.14 |
| 146 |
* Fix plugins translations incorrectly loaded in WP 4.6 |
| 147 |
* Fix error 404 on paged urls when using a non standard port |
| 148 |
|
| 149 |
= 2.0.3 (2016-08-16) = |
| 150 |
|
| 151 |
* Pro: Fix PHP notice when hiding the language code in url and the language is set from subdomains |
| 152 |
* Pro: Fix one more media being created when the duplicate media in all languages is activated (introduced in 2.0) |
| 153 |
* Pro: Fix shared term slugs not working on PHP 7 |
| 154 |
* Pro: Fix Polylang storing integers in some ACF Pro fields where ACF Pro stores strings |
| 155 |
* Pro: Fix ACF Pro custom fields synchronized even when the custom fields synchronization option is deactivated (#40) |
| 156 |
* Fix PHP notice: Undefined variable: original_value in /modules/wpml/wpml-api.php on line 168 |
| 157 |
* Fix translations loaded too soon by plugins not correctly reloaded since WP 4.6 (#39) |
| 158 |
* Fix: Remove the delete link for translations of the default category on PHP 7 |
| 159 |
* Fix unescaped i18n strings in Lingotek presentation |
| 160 |
|
| 161 |
= 2.0.2 (2016-08-03) = |
| 162 |
|
| 163 |
* Avoid fatal error when a 3rd party theme or plugin has a malformed wpml-config.xml file: the malformed wpml-config.xml file is simply ignored |
| 164 |
|
| 165 |
= 2.0.1 (2016-08-02) = |
| 166 |
|
| 167 |
* Fix fatal error on PHP < 5.4 (introduced in 2.0) |
| 168 |
* Fix custom flags not being loaded (introduced in 2.0) |
| 169 |
|
| 170 |
= 2.0 (2016-08-02) = |
| 171 |
|
| 172 |
* Pro: Improve integration with ACF Pro |
| 173 |
* Pro: Add support for single sign on across multiple domains or subdomains |
| 174 |
* Pro: Add support for browser language detection when using multiple domains |
| 175 |
* Pro: Add support for translation of the static portion of the post permalink structure |
| 176 |
* Pro: Fix deactivated languages appearing in Yoast SEO sitemaps |
| 177 |
* Pro: Fix impossibility to visit a deactivated language when using subdomains or multiple domains (#10) |
| 178 |
* Pro: Fix when sharing slug on the page for posts, only one of them is accessible (#33) |
| 179 |
* Add the possibility to use the language switcher as dropdown in menu |
| 180 |
* Add support for custom logo introduced in WP 4.5 (#6) |
| 181 |
* The backend current language ( PLL()->curlang ) is now equal to the language of current post or term being edited (#19) |
| 182 |
* The sample permalink is now updated when changing the language in the Languages metabox |
| 183 |
* Revamp the wpml-config.xml reader to use simplexml instead of our custom xml parser |
| 184 |
* Improve support for the WPML API (including Hook API introduced in WPML 3.2) |
| 185 |
* Add support for translation of meta titles and descriptions of custom post types and custom taxonomies in Yoast SEO |
| 186 |
* Replace uncached functions by WPCOM VIP functions when available |
| 187 |
* Improve compatibility with WP 4.6 |
| 188 |
* Fix parent category wrongly assigned to post when synchronizing children categories (#21) |
| 189 |
* Fix custom fonts not loaded when using multiple domains or subdomains |
| 190 |
* Fix remove_accents() not working for German and Danish (#24) |
| 191 |
* Fix incorrect static front pages urls on backend |
| 192 |
* Fix impossible to directly enter the page number in strings translation table (introduced in 1.9.3) |
| 193 |
* Fix conflict with WP Sweep (needs WP Sweep 1.0.8+) |
| 194 |
* Fix potential performance issue by querying only taxonomies to show in quick edit to filter the category checklist |
| 195 |
* Fix conflict (database error) with ReOrder-posts-within-categories plugin |
| 196 |
* Fix languages per page option not saved |
| 197 |
|
| 198 |
See [changelog.txt](https://plugins.svn.wordpress.org/polylang/trunk/changelog.txt) for older changelog |
| 199 |
|
