Title: TranslateRocket – Free Multilingual Translation, Unlimited Languages Author: Federico Published: 14 يوليو، 2026 Last modified: 24 سبتمبر، 2026 --- البحث عن الإضافات ![](https://ps.w.org/translate-rocket/assets/banner-772x250.png?rev=3675937) ![](https://ps.w.org/translate-rocket/assets/icon-256x256.png?rev=3608126) # TranslateRocket – Free Multilingual Translation, Unlimited Languages بواسطة [Federico](https://profiles.wordpress.org/federicodev/) [تنزيل](https://downloads.wordpress.org/plugin/translate-rocket.1.5.5.zip) [Live Preview](https://ar.wordpress.org/plugins/translate-rocket/?preview=1) * [تفاصيل](https://ar.wordpress.org/plugins/translate-rocket/#description) * [المراجعات](https://ar.wordpress.org/plugins/translate-rocket/#reviews) * [التنصيب](https://ar.wordpress.org/plugins/translate-rocket/#installation) * [التطوير](https://ar.wordpress.org/plugins/translate-rocket/#developers) [الدعم](https://wordpress.org/support/plugin/translate-rocket/) ## الوصف **TranslateRocket makes your site multilingual, and everything it does is free.** No word limits, no charge per language, and nothing switched off to push you towards an upgrade — it is not a trimmed-down version of a paid plugin. **Already using WPML, Polylang, TranslatePress or Weglot? Try TranslateRocket next to it — your site does not change.** Activate it alongside your current translation plugin: visitors keep seeing exactly the same site, while you import your translations, complete them and preview any page in any language as an administrator. When you are convinced, deactivate the old plugin and put TranslateRocket online with one click. Nothing of the other plugin is deleted, and switching it back on takes you straight back to where you started. **You do not need an API key at all.** Chrome and Edge on a computer carry a translator that runs on the device itself, and TranslateRocket can drive it: install the plugin, pick your languages, press one button and the site is translated. It costs nothing, needs no account, and the text never leaves your machine. It is the fastest way to a translated site. When you want fluent, idiomatic copy, the same pages can go through DeepL or an AI model with your own key (OpenAI, Anthropic, Gemini — you pay the provider directly), through ChatGPT or Gemini with a ready-made prompt at no cost, or through your own hands, line by line — and everything already translated is kept, so nothing is ever done twice. **Switching from another translation plugin? Your existing translations come with you.** One click imports everything you have already paid for or typed by hand — from **TranslatePress, Polylang, WPML, Weglot, qTranslate (X and XT), WPGlobus, WP Multilang, Bogo, Multilanguage by BestWebSoft, Falang, Sublanguage and Loco Translate**, plus CSV and TMX for anything else. Most are read straight from the tables, the posts or the files, so the import still works after the other plugin has been deactivated or even deleted — which is the usual state of a site that is moving on. Pages built with Elementor or Bricks come across too, widget by widget — their words live in a meta field, not in the page content, and most importers never look there. It detects translatable text as you browse — visible text, link titles, image alt, placeholders, ARIA labels, page titles, meta descriptions and the social preview tags a SEO plugin adds (Open Graph, X) — and serves each language under its own clean URL prefix (`/it/`, `/de/`), friendly to SEO and to page caches. You translate however you like: * 🆓 **In your browser, with no key** — Chrome and Edge translate the whole page, or the whole site, on the device itself. Nothing to sign up for, nothing to pay, nothing sent anywhere. Available both on the live page and on the bulk screen. * 🖱️ **On the live page** — switch on the visual editor and click any text to translate it in a small, draggable popup, with Previous/Next, a progress bar and a “skip already-translated” mode. * 🆓 **Free with Google Translate (no key)** — every field has a link that opens Google Translate prefilled, so you translate for free on Google’s own site and paste the result back. * ✍️ **By hand**, in a clear per-page editor (also inside the post/page screen) with red highlighting for what’s still missing — plus a copy & paste box for bulk Google translation. * 💬 **With ChatGPT or Gemini, no key** — one button copies the whole page with a translation prompt written for your site; paste the answer back and every line goes to its place. * 🤖 **With AI** — bring your own key for DeepL, OpenAI, Google Gemini, Anthropic( Claude) or Google Cloud Translate. Text is sent only to the provider you choose, only when you ask. #### Highlights * 🔑 **No API key required — and not just “by hand”.** Chrome and Edge translate the whole site automatically, on your own computer, for free. Or do it by hand in the visual editor, or free with Google Translate, and edit any translation later. There is no signup, no account and no key to create — AI providers are optional and only used if you add one yourself. * 🌍 **Unlimited languages** (36 built in), 100% free. Donations welcome, never required. * ⚡ **Built for huge sites**: past ~20,000 strings the engine switches by itself to indexed per-page lookups — flat memory and the same render time at 500 or 500,000 strings (load-tested), where map-loading translation plugins hit the PHP memory limit. * 🖱️ **On-page visual editor**: click text to translate it in a draggable popup— no admin round-trips. * 🧩 **Interface too**: translates theme & plugin interface strings, not just page content. * 🔗 **SEO-ready URLs**: translated slugs (e.g. `/it/chi-siamo/`) and `hreflang` tags. * 🔍 **One SEO panel with everything in it**: open a page in the visual editor and the SEO panel lists, in order, the translated address, the page title, the meta description, the social preview (Open Graph and X), the keywords, then every image on the page and every translatable attribute — titles, placeholders, ARIA labels. Each line takes you straight to that element on the page and opens the right editor, so nothing search engines read is left in the source language by accident. * 🚦 **Per-page visibility**: if a page has no equivalent in a language, redirect it, show a custom message, or 404 — per page, per language. * 🎌 **Flexible language switcher** as a shortcode `[translaterocket_switcher]`, a Gutenberg block, or a widget — inline, dropdown, or a **scrollable bar with‹› arrows** for many languages — with original SVG flags that render everywhere ( including Windows). Show a switcher on desktop only, on mobile only, or both, to style a different menu for each. * 📥 **One-click import from twelve other plugins** — TranslatePress, Polylang, WPML, Weglot, qTranslate (X and XT), WPGlobus, WP Multilang, Bogo, Multilanguage by BestWebSoft, Falang, Sublanguage and Loco Translate — plus CSV and TMX for everything else. Read straight from the tables, the posts or the `.po` files, so it works even when the other plugin is gone. Pages built with Elementor or Bricks come across too, widget by widget. * 🖼️ **A different image for each language** — swap any picture for a translated one: switch on the visual editor, click the button on the image and pick another from your media library. For text baked into a picture, a screenshot of your own interface, or a photo that only makes sense in one country. * 🎯 **Different content and menus per language** — show a paragraph, a block or a menu item only in some languages: with a shortcode, a class on any block, or a checkbox in Appearance Menus. * 🛒 **WooCommerce aware**: product and category slugs per language, the AJAX mini- cart and JS strings translated too, and customer emails rendered in the language the order was placed in. * 👀 **Preview mode**: review new translations or a fresh import on the real pages while visitors still see the default language — publish with one click when ready. * 🚦 **Add a language now, publish it when it is ready**: each language has a switch— green and your visitors see it, grey and only you do. While it is offline it stays out of the switcher, out of your sitemap and out of the `hreflang` tags, and its URLs send visitors to your default language, while you keep working on the real pages. Nothing half-translated ever reaches your visitors or Google. * 📂 **Built for scale**: searchable, sortable page list for sites with hundreds of pages. * ✅ **You stay in charge** — every machine translation can be reviewed and edited by hand. Translations live in your own database. #### Languages Translate your site into the languages your visitors actually speak: Spanish, French, German, Italian, Portuguese and Brazilian Portuguese, Dutch, Polish, Russian, Ukrainian, Turkish, Romanian, Greek, Arabic, Hindi, Indonesian, Vietnamese, Thai, Chinese, Japanese, Korean — 36 languages ship built in, and you can add unlimited custom ones (any language code works). The plugin’s own admin interface is translated into nine languages besides English: Japanese, Spanish, German, French, Brazilian Portuguese, Italian, Dutch, Russian and Polish. #### Works with TranslateRocket translates the page your site actually sends to the browser, so it is not tied to a theme or a page builder. Every release is tested on a real site with the plugins below (tested means installed, configured and checked from the visitor’s side, not only read about): * **Page builders:** Elementor and Elementor Pro (theme builder headers and footers included), the block editor. While a builder is editing a page – Elementor, Beaver Builder, Divi, Bricks, Oxygen, Breakdance, Brizy, WPBakery, Thrive Architect, the Customizer – TranslateRocket stays out of its way. * **Shops:** WooCommerce – product pages, cart, checkout and the order e-mails, in the customer’s language. * **Forms:** Forminator, Contact Form 7, WPForms, Gravity Forms, SureForms, Formidable, Ninja Forms. * **Cookie and consent banners:** Complianz, CookieYes, GDPR Cookie Compliance, Cookie Notice – the banner text is collected, can be clicked in the visual editor and reaches visitors translated. * **SEO:** Yoast SEO, Rank Math – translated titles, descriptions and social tags. * **Caching and optimisation:** Cache Enabler, Autoptimize, WP Fastest Cache. * **Side by side with, and importing from:** WPML, Polylang, TranslatePress, Weglot, Bogo and others. The full list, with what was checked and the date of the last test: https://translaterocket. com/compatibility/ Something missing, or not behaving? Tell me from https://translaterocket.com/support/ and I will test it. #### Need a hand with your site? **I can do it for you.** I am the developer of TranslateRocket, and I also build and translate WordPress sites for a living: a new multilingual site from scratch, an existing site taken from one language to ten, a migration away from a paid plugin, or a stubborn theme that will not translate. You get the person who wrote the engine, not a support queue. The plugin stays free either way — nothing here is locked behind that. Write to me from the “Help & Feedback” screen inside the plugin, or from https://translaterocket. com/support/ . ### External services This plugin can connect to third-party services, but only with your involvement: * **AI translation providers (optional).** If you add an API key and ask to translate, the relevant text is sent to the provider you selected so it can return a translation. No text is sent until you configure a provider and trigger a translation. Providers and policies: - DeepL — service: https://www.deepl.com/en/pro , privacy: https://www.deepl. com/en/privacy - OpenAI — service: https://platform.openai.com , privacy: https://openai.com/ policies/privacy-policy/ - Google Cloud Translation / Gemini — service: https://cloud.google.com/translate, privacy: https://policies.google.com/privacy - Anthropic (Claude) — service: https://www.anthropic.com , privacy: https:// www.anthropic.com/legal/privacy * **Google Translate (manual, always available).** Every editor offers a per-phrase link and a copy-paste box that open Google Translate (translate.google.com) prefilled, so you translate on Google’s own site and paste the result back. This is just a convenience link — your browser, not the plugin, contacts Google. Service: https://translate.google.com , terms: https://policies.google.com/terms , privacy: https://policies.google.com/privacy * **Optional one-click Google auto-fill (off by default).** A site owner can opt in (the `TRROCKET_AUTO_GOOGLE` constant / the `trrocket_auto_google` filter) to let the server fetch a translation from Google’s free endpoint with one click. This uses an undocumented endpoint and is best-effort, so it is disabled out of the box and the plugin never calls it on its own. For dependable automatic translation use the official AI providers below. * **translaterocket.com support ticket (optional, on request).** The Diagnostics screen has a form that opens a support ticket for you. It sends nothing until you fill it in and press Send, and what it sends is exactly what the page shows you: your name, your email address (so the answer can reach you), your subject and message, your site address and the plugin version, plus the technical report if you leave that box ticked. The report never contains API keys. To prove the request really comes from your site and not from a spam robot, the support site then makes one request back to your site’s home URL with a one-time token. Nothing else is transmitted, nothing is stored on your site, and if you would rather not use it the same page still offers the copy-and-paste route. Service: https:// translaterocket.com , privacy: https://translaterocket.com/privacy-policy/ * **translaterocket.com (optional).** The “Help & Feedback”, “Request customization”,“ Send feedback” and “Get tips & updates” links open translaterocket.com in your browser with your site’s domain in the URL. Nothing is sent automatically — these are links you choose to click. Service: https://translaterocket.com , privacy: https://translaterocket.com/privacy-policy/ ## لقطات الشاشة [⌊Translate without an API key at all: Chrome and Edge carry a translator that runs on the device itself, and one button puts it to work on everything still missing. Nothing is sent anywhere, nothing is charged, and what it translates is kept for good.⌉⌊Translate without an API key at all: Chrome and Edge carry a translator that runs on the device itself, and one button puts it to work on everything still missing. Nothing is sent anywhere, nothing is charged, and what it translates is kept for good.⌉[ Translate without an API key at all: Chrome and Edge carry a translator that runs on the device itself, and one button puts it to work on everything still missing. Nothing is sent anywhere, nothing is charged, and what it translates is kept for good. [⌊Click any text on your live page and translate it there — the language switcher, the progress bar and the SEO panel are all in the toolbar.⌉⌊Click any text on your live page and translate it there — the language switcher, the progress bar and the SEO panel are all in the toolbar.⌉[ Click any text on your live page and translate it there — the language switcher, the progress bar and the SEO panel are all in the toolbar. [⌊The per-page editor: your text on the left, the translation on the right. Type it yourself or let AI fill it in.⌉⌊The per-page editor: your text on the left, the translation on the right. Type it yourself or let AI fill it in.⌉[ The per-page editor: your text on the left, the translation on the right. Type it yourself or let AI fill it in. [⌊Pick the language your site is written in and the languages to translate it into. Each one gets its own /xx/ URL.⌉⌊Pick the language your site is written in and the languages to translate it into. Each one gets its own /xx/ URL.⌉[ Pick the language your site is written in and the languages to translate it into. Each one gets its own /xx/ URL. [⌊Every page at a glance, with how much of it is translated and what is still missing.⌉⌊ Every page at a glance, with how much of it is translated and what is still missing .⌉[ Every page at a glance, with how much of it is translated and what is still missing. [⌊Bring your own key — OpenAI, Anthropic, Gemini, DeepL or Google. You pay the provider directly, and a key is optional.⌉⌊Bring your own key — OpenAI, Anthropic, Gemini, DeepL or Google. You pay the provider directly, and a key is optional.⌉[ Bring your own key — OpenAI, Anthropic, Gemini, DeepL or Google. You pay the provider directly, and a key is optional. [⌊Coming from another plugin? WPML, Polylang, TranslatePress, qTranslate, WPGlobus, WP Multilang, Bogo, Multilanguage, Falang, Sublanguage and Loco Translate are all detected automatically; Weglot imports from its CSV export.⌉⌊Coming from another plugin? WPML, Polylang, TranslatePress, qTranslate, WPGlobus, WP Multilang, Bogo, Multilanguage, Falang, Sublanguage and Loco Translate are all detected automatically; Weglot imports from its CSV export.⌉[ Coming from another plugin? WPML, Polylang, TranslatePress, qTranslate, WPGlobus, WP Multilang, Bogo, Multilanguage, Falang, Sublanguage and Loco Translate are all detected automatically; Weglot imports from its CSV export. [⌊Design the language switcher with a live preview — dropdown or list, flags, colours, corners and position.⌉⌊Design the language switcher with a live preview — dropdown or list, flags, colours, corners and position.⌉[ Design the language switcher with a live preview — dropdown or list, flags, colours, corners and position. [⌊SEO for each page and language: the translated URL slug, the title Google shows and the meta description.⌉⌊SEO for each page and language: the translated URL slug, the title Google shows and the meta description.⌉[ SEO for each page and language: the translated URL slug, the title Google shows and the meta description. [⌊Translation memory: the same phrase is never paid for twice, and you can see what that has saved you.⌉⌊Translation memory: the same phrase is never paid for twice, and you can see what that has saved you.⌉[ Translation memory: the same phrase is never paid for twice, and you can see what that has saved you. [⌊Diagnostics: a health check of the setup plus anything the plugin has flagged, so nothing fails silently.⌉⌊Diagnostics: a health check of the setup plus anything the plugin has flagged, so nothing fails silently.⌉[ Diagnostics: a health check of the setup plus anything the plugin has flagged, so nothing fails silently. ## المكوّنات تقدّم هذه الإضافة مكوّن واحد (1). * Language Switcher ## التنصيب 1. Upload the `translate-rocket` folder to `/wp-content/plugins/`, or install it from the Plugins screen. 2. Activate the plugin through the **Plugins** menu in WordPress. 3. Go to **TranslateRocket Settings** and pick your source language and the languages to translate into. 4. Browse your site to detect content, then translate from **TranslateRocket Translations**( by hand, copy & paste, or AI). 5. Add the language switcher anywhere with the `[translaterocket_switcher]` shortcode, the block, or the widget. First steps, filmed from installation to the first translated page: ## الأسئلة المتكررّة ### Is it really free? Yes. All translation features and unlimited languages are free, with no paid tier inside the plugin. You only ever pay your own AI provider, directly, if you choose to use AI. ### How do you keep it free with no income from it? I build websites for a living, and I use TranslateRocket on every multilingual site I make. Every fix reaches those sites the day I release it, so the plugin gets maintained because I need it maintained — publishing it for everyone costs me nothing on top of that. What comes back is worth more to me than a licence fee would be: bug reports from setups I could never reproduce on my own, which end up improving my own clients’ sites too. Donations are welcome and change nothing about what the plugin does. **And if you want that work done on your own site, you can hire me.** Building and fixing WordPress sites is the day job: a site built from scratch, a design put right, a multilingual setup done properly, custom development, a migration off a plugin that charges you every month. That is where the money comes from — not from crippling this plugin. Ask me from the “Help & Feedback” screen inside the plugin, or at https:// translaterocket.com/support/ . ### Do I need an AI key? No — and without one you are not limited to typing by hand. **Chrome and Edge on a computer carry a translator that runs on the device itself, and one button puts it to work on your whole site.** It costs nothing, needs no account and no signup, and the text never leaves your machine. Quality sits below DeepL and the AI models, so it is the quickest way to a translated site rather than the finest one — but everything it translates is kept, so adding a provider later never repeats the work. It needs Chrome, or Edge 148 or later, on a computer that can run the built-in model: Windows 10 or 11, macOS 13 or later, Linux or ChromeOS (not Windows Server), 16 GB of RAM or a graphics card with more than 4 GB, and 22 GB of free disk space, with the admin on https. Anywhere else, the copy-and-paste route works in any browser and still needs no key. Beyond that you can click any text on the live page and type its translation, edit it again later, and publish it. Every field also offers a free Google Translate link you can paste back from. AI keys are optional and only used at the moment you ask for one. Two minutes, filmed on a real site: translating a page with no key at all. ### Do my translations stay on my site? Yes. Translations are stored in your own WordPress database. Text is only sent to the AI provider you configure, at the moment you ask for a translation. ### Does it work with caching plugins? Yes. Each language lives under its own URL (e.g. `/it/`), so page caches store each language separately and automatically. ### Does it work with WooCommerce? Yes. Product pages, categories and attributes are translated like any other content, and slugs are translated per language. It also covers the parts WooCommerce renders outside the page HTML, which a page-only engine misses: the AJAX mini-cart fragments, strings passed to JavaScript (such as the “View cart” link), and transactional emails— the order’s language is recorded at checkout (classic and block/Store API) and the customer email is rendered in that language. Wording that only ever appears inside an email (WooCommerce’s own “Thank you for your order”, “Quantity”, “Price”) is picked up automatically the first time such an email is sent and filed under “WooCommerce emails” in the translation screens, so you can translate it like anything else. Multi-currency is out of scope: TranslateRocket translates, it does not convert prices. The whole shop translated, from the product page to the order e-mail: ### Does it translate forms (Forminator, Contact Form 7, WPForms…)? Yes. Labels, placeholders, options and buttons are translated with the rest of the page, whether the form is added with a shortcode, a block, a widget or a page builder such as Elementor. The messages the form plugin adds with JavaScript — validation errors, “message sent” — are translated too, on Forminator, Contact Form 7, WPForms, Gravity Forms, SureForms, Formidable and Ninja Forms. With Forminator, the thank- you message, forms loaded with “Load form using AJAX” and the e-mail notifications follow the language of the page the form was sent from; the wording of the form settings and e-mails appears under “Forms: messages and e-mails” in the translation screens once an administrator has viewed the form or a notification has been sent. To keep a notification (for example the copy for the site owner) in the source language, return false from the `trrocket_forminator_translate_notification` filter. ### Is there a PHP function that returns the current language? Yes, for theme and plugin code that needs it (the equivalent of Polylang’s `pll_current_language()`):` trrocket_current_language()` returns the code of the language of the current request, such as `en`, `fr` or `pt-br` — also in AJAX requests sent from a translated page— and `trrocket_default_language()` returns the site’s source language. Wrap calls in `function_exists()` so your code keeps working if the plugin is deactivated. ### Which plugins can I import my translations from? Yes — use **TranslateRocket Import** to bring over your existing translations. The WPML import covers both its string translations and its post-based translations( titles, slugs and matching body text), and reads directly from WPML’s tables, so it works even when WPML is already deactivated. Coming from Weglot (a hosted service)? Export your translations from the Weglot dashboard as a CSV and upload the file on the same Import screen — the columns are detected automatically and mapped to your target languages. To review the result safely, turn on **Preview mode** (“Who sees the translations” in Settings): you browse the fully translated site while visitors keep seeing the default language, and one click publishes it when you are happy. Safer still: run TranslateRocket next to your current plugin, import, and switch only when you are happy. Two minutes: ### What if a page shouldn’t exist in another language? Open the page and use the “Language visibility” box to redirect it, show a custom message, or return a 404 — per language. ### Can I show something in one language only? Yes. Wrap it in `[translaterocket_language lang="it"]…[/translaterocket_language]`— several languages work too, as `lang="it,de"` — or use `not="it"` to show it everywhere except Italian. In the block editor you do not need the shortcode: add the class` trrocket-only-it` or `trrocket-hide-it` in “Advanced Additional CSS class(es)” of any block, navigation links included. Content limited with `lang=` or `trrocket- only-` is taken to be written in that language, and is shown exactly as you wrote it. ### Can a menu item appear only in some languages? Yes. In Appearance Menus every item has a “Show in” row with one checkbox per language; nothing ticked means every language. Hiding an item hides its sub-items too. Block themes build menus with the Navigation block instead: there, give a link the class` trrocket-only-it` or `trrocket-hide-it`. ### Can I translate with ChatGPT or Gemini without an API key? Yes. Open a page in the visual editor, click “Translate page” and use “Copy with a translation prompt” — or the ChatGPT and Gemini links, which copy the same thing. The prompt carries your languages, the words you never translate, your glossary and your house style, and asks for the reply in a code block with the line numbers intact. Paste the reply in box 2 and apply it. And when a machine translation gets a word wrong, fixing it takes ten seconds: ## المراجعات ![](https://secure.gravatar.com/avatar/e69d4545bba6c95dd690daefb91d2c581fd149f1cf45dea51dae5cead7553248? s=60&d=retro&r=g) ### 󠀁[Best free translation plugin out there](https://wordpress.org/support/topic/best-free-translation-plugin-out-there/)󠁿 [giovanniter](https://profiles.wordpress.org/giovanniter/) 23 سبتمبر، 2026 Moved from a paid plugin to TranslateRocket last week. I was worried about losing my translated pages, but the built-in import worked perfectly. The setup is straightforward, no complicated API keys required. Plus, the developer support is fantastic—they replied to my support ticket thread within hours. Exactly what I needed. ![](https://secure.gravatar.com/avatar/7c4cd6c844b50f6e66fb4207860840e35c35cac11e24fc56c07e76bb62f0fecf? s=60&d=retro&r=g) ### 󠀁[Mega Plugin / Mega Support](https://wordpress.org/support/topic/mega-plugin-mega-support-2/)󠁿 [lambo59](https://profiles.wordpress.org/lambo59/) 20 سبتمبر، 2026 1 reply For me, this is the perfect plugin for translations. I highly recommend it. The support is just great. I sent an email and got a reply the same day. Thank you very much. Keep up the good work. Developers like this deserve our support. ![](https://secure.gravatar.com/avatar/7aab4147018debf832f8d79a225c803c4e2df4e2fd91e9a6d32a923d34dcd708? s=60&d=retro&r=g) ### 󠀁[Great free plugin that works better than the paid one](https://wordpress.org/support/topic/great-free-plugin-that-works-better-than-the-paid-one/)󠁿 [annapons](https://profiles.wordpress.org/annapons/) 15 سبتمبر، 2026 Our web-site needs to reach customers from different countries, all of them are talking different languages. For years we were using paid plugins that created a lot of troubles to the web-site work reducing our downloading speed capacities, creating conflicts with other plugins installed in wordpress, messing up with urls. We decided to try TranslateRocket with AI translation and actually did the best decision we could do. We are very happy with it's work and hopefully in future it will continue working in the same mode. The plugin is easy to use and is absolutely free! We are truly grateful for this service, Great job! ![](https://secure.gravatar.com/avatar/06ad32588e289deb8bdc7b473e97ccf6ce31704aa4e339f3fd136b59c5195f46? s=60&d=retro&r=g) ### 󠀁[Perfetto](https://wordpress.org/support/topic/perfetto-153/)󠁿 [diversamentearte](https://profiles.wordpress.org/diversamentearte/) 14 سبتمبر، 2026 1 reply Il plugin è perfetto, il suo creatore meriterebbe più della donazione minima per l'impegno che ha impiegato per crearlo: è uno strumento estremamente semplice e affidabile ![](https://secure.gravatar.com/avatar/16e5fafbd58a7a4dc1be17a8542f6065ab7af41edffd23de095a7f912c4c4efb? s=60&d=retro&r=g) ### 󠀁[Sito in più lingue senza problemi e con facilità!!!](https://wordpress.org/support/topic/sito-in-piu-lingue-senza-problemi-e-con-facilita/)󠁿 [santisposi](https://profiles.wordpress.org/santisposi/) 10 سبتمبر، 2026 Veramente un bel tools che funziona veramente ed ha traduzioni affidabili e ben funzionanti!Sono estremamente soddisfatto dal primo utilizzo e dalla bontà dell'applicazione. ![](https://secure.gravatar.com/avatar/73cae69ed1558ca4cbd2589fa1707dca5836fdc7de8043c596d086dedd8ecf78? s=60&d=retro&r=g) ### 󠀁[Miglior applicazione sul mercato. Sito multilingue completo ed affidabile](https://wordpress.org/support/topic/miglior-applicazione-sul-mercato-sito-multilingue-completo-ed-affidabile/)󠁿 [bob1982](https://profiles.wordpress.org/bob1982/) 26 أغسطس، 2026 1 reply Miglior sito multilingue mai provato. Consente una connessione diretta con l’utenza con traduzione immediata e puntuale. L’ho già provato in almeno sei lingue diverse. Da provare assolutamente [ إقرأ جميع المراجعات 9 ](https://wordpress.org/support/plugin/translate-rocket/reviews/) ## المساهمون والمطوّرون “TranslateRocket – Free Multilingual Translation, Unlimited Languages” هو برنامج مفتوح المصدر. وقد ساهم هؤلاء الأشخاص بالأسفل في هذه الإضافة. المساهمون * [ Federico ](https://profiles.wordpress.org/federicodev/) [ترجمة ”TranslateRocket – Free Multilingual Translation, Unlimited Languages“ إلى لغتك.](https://translate.wordpress.org/projects/wp-plugins/translate-rocket) ### مُهتم بالتطوير؟ [تصفّح الشفرة](https://plugins.trac.wordpress.org/browser/translate-rocket/)، تحقق من [مستودع SVN](https://plugins.svn.wordpress.org/translate-rocket/)، أو الاشتراك في [سجل التطوير](https://plugins.trac.wordpress.org/log/translate-rocket/) بواسطة [RSS](https://plugins.trac.wordpress.org/log/translate-rocket/?limit=100&mode=stop_on_copy&format=rss). ## سجل التغييرات #### 1.5.5 * Fix: sentences you translated with an older version show up translated in the visual editor again. Older versions collected a sentence with a link, a bold word or a line break as separate pieces, and newer ones read it as one; visitors kept seeing it translated, but the visual editor showed it in the original language with an empty box, as if the work were lost. The editor now shows it as visitors do, with the box already filled, and once after the update every such sentence whose pieces are all translated gets its whole translation saved — exactly what visitors already read. Sentences with an untranslated piece and translations you wrote yourself are left alone, and nothing is deleted. * Fix: «Translate everything in this browser — no key» no longer leaves you waiting on a browser that cannot do it. The button turns off, a progress bar shows the one-time download of the language model and then each sentence, and if the download stalls or the first sentences fail, a box right under the button explains why and offers three free ways: a free Gemini key (5 minutes, no card) with a step- by-step guide, copy Google Translate paste back, or a desktop Chrome or Edge. Before, the only sign was «0 translated · 12 ⚠» after minutes. * Fix: the setup wizard tells you at the translation step when the browser you are using cannot translate by itself (phones, Firefox, Safari), and points to the free Gemini key guide. * Fix: «Only flags on phones» hid every language name except the current one, which stayed on screen next to its flag. Found by the new live preview below. * Fix: in the dropdown switcher, a language name that is short in letters but wide on screen could be cut off in the open menu. The width now comes from the widest name as drawn, not from the one with the most letters. * Fix: admin screens no longer jump at every click. Notices from WordPress and other plugins were printed above the screen and moved under the title only once the page had finished loading — on a slow site after 2–3 seconds, pushing everything down and back. They are now in place from the start. * Improved: the switcher’s live preview is now your real switcher, drawn by the same code and CSS as your site in a frame of its own. It follows every change before you save — layout, names, colours, divider — opens and closes like on the site, and has a Desktop / Phone view. Before, it was a copy that cut names short in the dropdown and showed layout changes only after saving. * Improved: changing, adding or deleting a switcher profile, or saving, brings you back to where you were on the page, not to the top. * Improved: «Load available models» says what went wrong, right next to the button: no key yet, key refused, too many requests, or the site cannot reach the provider. Before, every case showed the same browser alert. * Found with a new check that installs TranslateRocket on a brand-new WordPress( Astra + Elementor), follows the setup as a first-time user would, and times it— on a phone-sized and a desktop screen. #### 1.5.4 * New: choose what the AI may reuse from the translation memory (AI Translation Translation memory): everything (the cheapest), everything except what the free browser translator wrote, or nothing. Moving from the free Chrome/Edge translation to an AI, every repeated sentence — menus, footer, buttons — used to be copied from the browser version and never reached the AI. Glossary terms always apply, and the browser translator itself keeps reusing everything, since it costs nothing. * New: «Improve N browser translations with AI» on the Memory screen. It sends only the sentences the browser translator wrote to your AI provider; a sentence that has a hand-written version elsewhere is copied instead of paid for, and a translation a person saved is never touched. * Fix: every admin screen fits a phone. The translation panel under the page editor squeezed the translation to one letter per line; it now shows one card per sentence, original above and translation below. The same for the translation memory, the list of pages and the progress per language; the AI provider cards no longer run past the right edge, and the language visibility menus fit the editor sidebar. * Fix: the floating language switcher no longer covers the buttons of a cookie banner. It stays above banners, as since 1.5.2, but now also moves up above any bar fixed to the bottom of the screen, and comes back down when the bar goes away. * Fix: the setup wizard shows only its three steps, without notices from TranslateRocket or other plugins. * Improved: in the list of pages, «Redo» is now «Start over» and «✖» is now «Hide»( nothing is deleted), with an info icon explaining every button; the Undo link says what it puts back. * Tested on a phone-sized and a desktop screen, 17 screens and pages checked automatically, including the visual editor and the public site as a visitor. #### 1.5.3 * New: import from Falang and Sublanguage. Both keep the translation of a page as extra fields on the original page, not as copies; TranslateRocket reads them straight from the database, so the import works after the other plugin has been switched off. Only what Falang marks as published comes across, and an empty field – which both plugins read as “use the original” – is not imported as a translation. The translated page addresses come across too (/it/chi-siamo/ stays/ it/chi-siamo/), so the links search engines already know keep working. Menu labels typed by hand come across as well, and so do the site title and the widget texts saved by Falang. * New: when an import would do harm, it stops and says why. If the plugin you are coming from says your site is written in another language than the one set in TranslateRocket, every sentence would be paired with the wrong side; now nothing is imported and a message explains what to change, instead of a silent “0 imported”. * Fix: after switching off a translation plugin, pages no longer send visitors to the home page. Falang, Sublanguage and others leave their own address rules behind; WordPress kept reading addresses with the rules of a plugin that was gone. The rules are now rebuilt on the first visit after any plugin is switched off. * Fix: the page title in the browser tab, in search results and in social previews is translated even before anyone translates it as a whole. Themes and SEO plugins glue “Page title – Site name” together; that glued sentence never existed in the plugin you imported from, while both pieces did. It is now put together from its translated pieces, and a translation of the whole title, when there is one, still wins. * Fix: texts that visitors read but that live in data attributes are translated: the column headings WooCommerce and Tutor LMS show on phones, the “Sending…” text of Beaver Builder buttons, loading texts, tooltips (BuddyPress included) and data placeholders. Every other data attribute is left alone on purpose: they are ids and keys that scripts depend on. * Fix: Divi 4 texts written differently for desktop, tablet and phone are translated for every device. Divi keeps them in a data attribute and puts them on screen with JavaScript, so a phone showed the original language. * Fix: OpenAI’s reasoning models (o1, o3, o4-mini, gpt-5 and later) work. They refuse the fixed “temperature” TranslateRocket sent for steady translations, and every request failed; it is now sent only to the models that accept it, with one more try without it for any model not known yet. * Fix: the Gemini key travels in a request header, as Google now documents, instead of in the address, where addresses end up in server logs. * Fix: a DeepL key sent to the wrong server (free and paid keys live on different ones) is retried on the other one instead of failing. * Fix: identifiers made of words joined by underscores, and lone codes with digits in them, are no longer collected as text to translate. * Tested with the real Falang and Sublanguage plugins; 682 automated checks in 45 suites, including the update from the version on WordPress.org. #### 1.5.2 * Fix: the text of a submit button is translated. That is the button of the WordPress comment form (“Post Comment”), the search button of many themes and the login button of Divi: they all keep their text in an attribute, which was never read, so those buttons stayed in the original language on an otherwise translated page. The value of a text field, a checkbox or a hidden field is deliberately left alone: there it is data being submitted, not a label, and translating it would break the form. * Fix: a picture with a version of its own per language now reaches the eye. Until now only a lone was swapped; inside a the browser picks the beside it – which is what WebP plugins produce – so the translated picture never appeared. The same now works for a video poster, for video and audio sources, for the retina version in srcset, and for lazy loading, which used to put the original picture back half a second later. * Fix: the title of an SVG icon is translated. It is the name a screen reader says out loud, and it was skipped together with the title of the page. * Fix: visitors arriving from a campaign, a social network, a newsletter or a QR code now read a page from the cache like everybody else. Their address carries tracking parameters (utm_source and the like), and any address with a parameter was treated as a page of its own that could not be cached – so the most expensive traffic was the slowest. * Fix: an edited translation shows on the site immediately. Clearing the page cache was repeated by hand in a dozen places and missing from others; it now happens inside the saving itself, once per request, whether you save one sentence or import ten thousand. The same for sites with Redis or Memcached, where the per- page maps could stay up to twelve hours behind, and for WP Fastest Cache, which was never cleared at all. * Fix: optimization plugins are told to leave the language script alone. It runs in the page head to pick the visitor’s language before the page is painted; with“ delay JavaScript until interaction” it was postponed to the first tap, so the visitor read the wrong language, and the language picker did not open on the first click. Autoptimize, LiteSpeed Cache, WP Rocket, SiteGround Optimizer, WP- Optimize and W3 Total Cache are all told now. * Fix: the floating language picker is no longer hidden behind a cookie banner. * Fix: the subject of a WooCommerce email is translated into the language of the order. The body already was, and the subject is the first thing read in an inbox. * Fix: file names, template placeholders like ${name}, style strings, email addresses, colours and product codes are no longer collected as text to translate. They were paid for like any other phrase and came back changed: a translated file name makes the picture disappear, and a “localized” email address stops being clickable. Seen on real multilingual sites while comparing them with their translations. #### 1.5.1 * Fix: coming from qTranslate-X, qTranslate-XT, WPGlobus or WP Multilang, once that plugin was switched off every page showed all of its languages one after the other, with the language markers in plain sight – the title first. The public site now shows only the part in your source language, and TranslateRocket translates it like any other text. Nothing in your database is changed, and switching the old plugin back on brings everything back as it was. * Fix: imported sentences with a link or a bold word in them are now used on the translated page when they come from Weglot, Loco Translate, Multilanguage, qTranslate, WPGlobus or WP Multilang. Weglot marks those words in its export in its own way; they are now read. * Fix: from TranslatePress, a sentence left identical by machine translation is no longer imported as its own translation. A name you kept identical on purpose, approved by a person, still is – so automatic translation never touches it afterwards. * Fix: a TMX file exported from TranslateRocket and imported again no longer loses the translation of labels and social titles that share their words with page text. A TMX from another tool now works with straight apostrophes and dashes, and reaches every place those words are used on the site. * Tested with the real plugins, in Italian, German, French, Arabic and Chinese: Bogo, TranslatePress, qTranslate-XT, WPGlobus, WP Multilang, Multilanguage, Loco Translate, plus Weglot and TMX/CSV files. #### 1.5.0 * before you confirm.” reached the translator as three separate pieces, so nobody could put the words in the order German or Japanese needs, and “Read the” on its own is not translatable at all. The sentence now travels in one piece with numbered marks where the tags are, and the translation is put back into your own links: the address of a link always comes from your page, never from the translation. Sentences already translated keep what they have, so nothing you have done is lost, but the count of phrases to translate will go up: the whole sentences are new to the plugin. * New: “Next steps”, a screen of its own, first in the TranslateRocket menu, with a number beside it when something is waiting. It says where your site is right now and what is left to do, with a button for each step, and it is worked out from your site every time you open it. The same panel appears at the top of the main screen. It also says, plainly, when there is nothing to do: the steps that tell you to leave something alone matter as much as the ones that ask for work. * New: while another translation plugin is active, an administrator looking at the public site now sees one line saying that TranslateRocket is standing aside on purpose and nothing is broken. Somebody spent hours hunting a fault that was not there, because the right behaviour and a broken plugin looked identical. * New: the menus another plugin keeps one per language are now named on the Import screen, with the reason you can leave them exactly where they are. Switching that plugin off keeps the menu of your main language in every position; the others simply stop being used. * New: deactivating TranslateRocket asks once, and only once, what went wrong. Answering is optional, the plugin deactivates either way, and nothing is sent anywhere: the answer stays on your site and a button copies it for you if you want to send it yourself. * New: the support screen and the support page now say exactly what makes a report easy to fix: the address of a page, the exact words, and the piece of the page copied as code. * Fix: a page built with a page builder now brings its translations with it. Elementor keeps every word of a page in a meta field of its own, not in the page content, so importing from WPML or Polylang used to bring over the title and the excerpt and nothing else — on exactly the sites with the most translation work behind them, since Polylang or WPML plus Elementor is one of the commonest ways to build a multilingual site. The two copies are now read side by side and paired widget by widget, by the id of the widget, so a widget added in one language only does not throw everything after it out of line. Anything identical in both languages is left alone, and an address is never stored as the translation of another address. Bricks is read the same way. Found while looking into what a user who left had been through. * Fix: translations imported from Polylang, WPML and the other plugins that keep a copy of each page per language are now actually used when a sentence has an apostrophe, quotes, a dash or an ampersand. WordPress shows “don’t” as “don’t” and ” – ” as ” – “: the imported sentence was stored as it was typed, the page was read as it is shown, the two never matched, and the page stayed in the source language with nothing to say why. Both shapes are stored now. * Fix: a sentence that is the same in both copies is no longer imported as its own “translation”. It used to count as translated, stay in the source language on the translated page, and be skipped by automatic translation for good. * Fix: an ampersand in an imported translation no longer shows up as “&” on the translated page. * Fix: blocks that keep their text in their settings rather than in their HTML — Spectra 3 is one — are imported too. On a page built that way, only a handful of lines used to come across. * Fix: an imported paragraph with a link or a bold word in it is now used on the translated page. Since 1.5.0 the engine reads such a sentence whole, with numbered marks where its links are; the importer stored it with the links stripped, so the two never matched. Imported sentences now take the engine’s own shape, and are paired only when both copies carry the same links in the same places. * Fix: the import no longer takes styles (gradients, colours), a pattern’s own description or text damaged by a bad save for sentences to translate. * Fix: after the switch from WPML or Polylang, an old address under that plugin’s own language prefix – /zh-hans/ where TranslateRocket uses /zh/, and likewise zh-hant or pt-pt – answered “page not found”. It now leads to the translated page with a permanent redirect. Only prefixes the other plugin really used on your site are recognised, only addresses that would otherwise be “not found” are touched, and nothing changes while the other plugin is still active. * Fix: a copy left by WPML or Polylang whose text had all been imported was reported as having one text not imported when a sentence contained an ampersand or a typographic apostrophe, so it was offered to be kept and stayed online as a second page. The review now compares the sentences in the same shapes the import stores. * Fix: the advice about headers and footers in several languages never actually appeared. The templates were read with a query that Polylang and WPML filter by language, so the plugin saw one language, concluded there was nothing to say, and stayed silent — exactly on the sites that needed the advice. They are now read straight from the database. The same screen also names the menus another plugin keeps per language, and the product template of a page builder, which were missed before. * Fix: the advice about headers and footers in several languages used to say the copies “can go” without saying that you do not have to change anything and that they come straight back from the Trash. Written that way, it could cost somebody their header. * Fix: WordPress strips anything between angle brackets when it cleans up a form field, which would have thrown away the marks inside a sentence: a correction typed by hand could never have been saved. Corrections that lose those marks are now refused with an explanation instead of being stored unusable. #### 1.4.6 * New: the names in “Words & phrases” (Exclusions screen) now stay as they are inside sentences too. Until now a name was protected only when the whole text was the name: “LifeStyle-Shop” alone stayed, but “Willkommen im LifeStyle-Shop” came back from DeepL as “Benvenuti nel negozio LifeStyle”. Now DeepL receives the name marked with its own “do not translate” tag, Google Cloud with translate =”no”, and the AI models are told which names to copy exactly. Sentences without a protected name are sent exactly as before. Sentences already translated keep their translation: correct them in the visual editor, or use Redo on the page to translate it again. Asked for by a shop owner in Switzerland. #### 1.4.5 * Fix: a page edited in the block editor now reaches visitors at once. The block editor saves over the REST API, and the cache of translated pages was only being cleared from the classic admin screens, so visitors kept seeing the old translated page for up to six hours while the administrator – never served from the cache– saw the new one. The same happened to a product renamed through the store API and to a header or footer edited in the Site Editor of a block theme. Reported by a site that put a page back into separate blocks and kept seeing the old single block on the translated pages. * Change: the cache of translated pages is also cleared when a page is trashed or restored, and when widgets, menus, the customizer or a product are saved outside the admin screens. Autosaves and revisions never clear it, since every clearing also purges the host cache. #### 1.4.4 * Fix: words that a script writes into a placeholder already on the page are collected too. Consent plugins do exactly that – Complianz prints “{title}” in the banner and fills in the names of your privacy and legal pages when the script runs – and those two links could not be translated at all, because TranslateRocket was only watching for text that gets added, not for text rewritten in place. Reported with a screenshot, which is the only way it could have been found. * New: coming from Polylang or WPML with a header and a footer per language? The Import screen now says so, and says what to do: TranslateRocket translates the one header and the one footer you already have, so the copies can go and a single switcher replaces the three language menus. Text inside a duplicated template could never be translated – it was a second template that had never been in the source language – and nothing explained why. * Change: the Translations screen now says where the text of pop-ups and cookie banners comes from: it appears once you have opened the pop-up yourself, as an administrator, on a page in your source language. #### 1.4.3 * New: in the visual editor, text that JavaScript adds to the page – a consent banner, a pop-up – can now be clicked and translated like the rest of the page. Until now only the text printed by the server could be clicked; the banner had to be translated from the Translations list. Tested with Complianz, CookieYes, GDPR Cookie Compliance and Cookie Notice. * Fix: consent banners that build themselves the moment the page is ready (CookieYes among them) are now collected too – the collector was starting a few milliseconds after them. Tested with CookieYes, GDPR Cookie Compliance and Cookie Notice: the banner text reaches the translation screens and visitors see it translated. * Fix: page builders at work are left alone. When Elementor, Beaver Builder, Divi, Bricks, Oxygen, Breakdance, Brizy, WPBakery, Thrive Architect or the Customizer load a page to edit or preview it, TranslateRocket no longer collects their interface text (“Edit Header”, “Drag widget here”…), no longer translates the canvas and hides the floating switcher there. Header, footer and popup templates opened on their own are not filed as pages either. New filters: `trrocket_builder_request`,` trrocket_builder_template_types`. * Fix: text meant for administrators only is no longer collected as page text. Debug panels, page-builder helpers and notes tools (Query Monitor, Elementor’s editor helpers and Notes, the admin bar) are left alone, both in the page and in the text JavaScript adds later; and text JavaScript adds while hidden – dialogs, templates, collapsed helpers – is not collected until it is actually shown. The` trrocket_tool_prefixes` filter extends the list. * New: the separate pages left by Polylang, WPML or Bogo are now easy to spot. Once that plugin is deactivated, each copy is labelled in Pages and Posts (“Left by Polylang · Français — original: About us”), and a notice on those screens and on the Dashboard counts them and leads to “Review the separate pages”. * New: “Translate again” for one page. In the Translations list every page now has a Redo button (and an X to remove it from the list): it removes that page’s translations and its translated address for the language, so the page is translated from scratch with AI, in the browser or by hand. Nothing is lost: an Undo link puts everything back, and the last ten removals are kept. * Change: “Review the separate pages” says clearly that a page restored from the Trash is back at its old address at once. * Fix: text that JavaScript adds after the page has loaded – cookie and consent banners, pop-ups, AJAX results – now reaches the translation screens. When an administrator views a page in the source language, that text is filed with the page like the rest, so it can be translated and is then shown translated to visitors. Before, only text already translated elsewhere could be shown, so most cookie banners stayed in the source language. * Thanks to Alain, who tested every beta of this release on a real Polylang + Elementor + Forminator site and reported each of these issues with patience and precision. #### 1.4.2 * New: side by side, the preview is one click away. The Languages page shows a Preview panel with a button for each language, the admin bar has a Preview menu that opens the page you are looking at in another language (and a way back to the live site), and every published row in Pages and Posts has a Preview link. Before, the preview meant typing ?trr-preview= into the address. * Change: when the browser cannot translate, the panel now says what the translator built into Chrome and Edge needs (Windows 10 or 11, macOS 13+, Linux or ChromeOS but not Windows Server, 16 GB of RAM or a graphics card with more than 4 GB, 22 GB of free disk space, Edge 148+, https), instead of only saying that the browser has no translator. #### 1.4.1 * Fix: validation and “message sent” messages of forms added with the Elementor widget, the Forminator block, a widget area or a template stayed in the source language; the message translator was loaded only when the form was a shortcode in the page content. It is now loaded whenever a Forminator, Contact Form 7, WPForms, Gravity Forms, SureForms, Formidable or Ninja Forms form actually appears on a translated page. * New: Forminator messages returned by the server (thank-you message, invalid form, field errors) and forms loaded with “Load form using AJAX” are shown in the visitor’s language. * New: Forminator e-mail notifications are sent in the language of the page the form was submitted from. Their subject and body, and the form’s messages, are listed under “Forms: messages and e-mails” in the translation screens. The `trrocket_forminator_translate_notification` filter keeps a notification in the source language. * New: PHP functions for developers, `trrocket_current_language()` and `trrocket_default_language()`. * Fix: side-by-side mode no longer switches itself on when another translation plugin is activated on a site that TranslateRocket was already serving: the translated addresses stay online, and a notice offers “Run side by side” instead. * Fix: when the other translation plugin goes away without anyone opening wp-admin( WP-CLI, a folder removed, another site of a network), the translations are still shown to administrators only until “Go online”. * Fix: after “Go online”, languages that are still offline are named in the notice, with a link to switch them on. * Fix: side by side, the pages served by the other plugin in its own languages are no longer collected as source text. * Fix: side by side, blocks and menu items limited to some languages are not hidden on the other plugin’s pages. * Fix: on a previewed page (?trr-preview=xx) the links keep the preview; the “Translate my homepage now” button of the setup wizard opens a preview instead of the other plugin’s address. Preview pages also send noindex and no-cache headers. * Fix: on a fresh install the source language is derived correctly for Norwegian( nb_NO, nn_NO) and Traditional Chinese (zh_TW, zh_HK) sites, and falls back to English for locales the catalogue does not have instead of a code that matches nothing. * Fix: the forms message translator and Forminator only use languages that are online for visitors; an offline language stays private to administrators. * Fix: a form message, e-mail body or AJAX-loaded form containing a stray closing tag is left untouched instead of being cut short. * Fix: uninstalling with “delete data” also removes the side-by-side, wizard, log and cache options. * Fix: three interface strings that shipped untranslated (“%1$d of %2$d translated”, the “Want a hand with your site?” card). #### 1.4.0 * New: side-by-side mode. TranslateRocket can now be activated next to WPML, Polylang, TranslatePress, Weglot, GTranslate, qTranslate-XT, WPGlobus, WP Multilang, Bogo or Multilanguage without changing anything on your public site. While the other plugin is active, visitors see the site exactly as … ## ميتا Meta * Version **1.5.5** * Last updated **قبل 9 ساعات** * Active installations **10+** * WordPress version ** 5.6 أو أعلى ** * Tested up to **7.1.2** * PHP version ** 7.4 أو أعلى ** * Language * [English (US)](https://wordpress.org/plugins/translate-rocket/) * Tags * [language](https://ar.wordpress.org/plugins/tags/language/)[multilingual](https://ar.wordpress.org/plugins/tags/multilingual/) [translate](https://ar.wordpress.org/plugins/tags/translate/)[translation](https://ar.wordpress.org/plugins/tags/translation/) [woocommerce](https://ar.wordpress.org/plugins/tags/woocommerce/) * [عرض متقدم](https://ar.wordpress.org/plugins/translate-rocket/advanced/) ## التقييم 5 من 5 نجوم. * [ 9 5-star reviews ](https://wordpress.org/support/plugin/translate-rocket/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/translate-rocket/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/translate-rocket/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/translate-rocket/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/translate-rocket/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/translate-rocket/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/translate-rocket/reviews/) ## المساهمون * [ Federico ](https://profiles.wordpress.org/federicodev/) ## الدعم لديك شيء لتقوله؟ بحاجة الى مساعدة؟ [عرض منتدى الدعم](https://wordpress.org/support/plugin/translate-rocket/) ## تبرع هل ترغب في تقديم دعم متقدم لهذه الإضافة؟ [ تبرع لهذه الإضافة ](https://translaterocket.com/donate/)