Polylang free covers the basics. Building a real multilingual theme on it, you quickly run into things that only Polylang PRO or WPML handle. This plugin adds them, configured from your theme in code so the setup travels with the theme rather than the database.<\/p>\n\n
\/about-us\/<\/code> and \/es\/about-us\/<\/code> instead of \/es\/about-us-2\/<\/code>, for posts, pages, custom post types and terms. Requests resolve to the post or term of the requested language.<\/li>\n- Translated URL bases.<\/strong>
\/success-stories\/<\/code> in English, \/es\/casos-de-exito\/<\/code> in Spanish, for post types, taxonomies and the blog base.<\/li>\n- Per-language ACF \/ SCF options pages.<\/strong> Language tabs above the options page, a \"copy from the default language\" button, and a fallback to the default language for empty values.
get_field( 'name', 'options' )<\/code> keeps working.<\/li>\n- Duplicate as translation.<\/strong> A \"Duplicate \u2192 Espa\u00f1ol\" row action copies blocks, custom fields, featured image, template and terms, and links the posts as translations.<\/li>\n
- Copy from another language.<\/strong> A \"Translation\" box in the editor replaces a translation's title, content, custom fields and terms with those of any other language, like WPML's \"Copy content from\". New translations created with Polylang's \"+\" start pre-filled from the source post.<\/li>\n
- Outdated translations.<\/strong> A translation remembers what it was copied from. Once the source changes, the editor box and the posts list flag it as outdated until it is marked up to date or copied again.<\/li>\n
- Menu sync.<\/strong> One button on the Menus screen copies the default language menus to every other language and assigns them to the same locations. Items point to the translated posts and terms, labels already translated are kept, and items removed from the source are removed from the copies.<\/li>\n
- Translated ids on output.<\/strong> Reusable blocks and ACF post object, relationship and taxonomy values, options pages included, show the current language's translation when there is one.<\/li>\n
- Default category in every language.<\/strong> Repairs the default category translation Polylang leaves without a language when languages are created programmatically, and creates missing ones.<\/li>\n
- Image alt per language<\/strong>, with a fallback to the library alt, for images output with
wp_get_attachment_image()<\/code>. The block editor's Image block saves its alt into the post content and is translated with the post.<\/li>\n- Theme strings<\/strong> in Languages \u2192 Translations.<\/li>\n
- Author profile fields per language<\/strong>, including the biography fallback Polylang free lacks.<\/li>\n
- Language switcher data<\/strong> that hides untranslated, hidden or not-yet-translated copies, or keeps them greyed out, plus hreflang
x-default<\/code>.<\/li>\n- Paged archives.<\/strong> The switcher and hreflang of
\/page\/2\/<\/code> point to page 2 of each translation, and a language with fewer pages is left out. Polylang prints no hreflang on paged archives at all.<\/li>\n- No foreign slugs.<\/strong> A URL reached through another language's slug, like
\/pt\/recursos\/<\/code> for \/pt\/blog-e-noticias\/<\/code>, redirects to the translation's own address instead of serving a duplicate.<\/li>\n- One Yoast sitemap per language<\/strong>, if you prefer it. With languages in directories Yoast's per-type maps mix every language, as they do with WPML; opted in, the sitemap index lists
en-sitemap.xml<\/code>, es-sitemap.xml<\/code>\u2026 instead. Yoast's own rules for noindex, exclusions and canonicals still apply.<\/li>\n- Untranslated front page.<\/strong> Until the static front page is translated, a language's home redirects to the default language one instead of showing its empty blog, home links follow, and hreflang leaves that language out. Hidden languages are left out of hreflang too.<\/li>\n<\/ul>\n\n
Requires Polylang 3.7 or later.<\/p>\n\n
Cosmo Multilingual Kit for Polylang is an independent, unofficial plugin. \"Polylang\" is a trademark of WP SYNTEX; this plugin is not affiliated with or endorsed by WP SYNTEX, and the name refers to that plugin solely to describe what this one works with.<\/p>\n\n
Configuration<\/h3>\n\n
Everything is configured through a single filter, typically in the theme's functions.php<\/code>:<\/p>\n\nadd_filter( 'cosmo\/multilingual_kit\/config', function ( $config ) {\n return array_merge( $config, [\n 'post_types' => [ 'post', 'page', 'story' ],\n 'taxonomies' => [ 'category', 'post_tag', 'story_category' ],\n 'bases' => [ 'blog', 'story', 'story_category' ],\n 'base_map' => [ 'story' => [ 'es' => 'casos-de-exito' ] ],\n 'options_pages' => [ 'site-options' ],\n 'strings' => [ 'read_more' => 'Read more' ],\n 'strings_group' => 'My theme',\n 'user_fields' => [ 'position' => 'Position' ],\n 'pending_meta' => 'translation_pending',\n 'hidden_languages' => [ 'uz' ],\n 'sitemaps' => 'language',\n ] );\n} );\n<\/code><\/pre>\n\n\npost_types<\/code>, taxonomies<\/code> \u2014 made translatable in addition to Polylang's settings.<\/li>\nbases<\/code> \u2014 sections whose URL base can be translated: post type names, taxonomy names, or blog<\/code>. A default can be given explicitly ('blog' => 'news'<\/code>), otherwise the registered rewrite slug is used. Every URL of the section follows the translated base: nested terms, feeds, paging, archives.<\/li>\nbase_map<\/code> \u2014 translated bases per language. Flush permalinks after changing it, and let your SEO plugin rebuild its URL cache.<\/li>\noptions_pages<\/code> \u2014 ACF options page slugs stored per language. Storage goes by the page's post id, so every options page that keeps the default options<\/code> post id becomes per-language too; give pages that should stay shared their own post_id<\/code>. A field left empty in a language shows the default language value, except for cells inside repeaters and flexible content.<\/li>\nstrings<\/code>, strings_group<\/code> \u2014 template strings registered with Polylang.<\/li>\nuser_fields<\/code> \u2014 profile fields translated per language.<\/li>\npending_meta<\/code> \u2014 meta key set on duplicated copies; while set, the language switcher hides that language.<\/li>\nhidden_languages<\/code> \u2014 languages left out of the switcher and hreflang, e.g. while their content is being prepared.<\/li>\nx_default<\/code> \u2014 add hreflang x-default<\/code> (default true<\/code>).<\/li>\nprefill_translations<\/code> \u2014 pre-fill translations created with Polylang's \"+\" from the source post (default true<\/code>, off with Polylang PRO, which does it itself).<\/li>\nsitemaps<\/code> \u2014 Yoast sitemaps with languages in directories: mixed<\/code> keeps Yoast's per-type maps with every language in them (default), language<\/code> gives one map per language. Subdomains and domains get a sitemap per host either way.<\/li>\nmodules<\/code> \u2014 switch modules off: [ 'media' => false ]<\/code>. Keys: slugs<\/code>, bases<\/code>, default_term<\/code>, options<\/code>, duplicate<\/code>, translations<\/code>, menus<\/code>, ids<\/code>, media<\/code>, strings<\/code>, users<\/code>, frontend<\/code>, sitemaps<\/code>.<\/li>\n<\/ul>\n\nTemplate functions<\/h3>\n\n\ncosmo_mlk_language()<\/code>, cosmo_mlk_default_language()<\/code>, cosmo_mlk_locale( $language )<\/code>, cosmo_mlk_languages()<\/code><\/li>\ncosmo_mlk_home_url( $path, $language )<\/code>, cosmo_mlk_url_prefix( $language )<\/code>, cosmo_mlk_url_base( $key, $language )<\/code><\/li>\ncosmo_mlk_switcher( $args )<\/code> \u2014 languages for a switcher: slug, name, locale, url, flag, current, available. Pass keep_unavailable => true<\/code> to keep untranslated languages with an empty url.<\/li>\ncosmo_mlk_t( $key, $fallback )<\/code> \u2014 translated template string<\/li>\ncosmo_mlk_user_field( $user_id, $key, $language )<\/code>, cosmo_mlk_image_alt( $attachment_id, $language )<\/code><\/li>\ncosmo_mlk_translated_post( $post_id, $language )<\/code>, cosmo_mlk_readable_translation( $post_id, $language )<\/code>, cosmo_mlk_pending_translations()<\/code><\/li>\ncosmo_mlk_term_by_slug( $slug, $taxonomy, $language )<\/code>, cosmo_mlk_insert_term( $name, $taxonomy, $language, $args )<\/code><\/li>\ncosmo_mlk_duplicate_post( $post_id, $language, $args )<\/code>, cosmo_mlk_link_translations( $map )<\/code>, cosmo_mlk_link_term_translations( $map )<\/code><\/li>\ncosmo_mlk_copy_post( $from, $to )<\/code>, cosmo_mlk_translation_outdated( $post_id )<\/code><\/li>\ncosmo_mlk_sync_menus()<\/code><\/li>\ncosmo_mlk_copy_options( $from, $to, $pages )<\/code>, cosmo_mlk_migrate_legacy_options( $language )<\/code><\/li>\n<\/ul>\n\nEvery function keeps working with Polylang switched off, falling back to a single default language.<\/p>\n\n
Hooks<\/h3>\n\n\ncosmo\/multilingual_kit\/config<\/code> \u2014 the configuration above.<\/li>\ncosmo\/multilingual_kit\/switcher<\/code> \u2014 filters the switcher language list.<\/li>\ncosmo\/multilingual_kit\/per_page<\/code> \u2014 posts per page of a post type archive, for the paged URLs in the language sitemaps: ( $per_page, $post_type )<\/code>. Defaults to the Reading setting.<\/li>\ncosmo\/multilingual_kit\/duplicated<\/code> \u2014 fires after a translation is created by copying: ( $new_id, $source_id, $language )<\/code>.<\/li>\ncosmo\/multilingual_kit\/copied<\/code> \u2014 fires after an existing translation is overwritten from another language: ( $post_id, $source_id, $language )<\/code>.<\/li>\n<\/ul>\n\n\n\n- Install and activate Polylang 3.7 or later, and add your languages.<\/li>\n
- Upload the plugin through Plugins - Add New - Upload Plugin<\/strong>, or install it from the plugin directory.<\/li>\n
- Activate Cosmo Multilingual Kit for Polylang<\/strong>.<\/li>\n
- Add the
cosmo\/multilingual_kit\/config<\/code> filter to your theme (see Configuration in the description) and flush permalinks under Settings - Permalinks<\/strong>.<\/li>\n<\/ol>\n\n\n\nI switched an existing site to per-language options and the settings look empty<\/h3><\/dt>\nValues saved before were stored without a language. Run cosmo_mlk_migrate_legacy_options()<\/code> once to move them to the default language.<\/p><\/dd>\nDoes it work with Polylang PRO?<\/h3><\/dt>\nIt targets Polylang free. With PRO active, the slugs<\/code>, bases<\/code> and duplicate<\/code> modules switch themselves off, since PRO covers them. An explicit modules<\/code> entry in the config overrides that.<\/p><\/dd>\nWhich modules switch themselves off?<\/h3><\/dt>\nThe Plugins screen lists them with the reason:<\/p>\n\n
\nslugs<\/code> and bases<\/code> and duplicate<\/code> with Polylang PRO.<\/li>\nslugs<\/code> when Polylang sets the language from the content: with no language in the URL, shared slugs cannot be told apart.<\/li>\noptions<\/code> with ACF Options For Polylang, which stores options per language on its own.<\/li>\nmedia<\/code> when Polylang media translation is on, as every language then has its own attachment.<\/li>\n<\/ul><\/dd>\nWhich URL modes are supported?<\/h3><\/dt>\nLanguage as a directory (with or without \/language\/<\/code>), as a subdomain, or as a domain. Sites installed in a subdirectory work too.<\/p><\/dd>\nCan I duplicate WooCommerce products?<\/h3><\/dt>\nNo. WooCommerce keeps product data outside post meta, so a plain copy would give a broken product.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.2.2<\/h4>\n\n\n- A posts page sharing its slug with its translations shows each language's blog instead of an empty page.<\/li>\n<\/ul>\n\n
1.2.1<\/h4>\n\n\n- Yoast sitemaps stay mixed across languages by default, as in 1.1 and WPML. One sitemap per language is opted into with the new
sitemaps => 'language'<\/code> config key.<\/li>\n<\/ul>\n\n1.2.0<\/h4>\n\n\n- Paged archives keep the page number in the switcher and get hreflang, which Polylang leaves out.<\/li>\n
- URLs reached through another language's slug redirect to the translation's own address.<\/li>\n
- New
sitemaps<\/code> module: one Yoast sitemap per language, paged archives included.<\/li>\n<\/ul>\n\n1.1.1<\/h4>\n\n\n- Template functions are pluggable, so the plugin activates on a theme that declares its own fallbacks for them.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Copy from another language, pre-filled new translations and outdated translation tracking.<\/li>\n
- Menu sync across languages.<\/li>\n
- Reusable blocks and ACF relational fields follow the current language.<\/li>\n
- Switcher can keep untranslated languages greyed out.<\/li>\n
- Untranslated front page no longer exposes an empty blog in other languages.<\/li>\n
- Hidden languages are left out of hreflang.<\/li>\n
- Options pages: get_field() by name works in a language that was never saved.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"Fills the gaps of Polylang free: one slug in every language, translated URL bases, per-language ACF options, duplicate-as-translation and more.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/393500","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=393500"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/bakhods"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=393500"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=393500"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=393500"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=393500"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=393500"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=393500"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}