Image
Image

Polylang

Beskrivelse

Med Polylang fuldt integreret i WordPress og kun ved hjælp af dets indbyggede kernefunktioner (taksonomier), kan du opretholde en stabil ydelse på dit websted og oprette et flersproget websted med fra kun et ekstra sprog til 10 eller mere afhængigt af dine behov. Der er ingen grænse i antallet af tilføjede sprog, og WordPress’ sprogpakker downloades automatisk, når de er klar.

Funktioner

Afhængigt af hvilken type websted du har bygget eller planlægger at bygge, kan en kombination af plugins fra listen nedenfor være af interesse.
Alle plugins inkluderer en guide, der gør det muligt at opsætte dem med blot et par klik.

Polylang

Polylang og Polylang Pro deler den samme kerne, der leverer funktioner såsom:

  • Oversættelse af indlæg, sider, medier, kategorier, indlægstags, egne indlægstyper og taksonomier, RSS-feeds; RTL-scripts understøttes.
  • Sproget angives enten af sprogkoden i URL-adressen, eller du kan bruge et andet underdomæne eller domæne pr. sprog.
  • Automatisk kopi af kategorier, indlægstags og andre metaer, når du opretter et nyt indlæg eller sideoversættelse.
  • Oversætte klassiske menuer og klassiske widgets. Kan også bruges med Site Editor Classic Features i bloktemaer.
  • Sprogskifter, der kan tilpasses, tilgængelig som en widget eller et navigationsmenupunkt.
  • Kompatibilitet med Yoast SEO.

Polylang Pro

Hjælper med at optimere den tid, der bruges på at oversætte dit websted med nogle meget nyttige ekstrafunktioner såsom:

  • Bedre integration i den nye blokeditor.
  • Sprogskifter tilgængelig som en blok.
  • Sprogindstillinger tilgængelige i widgetblokeditoren.
  • Skabelondele, der kan oversættes i webstedseditoren (FSE).
  • Dupliker og/eller synkronisere indhold på tværs af indlægsoversættelser.
  • Forbedret kompatibilitet med andre plugins såsom ACF Pro.
  • Del det samme URL-kortlink for indlæg eller udtryk på tværs af sprog.
  • Oversæt URL-kortlink til kategorier, forfatterbaser, egne indlægstyper og mere…
  • Maskinoversættelse med DeepL.
  • Eksport og import af indhold i XLIFF-format til outsourcet professionel oversættelse.
  • Adgang til Premium Support for personlig assistance.

Polylang til WooCommerce

Add-on til kompatibilitet med WooCommerce, som giver funktioner såsom:

  • Oversættelse af WooCommerce-sider (butik, kasse, indkøbskurv, min konto), produktkategorier og globale attributudtryk direkte i WooCommerce-grænsefladen.
  • Oversættelse af WooCommerce e-mails og afsendelse af dem til kunder på deres sprog.
  • Synkronisering af produktmetadata.
  • Kompatibilitet med det oprindelige WooCommerce CSV import- og eksportværktøj.
  • Kompatibilitet med populære plugins som WooCommerce Subscribtions, Product Bundles, WooCommerce Bookings, Shipment Tracking og mere.
  • Mulighed for at bruge WooCommerce REST API (tilgængelig med Polylang Pro).
  • Adgang til Premium Support for personlig assistance.

Vores andre gratis plugins

Krediteringer

Mange tak til alle oversættere, der hjælper med at oversætte Polylang.
Mange tak til Alex Lopez for designet af logoet.
De fleste af de flag, der følger med Polylang, kommer fra famfamfam og er offentligt eje.
Hvor tredjepartskode er blevet brugt, er der givet kreditering i kodens kommentarer.

Skærmbilleder

  • Image
    Polylang administrationspanel for sprog
  • Image
    Administrationspanelet Oversættelse af strenge
  • Image
    Flersproget mediebibliotek
  • Image
    Skærmbilledet Rediger indlæg med metafeltet Sprog

Installation

  1. Sørg for, at du bruger WordPress 6.2 eller nyere, og at din server kører PHP 7.2 eller nyere (samme krav som WordPress selv).
  2. Hvis du her prøvet andre flersprogede plugins, skal du deaktivere dem, før du aktiverer Polylang, ellers kan du få uventede resultater!
  3. Installer og aktiver pluginet som normalt fra menuen ‘Plugins’ i WordPress.
  4. The setup wizard is automatically launched to help you get started more easily with Polylang by configuring the main features.

FAQ

Hvor kan man finde hjælp?

Er Polylang kompatibel med WooCommerce?

Where do I report security bugs found in this plugin?

  • Please report security bugs found in the source code of the Polylang plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.

Anmeldelser

Image
11. januar, 2026
Once I had understood how to link 2 languages through the plugin, each article needing to be written prior to be able to do it, then it worked flawlessly, and had been working that smooth since I installed it.I do use plugins to disable Gutenberg, on multi-sites (some with subsites and some with sub-domains), and even so, it works without a hickup. (I do not activate it for the whole network, however, only where it is needed).
Image
2. januar, 2026
I’ve been using Polylang for a while now. No problem so far, works well for my bilingual blog.
Image
23. december, 2025
I raised serious concerns and a refund request only two days after purchasing Polylang Pro. Despite this early feedback and the fact that the plugin was tested exclusively in a staging environment, the refund was refused and the discussion was immediately pushed toward internal terms and conditions. This set the tone for the entire experience. Polylang Pro is marketed as a professional multilingual solution with DeepL integration. Based on the product presentation, it creates the expectation of a relatively smooth, integrated, and efficient workflow for automatic translations. In practice, however, the setup is far more complex and fragmented than implied. The translation workflow requires multiple additional steps, external configurations, and ongoing third-party costs that are not made sufficiently clear before purchase. Under more serious load, especially when translating larger amounts of text or content containing more complex structures or code, the DeepL connection frequently fails. Translation processes interrupt, errors appear, and the workflow breaks down entirely. This makes the promised automation unreliable in real-world scenarios where volume and consistency actually matter. The gap between the marketing message and real-world usability is significant. What is presented as a professional, streamlined solution feels instead like a technically heavy system that demands substantial time investment just to reach a basic, workable state. Even more disappointing than the product itself was the support experience. When I raised legitimate concerns shortly after purchase, the responses were dismissive and heavily policy-driven. Instead of engaging with the substance of the issues, the communication relied on hiding behind general terms and conditions, avoiding any real responsibility for the mismatch between expectations and reality. The overall tone and behavior from support were off-putting and frustrating. For a plugin positioned toward professional users, this lack of transparency, flexibility, and accountability is unacceptable. This experience left me with the clear impression that once payment is made, customer feedback about real-world usability, stability, and reliability is not taken seriously. This is not about the price. The amount itself is irrelevant. What matters is trust, honest presentation, and professional handling of early customer concerns. Based on the refusal to issue a refund shortly after purchase, the instability of the DeepL integration under load, the misleading expectations created by the product presentation, and the disappointing support interaction, I will not use Polylang Pro again and I do not recommend it to anyone.
Læs alle 2.891 anmeldelser

Bidragsydere & udviklere

“Polylang” er open source-software. Følgende personer har bidraget til dette plugin.

Bidragsydere

“Polylang” er blevet oversat til 54 sprog. Tak til oversætterne for deres bidrag.

Oversæt “Polylang” til dit eget sprog.

Interesseret i udvikling?

Gennemse koden, tjek SVN repository, eller abonner på udviklerloggen via RSS.

Ændringslog

3.7.6 (2026-01-06)

  • Pro: Add support for WP 6.9 new blocks #2790
  • Pro: Fix insertion of navigation language switcher block in WP 6.9 #2847
  • Pro: Fix current post URL in site editor for WP 6.8+ #2843
  • Pro: Fix a conflict with Sensei LMS #2845
  • Fix categories not filtered per post language in quick edit #1785

3.7.5 (2025-11-10)

  • Pro: Updated DeepL supported languages list
  • Pro: Fix a regression in cross domain login
  • Pro: Fix post object field not correctly translated
  • Pro: Fix a fatal error in EDD plugin updater when the request to the server fails
  • Pro: Fix locale fallback in WP 6.8+
  • Pro: Add pll_enable_acf_labels_translation filter allowing to disable the translation of ACF labels
  • Pro: Fix ACF image field not correctly translated when media translation is active
  • Pro: Fix ACF image field in repeater not copied
  • Pro: Fix ACF ajax request unexpectedly filtered by language when editing a field group
  • Pro: Fix ACF blocks not translated when included inside a non-ACF block
  • Pro: Add compatibility of the duplicate tool with Divi
  • Fix Undefined array key “terms” in canonical.php #1691
  • Fix some regressions in the WPML API used by YITH WooCommerce Wishlist #1684
  • Fix LinkedIn site title preview with Yoast SEO #1686
  • Fix HTML language attribute on login page #1601
  • Fix conflict with WP Job Manager Application #1749

3.7.4 (2025-10-28)

  • Pro: Security: Fix a ReDoS vulnerability reported by Janine Moreira.
  • Security: Fix deserialization of untrusted data reported by Phat RiO – BlueRock via Patchstack.

3.7.3 (2025-06-16)

  • Pro: Always display ACF translation settings for field groups formerly translated in versions older than 3.7
  • Pro: Fix translation displayed in child fields of ACF layout fields when they should not
  • Pro: Fix translation of the ACF field “Choice” when the translation is set to “Copy once” or “Synchronize”
  • Pro: Fix a PHP warning when translating some blocks
  • Pro: Fix impossibility to change the language of an empty post in the block editor
  • Fix duplicate values in options #1672
  • Fix JS error in media library (grid view) #1674
  • Fix language dropdown not present in the media modal accessible from the media library grid view #1675
  • Fix DB error introduce by WooCommerce 9.9 #1681

3.7.2 (2025-05-27)

  • Pro: Require ACF 6.0+ to activate the integration to avoid fatal errors with older versions
  • Pro: Add a new ACF field group setting to decide if translations instructions must be displayed
  • Pro: Fix a fatal error when using ACF blocks with ACF < 6.3.0
  • Pro: Fix regression preventing to translate Oembed, URL and Email ACF fields
  • Pro: Fix ACF fields not translated when they have a default value
  • Pro: Fix empty ACF fields values not copied when the field has a default value
  • Pro: Fix ACF field default values not translated when copying a post
  • Pro: Fix possible fatal error if invalid types of data are sent for machine translation
  • Pro: Fix term meta removed when a term is machine translated
  • Fix nav menu locations not saved if invalid data are stored in database #1659
  • Fix parent relationship removed when a new translated term is created without parent #1671

3.7.1 (2025-05-05)

  • Pro: Do not display ACF fields translations settings when language location is set.
  • Pro: Fix ACF taxonomy field terms not synchronized when “Save Terms” and “load terms” settings are activated.
  • Pro: Fix duplicate options when using numeric keys for ACF choice fields.

3.7 (2025-04-22)

  • Requires PHP 7.2 as minimum version
  • Pro: Add DeepL machine translation for strings
  • Pro: Consider Polylang Pro as equivalent to Polylang for plugin dependencies
  • Pro: Add the details block and several labels in other blocks to XLIFF files and machine translation
  • Pro: Allow to translate metas stored as objects
  • Pro: Enhanced multilingual support of archive template hierarchy
  • Pro: Wrap the language switcher block in a nav tag
  • Pro: Support automatic IDs translation in blocks with new filters pll_sync_block_rules_for_attributes and pll_sync_blocks_xpath_rules
  • Pro: Complete rewrite of ACF integration
  • Pro: Add support for ACF blocks, post types and taxonomies.
  • Pro: Remove the possibility to translate ACF field groups
  • Pro: Add languages in ACF locations
  • Pro: Add translation of ACF labels in the strings translations page
  • Pro: Fix incorrect count of translated strings when importing strings translations
  • Pro: Fix incorrect translation when an XLIFF import updates a term sharing its slug
  • Pro: Fix term hierarchy with machine translation
  • Pro: Fix indented items of a list block not translated with machine translation
  • Pro: Fix navigation block inserted in the wrong language
  • Update plugin updater to 1.9.4
  • Add translation of widgets custom html in strings translations #1423
  • Refactor core to manage the plugin options in an object #1451
  • Refactor core to give access to languages management in all contexts #1503
  • Remove the language set from the content option for new installs #1517
  • Allow numbers in language codes #1546
  • Display empty fields in the translations table for untranslated strings (instead of duplicating the original) #1574
  • Add REST API endpoints to manage options and languages #1505 #1569
  • Improve performance by registering the language taxonomy only once #1359
  • Add new API functions to insert and update posts and terms in a given language #1500 #1520
  • Add compatibility with jQuery 4 (planned in core for WP 6.8) #1612
  • Fix translations not loaded when the language is set from the content #1395
  • Fix possible term duplication #1490
  • Fix sanitization of translated options that may impact other strings #1571
  • Fix home link block not translated #1647
  • Fix a conflict with WooCommerce Price Based on Country #1638

See changelog.txt for older changelog