Polylang

Opis

Features

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.

  • You can use as many languages as you want. RTL language scripts are supported. WordPress languages packs are automatically downloaded and updated.
  • You can translate posts, pages, media, categories, post tags, menus, widgets…
  • Custom post types, custom taxonomies, sticky posts and post formats, RSS feeds and all default WordPress widgets are supported.
  • 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
  • Categories, post tags as well as some other metas are automatically copied when adding a new post or page translation
  • A customizable language switcher is provided as a widget or in the nav menu

The author does not provide support on the wordpress.org forum. Support and extra features are available to Polylang Pro users.

If you wish to migrate from WPML, you can use the plugin WPML to Polylang

If you wish to use a professional or automatic translation service, you can install 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).

Credits

Thanks a lot to all translators who help translating Polylang.
Thanks a lot to Alex Lopez for the design of the logo.
Most of the flags included with Polylang are coming from famfamfam and are public domain.
Wherever third party code has been used, credit has been given in the code’s comments.

Do you like Polylang?

Don’t hesitate to give your feedback.

Zrzuty ekranów

  • The Polylang languages admin panel
  • The Strings translations admin panel
  • Multilingual media library
  • The Edit Post screen with the Languages metabox

Instalacja

  1. Make sure you are using WordPress 4.9 or later and that your server is running PHP 5.6 or later (same requirement as WordPress itself)
  2. If you tried other multilingual plugins, deactivate them before activating Polylang, otherwise, you may get unexpected results!
  3. Install and activate the plugin as usual from the ‚Plugins’ menu in WordPress.
  4. Go to the languages settings page and create the languages you need
  5. Add the ‚language switcher’ widget to let your visitors switch the language.
  6. 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 or ask the theme author to internationalize it.

FAQ

Where to find help ?

Is Polylang compatible with WooCommerce?

  • You need a separate addon to make Polylang and WooCommerce work together. A Premium addon is available.

Do you need translation services?

  • If you want to use professional or automatic translation services, install and activate the Lingotek Translation plugin.

Recenzje

30 czerwca 2020
Excellent transition software, very comprehensive. Nonetheless, I found out two behaviors that are not pretty good. 1. From time to time site switch from one language (default Spanish in my case) to English. No consistent anyway, to reproduce and isolate. 2. I use modal survey plugin for surveys and quizzes but, although all the strings are properly translated, It does not switch them automatically in my website. So, need to keep quizzed done in both languages :(. Besides this, kudos for the creators
30 czerwca 2020
Polylang elegantly provides the missing multilingual support that always should have been part of the WordPress base software. Just enough and not too much.
Przeczytaj 1 575 recenzji

Kontrybutorzy i deweloperzy

„Polylang” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki.

Zaangażowani

Wtyczka “Polylang” została przetłumaczona na 38 języków. Podziękuj tłumaczom za ich wkład.

Przetłumacz wtyczkę “Polylang” na swój język.

Interesuje cię rozwój wtyczki?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Log zmian

2.7.4 ( 2020-06-29)

  • Pro: Allow using our /untranslated-posts REST endpoint for non-public post types
  • Pro: Fix broken display in the block editor sidebar when a language has no flag
  • Pro: Fix SSO breaking the preview on secondary domains
  • Pro: Fix ACF translation option not working for term custom fields
  • Pro: Fix a styling issue in the fields group list table in ACF 5.9
  • Add Spanish from Puerto Rico to the predefined list of languages

2.7.3 (2020-05-26)

  • Security: Slash metas
  • Pro: Fix categories not savedafter the language has been switched in the block editor
  • Pro: Fix ACF fields stored as integers instead of strings
  • Pro: Fix ACF untranslated posts or terms being copied when creating a new translation
  • Pro: Fix PHP notice with ACF when a repeater or group is included in a flexible content
  • Pro: Fix „DevTools failed to load SourceMap” warning in browser console
  • Update plugin updater to 1.7.1
  • Honor the filter „pll_the_language_link” when the language switcher displays a dropdown #506
  • Fix „Something went wrong” message when quick editing untranslated post types #508
  • Fix wpseo_opengraph deprecated warning #509

2.7.2 (2020-04-27)

  • Pro: Re-allow to modify the capability for strings translations
  • Pro: Fix redirect for posts having the same slug as a media
  • Pro: Fix PHP notice with ACF flexible content
  • Pro: Fix a fatal error with InfiniteWP
  • Update plugin updater to 1.7
  • Fix font in setup wizard

2.7.1 (2020-04-09)

  • Pro: Fix untranslated post types filtered by the parameter in the REST API #493
  • Fix fatal error when the function idn_to_ascii is not available
  • Fix PHP warning warning when a 3rd party plugin declares options not stored in DB in wpml-config.xml #492
  • Fix fatal error when a 3rd party plugin declares options stored as objects in wpml-config.xml #494

2.7 (2020-04-06)

  • Minimum WordPress version is now 4.9
  • Pro: Strings translations can now be exported and imported (in PO format)
  • Pro: Allow to decide individually which ACF fields to copy or synchronize
  • Pro: Add action pll_inactive_language_requested
  • Pro; Fix fatal error in The Events Calendar compatibility when no language is defined yet
  • Pro: Fix bulk translate when a post has no language
  • Pro: Fix reusable block saved without language
  • Pro: Fix post requested by slug not filtered in REST API, when the slug is shared
  • Add a setup wizard
  • Add Swahili, Upper Sorbian, Sindhi and Spanish from Uruguay to the list of predefined languages
  • Add flags in the predefined list of languages
  • Allow to hide the metaboxes from the screen options
  • The deletion of the plugin’s data at uninstall is now controlled by a PHP constant instead of an option #456
  • Add parent in ajax response when selecting a term in autocomplete field #328
  • Add Vary: Accept-Language http header in home page redirect. Props @chesio #452
  • Improve performance to register/unregister WPML strings
  • Add support for the action wpml_switch_language
  • Add post_status to the list of accepted args of pll_count_posts()
  • Apply the filter pll_preferred_language in wp-login.php
  • Use filtered wrappers to create meta when creating media translations #231
  • Allow to translate the Twenty Seventeen header video Youtube url #460
  • Notices are now dismissed per site instead of per user #478
  • Fix terms not visible in the quick edit when only one language is defined and teh admin language filter is active
  • Fix post state not displayed for translations of the privacy policy page #395
  • Fix wildcards not correctly interpreted in wpml-config.xml
  • Fix product categories with special characters duplicated when importing WooCommerce products #474

See changelog.txt for older changelog