Adds an "Import from Polylang" button in LingoPress \u2192 Getting started and a WP-CLI command to bring your languages and translations over from Polylang.<\/p>","1.1.0":"
Adds an About tab with links to the documentation and an easy way to report a problem.<\/p>","1.0.1":"
Adds the license files (GPLv3 with additional terms). No functional changes.<\/p>","1.0.0":"
First WordPress.org release. Licensing has been removed: all features are free and updates now come from WordPress.org.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3738545,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3738545,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":{"lingopress\/language-switcher":{"name":"lingopress\/language-switcher","title":"Language Switcher (LingoPress)"}},"tagged_versions":["1.0.1","1.1.0","1.1.1"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[2353,8583,99,186,2333],"plugin_category":[48,55],"plugin_contributors":[285604],"plugin_business_model":[],"class_list":["post-383610","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-languages","plugin_tags-multilingual","plugin_tags-seo","plugin_tags-translation","plugin_category-language-tools","plugin_category-seo-and-marketing","plugin_contributors-ballesdev","plugin_committers-ballesdev"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/ballesdev-lingopress\/assets\/icon-128x128.png?rev=3738545","icon_2x":"https:\/\/ps.w.org\/ballesdev-lingopress\/assets\/icon-256x256.png?rev=3738545","generated":false},"screenshots":[],"raw_content":"\n
BallesDev LingoPress makes your WordPress site multilingual with a proven data model (languages and translation groups as taxonomies, no custom tables) and adds AI translation that actually understands your content. Every feature is included \u2014 there is no paid tier, license key or locked functionality.<\/p>\n\n
Multilingual core<\/strong><\/p>\n\n AI translation (optional)<\/strong><\/p>\n\n The multilingual features work fully without any API key. AI translation is an optional extra that only runs when you ask for it \u2014 see \"External services\" below.<\/p>\n\n Developer friendly<\/strong><\/p>\n\n Copyright 2026 balles.dev. BallesDev LingoPress is free software under the GPL, version 3 or later, with additional terms: copies and modified versions must keep the notice \"Originally developed by balles.dev (https:\/\/balles.dev\/)\", and modified versions must use a different name, without \"BallesDev\", \"balles.dev\" or \"LingoPress\". See LICENSE.txt and NOTICE.txt.<\/p>\n\n LingoPress can translate your content with an AI provider of your choice. This is optional: no request is made to any AI service until a provider is set up \u2014 a connector in Settings \u2192 Connectors<\/strong> (WordPress 7.0+) or an API key in LingoPress \u2192 AI translation<\/strong> (or its constant in Only the provider selected in the settings receives data. Each request sends the text being translated (post title, content and excerpt; a theme template; or the registered strings), the source and target languages, your site name and tagline, the \"Site context\" and glossary settings, the post type and the names of the post's categories and tags, together with your API key to authenticate. No other site or visitor data is sent.<\/p>\n\n The Getting started<\/strong> tab walks you through these steps and shows what is still pending.<\/p>\n\n\n No. Languages, URLs, hreflang, the language switcher, menus, media and string translations all work without any API key. AI translation is optional.<\/p><\/dd>\n No. Every translation is created as a draft, linked to the original, for a human to review and publish.<\/p><\/dd>\n Jobs are retried automatically with increasing backoff. You can also retry failed jobs manually from LingoPress \u2192 Queue.<\/p><\/dd>\n With the \"WordPress (Connectors)\" provider (WordPress 7.0+), in Settings \u2192 Connectors<\/strong>: WordPress manages the credentials and LingoPress stores none. With your own key, in the plugin settings, or preferably in Yes. With Polylang still installed (active or not), go to LingoPress \u2192 Getting started<\/strong> and click Import from Polylang<\/strong>. It migrates languages, post\/term languages and translation groups, never changes Polylang's data, and is safe to run again: anything already imported is skipped. On large sites you can run \n
lang<\/code> and translations<\/code> fields on wp\/v2, collection filtering with ?lang=<\/code>.<\/li>\n<\/ul>\n\n\n
\n
lingopress_set_post_language()<\/code>, lingopress_get_post()<\/code>, lingopress_the_languages()<\/code>, lingopress_register_string()<\/code> and more.<\/li>\nlingopress_language_defined<\/code>, lingopress_ai_system_prompt<\/code>, lingopress_ai_provider<\/code>, lingopress_switcher_items<\/code>, lingopress_sync_post_meta<\/code>.<\/li>\nwp lingopress import-polylang<\/code>.<\/li>\n<\/ul>\n\nLicense<\/h4>\n\n
External services<\/h3>\n\n
wp-config.php<\/code>) \u2014 and a user with editing permissions starts a translation \u2014 from the post editor, the bulk action, the Queue, the Templates tab or the \"Translate missing strings with AI\" button. Queued jobs run in the background through WP-Cron, but only jobs that a user explicitly queued.<\/p>\n\n\n
api.anthropic.com<\/code>) \u2014 used when the provider is set to Claude. Terms of service<\/a>, Privacy policy<\/a>.<\/li>\ngenerativelanguage.googleapis.com<\/code>) \u2014 used when the provider is set to Gemini. Terms of service<\/a>, Privacy policy<\/a>.<\/li>\napi.openai.com<\/code>) \u2014 used when the provider is set to OpenAI. Terms of service<\/a>, Privacy policy<\/a>.<\/li>\napi.groq.com<\/code>) \u2014 used when the provider is set to Groq. Terms of service<\/a>, Privacy policy<\/a>.<\/li>\n<\/ul>\n\n\n\n
\n
Do I need an AI provider to use LingoPress?<\/h3><\/dt>\n
Does the AI publish translations automatically?<\/h3><\/dt>\n
What happens if the AI provider is saturated?<\/h3><\/dt>\n
Where do the API keys live?<\/h3><\/dt>\n
wp-config.php<\/code> via the LINGOPRESS_ANTHROPIC_API_KEY<\/code>, LINGOPRESS_GEMINI_API_KEY<\/code>, LINGOPRESS_OPENAI_API_KEY<\/code> or LINGOPRESS_GROQ_API_KEY<\/code> constants (constants take precedence).<\/p><\/dd>\nCan I migrate from Polylang?<\/h3><\/dt>\n
wp lingopress import-polylang<\/code> instead.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.1<\/h4>\n\n
\n
wp lingopress import-polylang<\/code>.<\/li>\n1.1.0<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n
lingopress_<\/code> prefix, e.g. lingopress_get_post()<\/code>, lingopress_set_post_language()<\/code>.<\/li>\n