Polylang

Beskrivning

Funktioner

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.

Skärmdumpar

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

Installation

  1. Se till att du använder WordPress 4.7 eller senare och att din server kör PHP 5.2.4 eller senare (samma krav som WordPress själv)
  2. Om du provat andra språktillägg, avaktivera dem innan du aktiverar Polylang. Annars kan du få oväntade resultat!
  3. Install and activate the plugin as usual from the ’Plugins’ menu in WordPress.
  4. Gå till ”Språk” under ”Inställningarna” och skapa de språk du behöver
  5. Lägg till widgeten ”Språkväljaren” för att kunna göra det möjlig för dina besökare att byta språk.
  6. Se till att ditt tema innehåller motsvarande .mo-filer (Polylang hämtar dem för teman och tillägg som levereras via WordPress). Om ditt tema ännu inte är förberett för översättning ber vi dig studera Temahandboken, eller kontakta temats författare och be dem anpassa temat för översättning.

Vanliga frågor

Var hittar man hjälp?
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?
  • Om du vill använda professionell, eller automatisk översättningstjänst, installera och aktivera tillägget Lingotek Translation.

Recensioner

Läs alla 773 betyg

Bidragsgivare och utvecklare

”Polylang” är programvara med öppen källkod. Följande personer har bidragit till detta tillägg.

Bidragande personer

”Polylang” har översatts till 30 språk. Tack till översättarna för deras bidrag.

Översätt ”Polylang” till ditt språk.

Intresserad av programutveckling?

Läs programkoden, kika på SVN-filförvaret eller prenumerera på utvecklarloggen via RSS.

Ändringslogg

2.5.1 (2018-01-16)

  • Security: Fix categories and media duplication not protected from CSRF
  • Pro: Allow to update the plugin with WP CLI
  • Pro: Fix search in the button block not filtered in the correct language (needs WP 5.1)
  • Add Saraiki to the predefined languages list
  • Fix a conflict causing a blank page with Divi

2.5 (2018-12-06)

  • Add compatibility with WP 5.0
  • Fix custom flags when the WP content folder is not in the WP install folder
  • Fix PHP notice if a language has no flag

2.4.1 (2018-11-27)

  • Pro: Add compatibility with REST API changes made in WP 5.0
  • Pro: Fix sticky posts in the REST API
  • Pro: Fix overwritten custom post slug when the post is updated with the REST API
  • Pro: Fix bulk translate for media
  • Fix a conflict with Custom sidebars and Content aware sidebars
  • Fix a conflict with the theme Pokemania
  • Fix PHP notices when using the function ’icl_link_to_element’ for terms
  • Fix title slugs for posts written in German

2.4 (2018-11-12)

  • Minimum WordPress version is now 4.7
  • Pro: Add the possibility to bulk duplicate or bulk synchronize posts.
  • Pro: Add compatibility with Admin Columns
  • Pro: Add synchronized posts to the REST API
  • Pro: Fix variations messed when changing WooCommerce attributes slugs
  • Pro: Fix incorrect language for ajax requests made on front by The Events Calendar
  • Pro: Fix term not duplicated correctly when the language is set from the content
  • Refactor the core to activate on front and for the REST api actions that were previously available only in the backend (language checks, synchronizations…).
  • Add flags to widgets displayed in only one language (Props Jory Hogeveen) #257
  • Honor the filter ’pll_the_language_args’ for all options in menus #237
  • Add better filters for default flags and custom flags
  • Custom flags can now be stored in the polylang directory in the theme
  • Custom flags can now use SVG
  • Add compatibility with Jetpack featured content module
  • Fix Twenty Fourteen featured posts possibly not filtered per language
  • Fix home url not working with WordPress MU Domain mapping
  • Fix Assigning a parent category breaking the hierarchy of translated category
  • Fix: Accept 0,1 and 1.0 as q factors in browser preferred language detection (Props Dominic Rubas)
  • Fix performance issue when using hundreds of widgets
  • Fix translations possibly wrong if the post language is changed without saving the post after

See changelog.txt for older changelog