Leservice client et l'emballage des commandes sur votre téléphone - découvrez l'application PrestaShop Pocket 📦
- Traduction d'une boutique PrestaShop
- Traduction en temps réel de la boutique
- Traduction en masse de la boutique
- Glossaire de traduction
- Automatisation – nous accordons de l’importance à votre temps
- Prise en charge de 31 langues
- Comparaison des licences d': Standard vs Professionnelle
- Comment commencer à travailler avec plusieurs langues dans PrestaShop ?
Description détaillée
Le module PrestaShop Translator utilise le traducteur DeepL et l'IA (Open Router).
Ce module est capable de saisir les nuances et de produire des traductions d’une précision inégalée par les solutions concurrentes.
- Traduction en masse de la boutique en plusieurs langues.
- Traduction des modifications en temps réel.
- Contexte personnalisé pour l'IA.
- Glossaires pour votre terminologie spécialisée.
Créez du contenu et traduisez-le en un seul clic
À côté de chaque champ du Back Office, le module ajoute un bouton interactif « Traduire ». Cliquez sur ce bouton et le traducteur traduira le champ dans les autres langues activées sur votre boutique.
Liberté de modification
Vous pouvez modifier manuellement le champ traduit dans chaque langue.
1
Sélectionnez les languesd'
, source et cible
2
Indiquez
les éléments de la boutique
3
Lancer la
la traduction en masse
Catalogue de produits
Traduisez tous les champs du catalogue de produits, notamment : les descriptions et les noms des produits et des catégories, les caractéristiques, les attributs, les combinaisons, les pages CMS, les balises, les URL conviviales et les champs SEO.
Modèle de boutique et modules
Traduisez les phrases présentes dans le modèle de la boutique et dans les modèles des modules installés.
Traduire les composants de la boutique
Traduisez les noms des codes de réduction, les statuts des commandes et les autres contenus dans les paramètres du Back Office.
Ignorer des éléments
Vous pouvez ignorer la traduction d'un groupe d'éléments déjà traduits et ignorer n'importe quelle plage
Vos suggestions
Le glossaire vous permettra de créer des traductions préférentielles pour n'importe quels mots et expressions, ce qui permettra au moteur de traduction de reproduire encore mieux le style et la terminologie spécialisée de votre entreprise.
Vocabulaire spécialisé
Le module utilise vos suggestions pour fournir les meilleures traductions possibles.
Créez autant de glossaires que vous le souhaitez
Dans ce module, vous pouvez créer un glossaire pour chaque paire de langues.
Vous pouvez importer et exporter ces glossaires à l’aide de fichiers CSV (Excel).
Prise en charge
HTML et CSS
- Le système reconnaît la mise en forme du texte ainsi que le code HTML et CSS présents dans les champs à traduire.
- Il traduit correctement les descriptions en blocs, les titres et les expressions cachées, par exemple le texte alternatif (alt-text).
Corrige les erreurs linguistiques
- Détecte les fautes de frappe dans le contenu et traduit correctement les phrases contenant des erreurs.
- Si, dans votre modèle, le texte ne se trouve pas entre des balises de langue, il sera nécessaire de corriger les fichiers du modèle/des modules.
Journal – aperçu du travail du traducteur
- Un journal est généré pendant les traductions.
- Vous pouvez consulter les résultats de la traduction en temps réel ou à tout moment par la suite.
Marquez les contenus dont vous souhaitez ignorer la traduction
- Vous pouvez marquer les contenus que le traducteur doit ignorer.
- Vous pouvez marquer ces contenus à l'aide de l'attribut translate="no" ou de la classe class="notranslate" (comme en CSS).
PrestaShop Translator se distingue par une précision de traduction inégalée par rapport aux autres outils de traduction et générateurs de texte.
- anglais (américain)
- anglais (britannique)
- arabe
- bulgare
- chinois (simplifié)
- tchèque
- danois
- estonien
- finnois
- français
- grec
- espagnol
- japonais
- coréen
- lituanien
- letton
- néerlandais
- allemand
- norvégien (Bokmål)
- polonais
- portugais
- portugais (brésilien)
- coréen
- russe
- roumain
- slovaque
- slovène
- suédois
- turc
- ukrainien
- hongrois
- italien
| Standard | Professionnelle | |
| Licence | À vie | À vie |
| Traducteur DeepL | ✅ | ✅ |
| Glossaires | ❌ | ✅ |
| Traducteur IA | ❌ | ✅ |
Les autres fonctionnalités du module ainsi que l'assistance sont identiques pour les licences Standard et Professionnelle.
Traducteur DeepL ou IA
Traducteur DeepL API
Un million de caractères gratuits pour commencer
Profitez de l'offre DeepL API : vous recevrez un forfait gratuit, puis vous pourrez passer à un abonnement + facturation à l'utilisation, soit environ 22 EUR pour 1 million de caractères.
Traducteur IA
Dans ce module, vous pouvez configurer votre compte OpenRouter, qui vous donne accès aux traductions d’OpenAI, Claude, Gemini et bien d’autres encore.
Basculez entre
l'API DeePL et OpenRouter
- Découvrez l'offre de l'API DeePL.
- Découvrez l'offre Open Router
Notre recommandation :
Le traducteur DeepL avec des glossaires pour une précision optimale.
Un modèle d'IA pour réduire les coûts de traduction.
Conseil :
Utilisez un modèle moins cher pour les fiches produits, et un modèle plus cher pour les textes importants pour l'image de marque (conditions générales, pages d'information). Avant de lancer le processus complet, traduisez quelques éléments et évaluez la qualité.
Quel modèle d'IA choisir ?
(prix indicatifs pour 1 million de tokens d'entrée/sortie, situation en juillet 2026)
- Modèle OpenAI (ChatGPT) offrant un très bon rapport qualité-prix : openai/gpt-4o-mini - ~0,15 $ / ~0,60 $.
- Plus cher, mais meilleure qualité : openai/gpt-4.1 - ~2,00 $ / ~8,00 $.
- Une alternative pour une qualité optimale des nuances linguistiques : anthropic/claude-sonnet-4.5 - ~3,00 $ / ~15,00 $.
Effectuez une sauvegarde de votre boutique et de votre base de données avant de lancer la première traduction !
- Back-office > « Paramètres de localisation » > Activez les langues supplémentaires et importez les paramètres par défaut (format de date, taxes, etc.).
- Accédez au module PrestaShop Translator et indiquez la langue source à partir de laquelle les traductions doivent être récupérées ainsi que la langue cible (par exemple, polonais -> tchèque).
- Sélectionnez les éléments de la boutique que vous souhaitez traduire en masse, par exemple les modules, les pages CMS, les informations sur les produits et les catégories, les articles de blog, etc.
- Cliquez sur « TRADUCTEUR » : le module commencera la traduction et vous tiendra informé de l’avancement des travaux.
- Si vous souhaitez modifier, par exemple, la description d’un produit spécifique, vous pouvez utiliser l’option de traduction du champ que vous êtes en train de modifier.
Intégration du traducteur avec les autres modules de PrestaShow
Éditeur de contenu moderne
Ce module remplacera l’éditeur de contenu par défaut de votre boutique PrestaShop. Les descriptions créées avec ce module s’affichent à merveille sur les ordinateurs et les appareils mobiles.
Gestion de plusieurs domaines
Le module prendra en charge la gestion de plusieurs domaines dans votre boutique PrestaShop. Redirigez des domaines supplémentaires vers votre boutique et associez-les aux langues et devises disponibles dans votre boutique.
PrestaShop SEO Blog
Le module PrestaShop SEO Blog vous permettra de créer des articles de blog interactifs intégrant des produits, optimisés à la fois pour les clients de votre boutique et pour les moteurs de recherche.
Disponibilité des produits par langue
Grâce à ce module, vous pourrez préparer une offre de catalogue personnalisée pour chacune des langues prises en charge.
Changelog (v2.8)
## v2.8.10 - 2026-07-02
### Fixed
- Default OpenRouter model changed from `anthropic/claude-haiku-4-5` to `openai/gpt-4o-mini`. The previous default was not a valid OpenRouter model id (the real Anthropic id uses a dot: `anthropic/claude-haiku-4.5`), so an unconfigured OpenRouter provider failed on the first `/chat/completions` call and translation never ran until the user manually changed the Model field. The new default is a valid, low-cost id that supports the structured-output (`json_schema`) response format the module requires. The Back Office model placeholder and suggestion list were updated to valid ids as well.
## v2.8.9 - 2026-06-16
### Added
- Product tag translation support (`TagTranslationService`). PrestaShop stores tags in `ps_tag` with an `id_lang` column directly in the main table (no `*_lang` table), so the existing ObjectModel scanner never picked them up. The new service scans source-language tags per product, compares counts against the target language, and translates the missing ones via direct `ps_tag` / `ps_product_tag` inserts. The operation is idempotent: re-running never creates duplicate tag rows or product links. Exposed as the `TAG` status type and `translateTag` AJAX action in the Back Office.
## v2.8.8 - 2026-06-15
### Fixed
- The inline friendly-URL slugify fix now also covers CMS pages and CMS categories (whose field is named `friendly_url`), so their translated friendly URLs are saved as valid slugs instead of plain translated text with spaces and accents.
## v2.8.7 - 2026-06-15
### Fixed
- Translating a friendly URL with the inline field button now produces a valid slug (no spaces or accented characters) instead of plain translated text — e.g. a Czech friendly URL is saved as `co-by-mela-mit-fotbalova-branka` rather than `co by měla mít fotbalová branka`.
## v2.8.6 - 2026-06-10
### Fixed
- `link_rewrite` with spaces or non-ASCII characters (e.g. `nauji produktai`, `nové-produkty`) stored by an older module version is no longer treated as already translated. The scan now detects invalid slugs and re-queues them so `saveTranslations()` can re-slugify via `Tools::str2url()`.
- Products created without a friendly URL in the source language (empty `link_rewrite`) now still receive a translated slug in the target language — the scan falls back to the source `name` as the slug-generation phrase.
## v2.8.5 - 2026-06-03
### Fixed
- "Translate missing" leaving a permanent residual (e.g. stuck at "1 missing") for `link_rewrite` slugs the translator only changes in letter case/spacing (e.g. "midland …" → "Midland …"). `str2url()` collapses those back to the source slug, so the cell stayed `target == source` and was reported missing forever (and re-sent to the paid API every pass). Such cells are now detected by comparing slug forms and recorded as non-translatable, so the next scan excludes them.
## v2.8.4 - 2026-06-03
### Fixed
- "Translate missing" reaching 100% while products were still reported as missing after a refresh (forcing repeated clicks). The progress bar counted every saved cell as translated — including content the translator returns verbatim (untranslatable product slugs / model numbers) or empty — so it hit 100% while those cells stayed missing on the next scan. Now only genuinely changed, non-empty results count as translated; empty results are left for retry; unchanged results are still stored so they are excluded from the missing count. The Back Office now drives completion from the server's authoritative remaining-missing count (recomputed after saving) and stops when a pass makes no further progress, instead of trusting the inflated translated count — which also stops re-sending untranslatable phrases to the paid translation API every pass.
## v2.8.3 - 2026-06-03
### Performance
- ObjectModel mass translation (products, categories, …) on large catalogues: rewrote the scan so it no longer issues one DB query per object (source lookup) and one per already-translated cell (NonTranslatable lookup). Source rows and NonTranslatable phrases are now resolved in batches per page, turning hundreds of thousands of queries per AJAX request into a few. This fixes the case where a single translate request advanced by only one product after ~30 s on a 60k+ product shop.
- PS1.6 path: the catalogue is now paged in bounded windows instead of loading the entire `*_lang` table into memory (out-of-memory risk on very large catalogues).
- Removed the hard-coded 100,000-object scan cap that silently truncated catalogues larger than 100k products.
- Paging is now ordered by primary key so large catalogues cannot skip or re-read rows between pages.
## v2.8.2 - 2026-06-02
### Fixed
- JS cache busting: dynamicTranslation.js URL now includes the module version as a query parameter so browsers and CDNs always fetch the latest script after a module update instead of serving a stale cached copy
- "Translate into all other languages" button on individual fields: rewrote to fire all target-language requests in parallel via Promise.all and wait for all to complete before changing the UI state; the old implementation used Array.map with fire-and-forget async callbacks which caused state race conditions - setState(IDLE) from the first completed language fired while other languages were still translating
## v2.8.1 - 2026-06-01
### Fixed
- ObjectModel mass translation (e.g. categories): the phrase "total" counter no longer includes cells whose source field is empty. Such cells can never be translated, so counting them made progress stall short of 100% (e.g. 5992/25080) and "Re-translate all" looked like it stopped early. The total now equals the number of phrases actually processed.
- "Re-translate all" no longer aborts with "Cannot rewind a generator that was already run". After skipping `reTranslateAllOffset` items, the batch loop now iterates the generator manually (while/current/next) instead of `foreach`, which tried to rewind an already-started generator.
- NonTranslatable cache for `link_rewrite` fields: the "non-translatable" lookup now uses the same dashes-as-spaces phrase that is sent to the translator and stored, so a non-translatable slug is cached correctly instead of being re-sent to the API on every run.
- Translation UI no longer gets stuck on "Translating..." after an error. Previously a network/non-JSON error left the row spinning with the action buttons hidden and the whole queue jammed; the queue item is now always released, so the buttons reappear and clicking "Translate missing" resumes from where it stopped.
## v2.8.0 - 2026-05-14
### Added
- "Retranslate all in this section" button (yellow) next to the existing missing-only button — re-translates every phrase in a section from scratch, overwriting current translations (with a confirmation prompt)
## v2.7.2 - 2026-05-12
### Fixed
- PrestaShop 1.6 — "Translate All" for a module domain (e.g. paymentConfirmation) now overrides previous translations as expected; saved keys are lowercased to match PrestaShop's lookup
## v2.7.1 - 2026-05-12
### Fixed
- In-admin translate widget no longer reads the source text from a different translatable field when the form layout nests language tabs at uneven depths (e.g. cz_imageslider's custom file_lang and autoload_rte templates)
## v2.7.0 - 2026-04-22
### Added
- OpenRouter (AI) translator with editable system prompt (context, vocabulary, tone) — Pro license
- "What to translate" filter (all / objects / modules / configuration / front theme)
- "Skip disabled modules" toggle
### Fixed
- PrestaShop 9 compatibility (in-admin translate buttons, theme translation stats, product save)
## v2.6.9 - 2026-03-13
### Fixed
- Support with non-standard editor modules
## v2.6.8 - 2026-03-12
### Added
- Added configuration domain for translation
## v2.6.7 - 2026-03-10
### Fixed
- Fixed "Failed to update API key." error
## v2.6.6 - 2026-02-24
### Fixed
- Fixed theme translations not being assigned to the theme in the database
## v2.6.5 - 2025-01-22
### Added
- Support for Norwegian and Slovenian language translation
## v2.6.4 - 2025-12-11
### Added
- Updated list of supported languages for translate
## v2.6.3 - 2025-12-06
### Added
- Updated list of supported languages for translate
## v2.6.2 - 2025-11-26
### Added
- Updated list of supported languages for glossaries
## v2.6.1 - 2025-11-05
### Fixed
- Improved theme translation lookup
## v2.6.0 - 2025-11-05
### Added
- Support for translating input fields inside iframes — for example, when adding a new file on the product edit form
## v2.5.7 - 2025-10-13
### Fixed
- Improved translation of module configurations
## v2.5.6 - 2025-09-23
### Fixed
- Suppport gb and us source languages
## v2.5.5 - 2025-07-14
### Fixed
- Better API error handling
## v2.5.4 - 2025-07-10
### Added
- Added option: Stop translation on first error occured
## v2.5.3 - 2025-07-01
### Fixed
- Improved translating long text
## v2.5.2 - 2025-06-18
### Fixed
- Improved loading translations in the module configuration
## v2.5.1 - 2025-05-05
### Fixed
- The compatibility problem with newer php versions
## v2.5.0 - 2025-01-14
### Added
- Support DeepL API changes from March 2025
## v2.4.10 - 2024-11-22
### Fixed
- The problem with the button for quick translation of text fields in prestashop 8.2
## v2.4.9 - 2024-10-21
### Fixed
- Translating fields in third party modules
## v2.4.8 - 2024-07-04
### Fixed
- Automatic usage of glossaries for translations
## v2.4.7 - 2024-05-14
### Fixed
- Translating phrases added to the custom translation domain in the theme files
## v2.4.6 - 2024-04-29
### Fixed
- Translating hardcoded phrases from template files
## v2.4.5 - 2024-04-16
### Fixed
- ObjectModel classes finder
## v2.4.4 - 2024-03-28
### Fixed
- Support prestashop 1.7.2
## v2.4.3 - 2024-03-18
### Added
- Support module ph_simpleblog
## v2.4.2 - 2024-01-16
### Fixed
- Fix typing
## v2.4.1 - 2024-01-11
### Fixed
- Improved translating when there are thousands of records in the database
## v2.4.0 - 2023-11-28
### Added
- Allow to translate very long texts thanks to the splitting into smaller parts - DeepL API limit is 128kb per request
## v2.3.0 - 2023-11-08
### Added
- Support glossaries: user can manage glossaries in the module; glossary will be automatically used for all translations
## v2.2.6 - 2023-10-03
### Fixed
- Improve support for Prestashop 8.1
## v2.2.5 - 2023-09-08
### Fixed
- Decrease num of texts translating at once
## v2.2.4 - 2023-08-24
### Fixed
- Fix translator url when back-office is running on no main domain
## v2.2.3 - 2023-08-21
### Fixed
- Prestashop 8.0.4 require to save module translations into `modules/*/translations/*.php` file
## v2.2.2 - 2023-07-26
### Fixed
- Skip searching for ObjectModel in modules where `_` has been added to the directory name
## v2.2.1 - 2023-07-21
### Fixed
- There was a problem with the 'preview' button on the product edit page in the admin panel
## v2.2.0 - 2023-07-19
### Added
- Added support for Prestashop 8.0 and 8.1
- Added support for PHP 8.1
- Improved error handling
## v2.1.4 - 2023-07-05
### Added
- Dispatch 'change' event while updating textarea to improve compatibility
## v2.1.3 - 2023-05-24
### Added
- Add support for lang KO - Korean
- Add support for lang TR - Turkish
- Add support for lang UK - Ukrainian
- Add support for lang NB - Norwegian (Bokmål)
## v2.1.2 - 2023-05-19
### Fixed
- Optimized object model loading
- Fixes for Prestashop 1.7.7
- Service refactoring
## v2.1.1 - 2023-05-02
### Fixed
- Small fix for multistore support
## v2.1.0 - 2023-04-27
### Added
- Added support for Prestashop 1.7.5 and older
## v2.0.4 - 2023-03-30
### Fixed
- Small fix for output buffer
## v2.0.3 - 2023-03-24
### Fixed
- Fix for protected method Link::getBaseLink() on some Prestashop versions
## v2.0.2 - 2023-02-17
### Fixed
- check if files of the installed module exist before trying to translate them
## v2.0.1 - 2023-02-16
### Fixed
- catch error while some database tables are missing
## v2.0.0 - 2023-02-15
### Added
- allow translating front theme and modules using translations from other language as a source instead of phrases directly from files
- allow translating phrases from single module files
### Fixed
- most of the algorithms have been rewritten for more accurate and stable operation
- update dependencies
## v1.4.4 - 2023-02-08
### Fixed
- additional fix for: automatically convert target language to en-us, en-gb, pt-pt, pt-br
## v1.4.3 - 2023-01-24
### Fixed
- automatically convert target language to en-us, en-gb, pt-pt, pt-br
## v1.4.2 - 2023-01-17
### Fixed
- improve translating link_rewrite field
## v1.4.1 - 2022-10-13
### Fixed
- Improve modules translation - better searching for translatable elements
## v1.4.0 - 2022-07-29
### Added
- Add translation logging
- Add log viewer in the back-office
- Allow translating inputs with tags (e.g. cms page meta keywords)
### Fixed
- Improve translating single fields in the back-office
- Fix translating special chars in non-html fields (e.g. `&` was wrongly changing to `&`)
## v1.3.4 - 2022-07-20
### Fixed
- Fix not found Translation Service
## v1.3.3 - 2022-07-14
### Fixed
- The problem with undefined variable in module settings
## v1.3.2 - 2022-07-12
### Fixed
- Catch errors caused by duplicated class names
- Catch exceptions thrown because of missing database tables
## v1.3.1 - 2022-07-11
### Fixed
- Changed CDN JS to local files
## v1.3 - 2022-05-30
### Fixed
- Fix issue with missing translation service on PrestaShop version 1.7.4 and lower
## v1.2 - 2022-05-17
### Fixed
- Improve dynamic translation in single fields
- Search for objects (ObjectModel) to translate in the main module directories
## v1.1 - 2022-05-16
### Added
- Support PrestaShop 1.7
## v1.0 - 2022-04-08
### Added
- Allow translating phrases from template files
- Allow translating phrases from modules files
- Allow translating fields from \ObjectModel objects
### Fixed
- Default OpenRouter model changed from `anthropic/claude-haiku-4-5` to `openai/gpt-4o-mini`. The previous default was not a valid OpenRouter model id (the real Anthropic id uses a dot: `anthropic/claude-haiku-4.5`), so an unconfigured OpenRouter provider failed on the first `/chat/completions` call and translation never ran until the user manually changed the Model field. The new default is a valid, low-cost id that supports the structured-output (`json_schema`) response format the module requires. The Back Office model placeholder and suggestion list were updated to valid ids as well.
## v2.8.9 - 2026-06-16
### Added
- Product tag translation support (`TagTranslationService`). PrestaShop stores tags in `ps_tag` with an `id_lang` column directly in the main table (no `*_lang` table), so the existing ObjectModel scanner never picked them up. The new service scans source-language tags per product, compares counts against the target language, and translates the missing ones via direct `ps_tag` / `ps_product_tag` inserts. The operation is idempotent: re-running never creates duplicate tag rows or product links. Exposed as the `TAG` status type and `translateTag` AJAX action in the Back Office.
## v2.8.8 - 2026-06-15
### Fixed
- The inline friendly-URL slugify fix now also covers CMS pages and CMS categories (whose field is named `friendly_url`), so their translated friendly URLs are saved as valid slugs instead of plain translated text with spaces and accents.
## v2.8.7 - 2026-06-15
### Fixed
- Translating a friendly URL with the inline field button now produces a valid slug (no spaces or accented characters) instead of plain translated text — e.g. a Czech friendly URL is saved as `co-by-mela-mit-fotbalova-branka` rather than `co by měla mít fotbalová branka`.
## v2.8.6 - 2026-06-10
### Fixed
- `link_rewrite` with spaces or non-ASCII characters (e.g. `nauji produktai`, `nové-produkty`) stored by an older module version is no longer treated as already translated. The scan now detects invalid slugs and re-queues them so `saveTranslations()` can re-slugify via `Tools::str2url()`.
- Products created without a friendly URL in the source language (empty `link_rewrite`) now still receive a translated slug in the target language — the scan falls back to the source `name` as the slug-generation phrase.
## v2.8.5 - 2026-06-03
### Fixed
- "Translate missing" leaving a permanent residual (e.g. stuck at "1 missing") for `link_rewrite` slugs the translator only changes in letter case/spacing (e.g. "midland …" → "Midland …"). `str2url()` collapses those back to the source slug, so the cell stayed `target == source` and was reported missing forever (and re-sent to the paid API every pass). Such cells are now detected by comparing slug forms and recorded as non-translatable, so the next scan excludes them.
## v2.8.4 - 2026-06-03
### Fixed
- "Translate missing" reaching 100% while products were still reported as missing after a refresh (forcing repeated clicks). The progress bar counted every saved cell as translated — including content the translator returns verbatim (untranslatable product slugs / model numbers) or empty — so it hit 100% while those cells stayed missing on the next scan. Now only genuinely changed, non-empty results count as translated; empty results are left for retry; unchanged results are still stored so they are excluded from the missing count. The Back Office now drives completion from the server's authoritative remaining-missing count (recomputed after saving) and stops when a pass makes no further progress, instead of trusting the inflated translated count — which also stops re-sending untranslatable phrases to the paid translation API every pass.
## v2.8.3 - 2026-06-03
### Performance
- ObjectModel mass translation (products, categories, …) on large catalogues: rewrote the scan so it no longer issues one DB query per object (source lookup) and one per already-translated cell (NonTranslatable lookup). Source rows and NonTranslatable phrases are now resolved in batches per page, turning hundreds of thousands of queries per AJAX request into a few. This fixes the case where a single translate request advanced by only one product after ~30 s on a 60k+ product shop.
- PS1.6 path: the catalogue is now paged in bounded windows instead of loading the entire `*_lang` table into memory (out-of-memory risk on very large catalogues).
- Removed the hard-coded 100,000-object scan cap that silently truncated catalogues larger than 100k products.
- Paging is now ordered by primary key so large catalogues cannot skip or re-read rows between pages.
## v2.8.2 - 2026-06-02
### Fixed
- JS cache busting: dynamicTranslation.js URL now includes the module version as a query parameter so browsers and CDNs always fetch the latest script after a module update instead of serving a stale cached copy
- "Translate into all other languages" button on individual fields: rewrote to fire all target-language requests in parallel via Promise.all and wait for all to complete before changing the UI state; the old implementation used Array.map with fire-and-forget async callbacks which caused state race conditions - setState(IDLE) from the first completed language fired while other languages were still translating
## v2.8.1 - 2026-06-01
### Fixed
- ObjectModel mass translation (e.g. categories): the phrase "total" counter no longer includes cells whose source field is empty. Such cells can never be translated, so counting them made progress stall short of 100% (e.g. 5992/25080) and "Re-translate all" looked like it stopped early. The total now equals the number of phrases actually processed.
- "Re-translate all" no longer aborts with "Cannot rewind a generator that was already run". After skipping `reTranslateAllOffset` items, the batch loop now iterates the generator manually (while/current/next) instead of `foreach`, which tried to rewind an already-started generator.
- NonTranslatable cache for `link_rewrite` fields: the "non-translatable" lookup now uses the same dashes-as-spaces phrase that is sent to the translator and stored, so a non-translatable slug is cached correctly instead of being re-sent to the API on every run.
- Translation UI no longer gets stuck on "Translating..." after an error. Previously a network/non-JSON error left the row spinning with the action buttons hidden and the whole queue jammed; the queue item is now always released, so the buttons reappear and clicking "Translate missing" resumes from where it stopped.
## v2.8.0 - 2026-05-14
### Added
- "Retranslate all in this section" button (yellow) next to the existing missing-only button — re-translates every phrase in a section from scratch, overwriting current translations (with a confirmation prompt)
## v2.7.2 - 2026-05-12
### Fixed
- PrestaShop 1.6 — "Translate All" for a module domain (e.g. paymentConfirmation) now overrides previous translations as expected; saved keys are lowercased to match PrestaShop's lookup
## v2.7.1 - 2026-05-12
### Fixed
- In-admin translate widget no longer reads the source text from a different translatable field when the form layout nests language tabs at uneven depths (e.g. cz_imageslider's custom file_lang and autoload_rte templates)
## v2.7.0 - 2026-04-22
### Added
- OpenRouter (AI) translator with editable system prompt (context, vocabulary, tone) — Pro license
- "What to translate" filter (all / objects / modules / configuration / front theme)
- "Skip disabled modules" toggle
### Fixed
- PrestaShop 9 compatibility (in-admin translate buttons, theme translation stats, product save)
## v2.6.9 - 2026-03-13
### Fixed
- Support with non-standard editor modules
## v2.6.8 - 2026-03-12
### Added
- Added configuration domain for translation
## v2.6.7 - 2026-03-10
### Fixed
- Fixed "Failed to update API key." error
## v2.6.6 - 2026-02-24
### Fixed
- Fixed theme translations not being assigned to the theme in the database
## v2.6.5 - 2025-01-22
### Added
- Support for Norwegian and Slovenian language translation
## v2.6.4 - 2025-12-11
### Added
- Updated list of supported languages for translate
## v2.6.3 - 2025-12-06
### Added
- Updated list of supported languages for translate
## v2.6.2 - 2025-11-26
### Added
- Updated list of supported languages for glossaries
## v2.6.1 - 2025-11-05
### Fixed
- Improved theme translation lookup
## v2.6.0 - 2025-11-05
### Added
- Support for translating input fields inside iframes — for example, when adding a new file on the product edit form
## v2.5.7 - 2025-10-13
### Fixed
- Improved translation of module configurations
## v2.5.6 - 2025-09-23
### Fixed
- Suppport gb and us source languages
## v2.5.5 - 2025-07-14
### Fixed
- Better API error handling
## v2.5.4 - 2025-07-10
### Added
- Added option: Stop translation on first error occured
## v2.5.3 - 2025-07-01
### Fixed
- Improved translating long text
## v2.5.2 - 2025-06-18
### Fixed
- Improved loading translations in the module configuration
## v2.5.1 - 2025-05-05
### Fixed
- The compatibility problem with newer php versions
## v2.5.0 - 2025-01-14
### Added
- Support DeepL API changes from March 2025
## v2.4.10 - 2024-11-22
### Fixed
- The problem with the button for quick translation of text fields in prestashop 8.2
## v2.4.9 - 2024-10-21
### Fixed
- Translating fields in third party modules
## v2.4.8 - 2024-07-04
### Fixed
- Automatic usage of glossaries for translations
## v2.4.7 - 2024-05-14
### Fixed
- Translating phrases added to the custom translation domain in the theme files
## v2.4.6 - 2024-04-29
### Fixed
- Translating hardcoded phrases from template files
## v2.4.5 - 2024-04-16
### Fixed
- ObjectModel classes finder
## v2.4.4 - 2024-03-28
### Fixed
- Support prestashop 1.7.2
## v2.4.3 - 2024-03-18
### Added
- Support module ph_simpleblog
## v2.4.2 - 2024-01-16
### Fixed
- Fix typing
## v2.4.1 - 2024-01-11
### Fixed
- Improved translating when there are thousands of records in the database
## v2.4.0 - 2023-11-28
### Added
- Allow to translate very long texts thanks to the splitting into smaller parts - DeepL API limit is 128kb per request
## v2.3.0 - 2023-11-08
### Added
- Support glossaries: user can manage glossaries in the module; glossary will be automatically used for all translations
## v2.2.6 - 2023-10-03
### Fixed
- Improve support for Prestashop 8.1
## v2.2.5 - 2023-09-08
### Fixed
- Decrease num of texts translating at once
## v2.2.4 - 2023-08-24
### Fixed
- Fix translator url when back-office is running on no main domain
## v2.2.3 - 2023-08-21
### Fixed
- Prestashop 8.0.4 require to save module translations into `modules/*/translations/*.php` file
## v2.2.2 - 2023-07-26
### Fixed
- Skip searching for ObjectModel in modules where `_` has been added to the directory name
## v2.2.1 - 2023-07-21
### Fixed
- There was a problem with the 'preview' button on the product edit page in the admin panel
## v2.2.0 - 2023-07-19
### Added
- Added support for Prestashop 8.0 and 8.1
- Added support for PHP 8.1
- Improved error handling
## v2.1.4 - 2023-07-05
### Added
- Dispatch 'change' event while updating textarea to improve compatibility
## v2.1.3 - 2023-05-24
### Added
- Add support for lang KO - Korean
- Add support for lang TR - Turkish
- Add support for lang UK - Ukrainian
- Add support for lang NB - Norwegian (Bokmål)
## v2.1.2 - 2023-05-19
### Fixed
- Optimized object model loading
- Fixes for Prestashop 1.7.7
- Service refactoring
## v2.1.1 - 2023-05-02
### Fixed
- Small fix for multistore support
## v2.1.0 - 2023-04-27
### Added
- Added support for Prestashop 1.7.5 and older
## v2.0.4 - 2023-03-30
### Fixed
- Small fix for output buffer
## v2.0.3 - 2023-03-24
### Fixed
- Fix for protected method Link::getBaseLink() on some Prestashop versions
## v2.0.2 - 2023-02-17
### Fixed
- check if files of the installed module exist before trying to translate them
## v2.0.1 - 2023-02-16
### Fixed
- catch error while some database tables are missing
## v2.0.0 - 2023-02-15
### Added
- allow translating front theme and modules using translations from other language as a source instead of phrases directly from files
- allow translating phrases from single module files
### Fixed
- most of the algorithms have been rewritten for more accurate and stable operation
- update dependencies
## v1.4.4 - 2023-02-08
### Fixed
- additional fix for: automatically convert target language to en-us, en-gb, pt-pt, pt-br
## v1.4.3 - 2023-01-24
### Fixed
- automatically convert target language to en-us, en-gb, pt-pt, pt-br
## v1.4.2 - 2023-01-17
### Fixed
- improve translating link_rewrite field
## v1.4.1 - 2022-10-13
### Fixed
- Improve modules translation - better searching for translatable elements
## v1.4.0 - 2022-07-29
### Added
- Add translation logging
- Add log viewer in the back-office
- Allow translating inputs with tags (e.g. cms page meta keywords)
### Fixed
- Improve translating single fields in the back-office
- Fix translating special chars in non-html fields (e.g. `&` was wrongly changing to `&`)
## v1.3.4 - 2022-07-20
### Fixed
- Fix not found Translation Service
## v1.3.3 - 2022-07-14
### Fixed
- The problem with undefined variable in module settings
## v1.3.2 - 2022-07-12
### Fixed
- Catch errors caused by duplicated class names
- Catch exceptions thrown because of missing database tables
## v1.3.1 - 2022-07-11
### Fixed
- Changed CDN JS to local files
## v1.3 - 2022-05-30
### Fixed
- Fix issue with missing translation service on PrestaShop version 1.7.4 and lower
## v1.2 - 2022-05-17
### Fixed
- Improve dynamic translation in single fields
- Search for objects (ObjectModel) to translate in the main module directories
## v1.1 - 2022-05-16
### Added
- Support PrestaShop 1.7
## v1.0 - 2022-04-08
### Added
- Allow translating phrases from template files
- Allow translating phrases from modules files
- Allow translating fields from \ObjectModel objects
Exigences techniques
Exigences techniques
- PHP 7.1 - 8.x
- Extension serveur ionCube Loader
- PrestaShop Importer uniquement : PHP libxml version > 2.9.3
- PrestaShop Facebook Integrator uniquement : PHP 7.2 ou supérieur
- PrestaShop VAT Validator uniquement : PHP SOAP
Plus d'informations sur les exigences techniques dans la base de connaissances
Support et mises à jour
Support = Mises à jour + HelpDesk
Vous bénéficiez d'un accès de 90 jours (3 mois) au support complet de PrestaShow.
Mises à jour des modules
Les modules vous informeront des mises à jour disponibles. Lisez le journal des modifications et effectuez une mise à jour du module en 1 clic directement depuis votre boutique.
Panneau HelpDesk
C'est le panneau où nous vous fournissons de l'aide. Sur le HelpDesk, vous pouvez signaler des problèmes, commander l'installation et la mise à jour gratuites de modules, ainsi que des modifications et des travaux de développement individuels.
Prolonger l'assistanc e
Une fois l'assistance expirée, vous pouvez utiliser le module sans aucune restriction. Vous pouvez prolonger votre accès à l'assistance à tout moment lorsque vous en avez besoin.
Base de connaissances et FAQ
Gratuit pour toujours
La base de connaissances est accessible à tous. Vous y trouverez la documentation du module ainsi que des instructions, des vidéos et des réponses aux questions fréquemment posées.
Licence
Licence à vie pour le module
- Vous pouvez utiliser le module sans limitation pour 1 magasin = 1 domaine.
- Vous pouvez utiliser un domaine supplémentaire, par exemple pour une copie de développeur.
- Pour une somme modique, vous pouvez changer vous-même le domaine du module.
Domaines supplémentaires pour Multistore
- Tous nos modules supportent PrestaShop Multistore.
- La prise en charge d'un nombre illimité de domaines pour PrestaShop Multistore nécessite l'achat du support multistore pour le module.
Modifier le code
- Le code du module relatif à l'intégration avec la boutique et la conception (.tpl, .css, .js) est open source et vous êtes libre de le modifier.
- Le code source du module (.php) est crypté avec ionCube et sa modification annule la garantie.
Démo
Démo - tester le module
- Ce module n'a pas de boutique de démonstration
Aucune entrée pour le moment.
Jeśli jakieś pole ma uzupełnioną zawartość w danym języku, to moduł uznaje, że jest to pole przetłumaczone w danym języku. Jeśli pole w danym języku jest puste, to moduł oznacza to jako brak tłumaczenia. W module można masowo tłumaczyć wszystko lub tylko pola z brakiem tłumaczenia.
Automatyczne tłumaczenie aktualnie edytowanego produktu wymaga dodatkowego 1-kliknięcia przy polu, które edytujesz. Możemy rozbudować moduł, aby tłumaczenie odbywało się po zapisie produktu i nie wymagało dodatkowego kliknięcia - otwórz zgłoszenie na helpdesk.prestashow.pl
Moduł od ETS pozwala tłumaczyć opisy jeśli tekst jest 1:1 taki sam na obu wersjach, ale to nie jest idealne rozwiązanie.
Czy moduł pozwala na automatyczne tłumaczenie opisu przy zapisie produktu?