Title: OpenLang – WordPress Translation & Multilingual Plugin with AI Author: Vynatics Published: 19 rugpjūčio, 2026 Last modified: 27 rugpjūčio, 2026 --- Ieškoti įskiepiuose ![](https://ps.w.org/vynlang/assets/banner-772x250.jpg?rev=3657352) ![](https://ps.w.org/vynlang/assets/icon-256x256.png?rev=3655017) # OpenLang – WordPress Translation & Multilingual Plugin with AI Autorius [Vynatics](https://profiles.wordpress.org/vynatics/) [Parsisiųsti](https://downloads.wordpress.org/plugin/vynlang.2.8.7.zip) [Live Preview](https://lt.wordpress.org/plugins/vynlang/?preview=1) * [Informacija](https://lt.wordpress.org/plugins/vynlang/#description) * [Atsiliepimai](https://lt.wordpress.org/plugins/vynlang/#reviews) * [Diegimas](https://lt.wordpress.org/plugins/vynlang/#installation) * [Kūrimas](https://lt.wordpress.org/plugins/vynlang/#developers) [Pagalba](https://wordpress.org/support/plugin/vynlang/) ## Aprašymas OpenLang is a free WordPress translation plugin for building multilingual websites with manual translation control and optional automatic AI translation. Translate WordPress without creating a separate page for every language. OpenLang discovers visible frontend text at runtime, lets you review and edit translations in WordPress admin, and serves language-specific URLs with a frontend language switcher. Use OpenLang to create a multilingual WordPress website, translate content manually, automatically translate missing strings with AI, support RTL layouts, add an Elementor language switcher, and customize fonts, logos, CSS, and JavaScript for individual languages. All features included in this WordPress.org package are available without a license key. #### WordPress Translation & Multilingual Features * Discover visible frontend text and common translatable attributes at runtime. * Manage manual WordPress translations and detected strings. * Use hosted automatic AI translation for missing strings. * Enable multiple languages with a configurable default language. * Serve language-specific URLs without manually duplicating every page. * Add a frontend language switcher with local translation caching. * Support RTL and LTR page direction. * Use an Elementor language-switcher integration. * View translation coverage, runtime activity, analytics, and system status. * Configure typography separately for each language. * Use Google Fonts, system fonts, or uploaded WOFF, WOFF2, TTF, and OTF webfonts. * Set language-specific website logos. * Import and export translations with CSV. * Add per-language Custom CSS and Custom JavaScript. #### Manual or Automatic WordPress Translation OpenLang supports both manual and automatic translation workflows. For manual translation, OpenLang discovers visible frontend strings and lets administrators review and edit translations directly from WordPress admin. Hosted AI translation is enabled by default. When an enabled language has missing strings, OpenLang can send them to the managed translation service, receive translated text, and store the translations for use on the website. Administrators can disable automatic translation under OpenLang > Settings. #### Multilingual URLs, Language Switcher & RTL OpenLang serves language-specific URLs with frontend language switching, browser- history handling, and local translation caching. It supports both RTL and LTR direction. #### Elementor, Typography & Language-Specific Design OpenLang includes an Elementor language-switcher integration. Each language can also use its own typography, fonts, website logo, Custom CSS, and Custom JavaScript. Generated files are stored under `wp-content/uploads/vynlang/assets/`. #### Privacy and External Services OpenLang works locally for manual translation management. Hosted automatic translation is enabled by default and can be disabled under OpenLang > Settings. When enabled and missing strings need translation, OpenLang can send requests to: ``` https://vynatics.corsysltd.com/server/api/translate ``` A translation request can include source and target language codes, source strings and their MD5 dictionary hashes, the site URL and an MD5 hash of the site URL, and OpenLang and WordPress version numbers. This build has no license activation system and does not require or transmit an OpenLang license key. The public OpenLang REST dictionary endpoint is read-only. It returns locally stored translations and language assets; it does not call the hosted service and does not write translations to the database. If automatic translation is enabled and a visitor requests a language whose current page still contains untranslated strings, OpenLang uses the normal language URL so translation can occur through the server-side page-rendering workflow. If an administrator selects a Google Font, the visitor’s browser may load resources from `https://fonts.googleapis.com` and `https://fonts.gstatic.com`. Standard request information such as IP address, user agent, and requested font resource may therefore be sent to Google. Google Privacy Policy: https://policies.google.com/privacy Google Terms: https:// policies.google.com/terms Service provider: Vynatics Privacy policy: https://vynatics.corsysltd.com/openlang/ privacy-policy.html Terms: https://vynatics.corsysltd.com/openlang/terms-of-service. html Support: d.laeeq@corsysltd.com #### Security * Administrative data-changing actions require WordPress capability checks and nonces. * The public translation REST endpoint is read-only and accepts only bounded, validated MD5 hash lookups. * Managed translation requests require HTTPS and use WordPress safe HTTP requests with redirects disabled. * Custom webfont uploads are limited to administrators who can upload files. * CSV import is administrator-only, nonce-protected, limited to CSV files up to 10 MB, and does not execute uploaded content. * CSV exports neutralize leading spreadsheet-formula characters in human-entered text fields. * Custom code changes are administrator-only and nonce-protected; unfiltered JavaScript editing respects WordPress’s `unfiltered_html` capability. ## Ekrano nuotraukos [⌊OpenLang dashboard showing multilingual and translation status.⌉⌊OpenLang dashboard showing multilingual and translation status.⌉[ OpenLang dashboard showing multilingual and translation status. [⌊Languages screen for enabling and managing website languages.⌉⌊Languages screen for enabling and managing website languages.⌉[ Languages screen for enabling and managing website languages. [⌊Translation manager for reviewing and editing detected WordPress strings.⌉⌊Translation manager for reviewing and editing detected WordPress strings.⌉[ Translation manager for reviewing and editing detected WordPress strings. ## Diegimas 1. Install OpenLang from the WordPress Plugin Directory or upload the `vynlang` plugin folder / ZIP. 2. Activate `OpenLang - AI Language Translator`. 3. Open OpenLang > Languages and enable the languages you need. 4. Open OpenLang > Translations to review or manually edit detected strings. 5. Automatic AI translation is enabled by default; optionally review or disable it under OpenLang > Settings. 6. Configure Typography and Website Logo overrides for individual languages if needed. 7. Use OpenLang > Custom CSS / JS for language-specific frontend code. ## DUK ### What is OpenLang? OpenLang is a free WordPress translation and multilingual plugin with manual translation management, optional AI translation, language-specific URLs, RTL support, caching, a frontend language switcher, Elementor integration, and per-language design controls. ### Is OpenLang free? Yes. All features shipped in this WordPress.org package are available without license activation. ### How do I translate a WordPress website into multiple languages? Install OpenLang, enable languages under OpenLang > Languages, then use OpenLang > Translations to review or edit detected strings. Automatic AI translation can translate missing strings when enabled. ### Can I translate WordPress manually? Yes. OpenLang discovers visible frontend strings and lets administrators review and edit translations manually from WordPress admin. ### Can OpenLang translate WordPress automatically with AI? Yes. Hosted AI translation is enabled by default so missing strings can be translated automatically. Administrators can disable it under OpenLang > Settings. ### Does OpenLang create a separate page for every language? No. OpenLang serves language-specific URLs and stored translations without requiring a separate manually created WordPress page for every language. ### Does OpenLang include a language switcher? Yes. OpenLang includes frontend language switching and an Elementor language-switcher integration. ### Does OpenLang work with Elementor? OpenLang includes an Elementor language-switcher integration for adding language selection to Elementor layouts. ### Does OpenLang support RTL languages? Yes. OpenLang supports both RTL and LTR direction handling. ### Can each language use different fonts or logos? Yes. OpenLang supports per-language typography, uploaded webfonts, and website-logo overrides. ### Can I import and export translations with CSV? Yes. Administrators can import and export translation data using CSV files. ## Atsiliepimai Įskiepis neturi atsiliepimų. ## Programuotojai ir komandos nariai “OpenLang – WordPress Translation & Multilingual Plugin with AI” yra atviro kodo programa. Prie jos sukūrimo prisidėję žmonės surašyti toliau. Autoriai * [ Vynatics ](https://profiles.wordpress.org/vynatics/) [Išverskite “OpenLang – WordPress Translation & Multilingual Plugin with AI” į savo kalbą.](https://translate.wordpress.org/projects/wp-plugins/vynlang) ### Domina programavimas? [Peržiūrėkite kodą](https://plugins.trac.wordpress.org/browser/vynlang/), naršykite [SVN repozitorijoje](https://plugins.svn.wordpress.org/vynlang/), arba užsiprenumeruokite [kodo pakeitimų žurnalą](https://plugins.trac.wordpress.org/log/vynlang/) per [RSS](https://plugins.trac.wordpress.org/log/vynlang/?limit=100&mode=stop_on_copy&format=rss). ## Pakeitimų istorija #### 2.8.7 * Changed Custom CSS and Custom JavaScript from site-wide code to per-language assets. * Added per-language CSS/JS storage, language switching in the editor, DOM-ready and document-head JavaScript options, AJAX load/save/reset, and unsaved-change protection. * Generate cache-busted files under `wp-content/uploads/vynlang/assets/css/{language}. css` and `wp-content/uploads/vynlang/assets/js/{language}.js`. * Enqueue generated files only for the active server-rendered language and dynamically replace them during client-side language switching. * Preserve 2.8.6 site-wide custom code by migrating it into the default language on upgrade. * Kept custom-code changes nonce/capability protected and retained WordPress `unfiltered_html` enforcement for JavaScript editing. ## Metainformacija * Version **2.8.7** * Atnaujinta **prieš 4 val** * Aktyvių instaliacijų **Mažiau nei 10** * WordPress versija ** 6.3 ar naujesnė ** * Ištestuota iki **7.1** * PHP versija ** 7.4 ar naujesnė ** * Kalba * [English (US)](https://wordpress.org/plugins/vynlang/) * Žymos * [ai translation](https://lt.wordpress.org/plugins/tags/ai-translation/)[automatic translation](https://lt.wordpress.org/plugins/tags/automatic-translation/) [multilingual](https://lt.wordpress.org/plugins/tags/multilingual/)[translate](https://lt.wordpress.org/plugins/tags/translate/) [translation](https://lt.wordpress.org/plugins/tags/translation/) * [Daugiau](https://lt.wordpress.org/plugins/vynlang/advanced/) ## Įvertinimai No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/vynlang/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/vynlang/reviews/) ## Autoriai * [ Vynatics ](https://profiles.wordpress.org/vynatics/) ## Pagalba Turite pastabų? Reikia pagalbos? [Peržiūrėti pagalbos forumą](https://wordpress.org/support/plugin/vynlang/)