Plugin description
The "Auto Translation Pro - translation at the touch of a button" plugin forms the centrepiece of the popular Auto Translation Pro Series and enables you to translate your product texts and variants fully automatically. With just one click, you can translate content into different languages directly and conveniently in the Shopware backend.
Our plugin is modular and allows you to seamlessly integrate additional functions via our plugin family. At the bottom of this page you will find detailed information on the various functions and configuration options as well as a helpful FAQ.
Plugin features and functions
Translation Pro Plugin Family
Auto Translation Pro: General questions
To configure the plugin, please follow the steps below:
1. Upload the app in the administration under "Extensions/My Extensions".
2. Install and activate the app.
3. Go to the app configuration and add the translation service ID you need.
4. Create a Private Key for the translation service you want, we recommend DeepL. Note that you need the Developer Package to get a DeepL key.
If you use a Google Translate API Key, add this as well.
5. Check in the app configuration whether the private key is valid for the desired translation service.
6. Go to "Settings/Shop/Languages" and specify a source language and the desired translation API for the languages to be translated.
7. Once the language is configured, you can use it for translation.
If you would like to test the result before purchasing an API key, you can enter your text on the following pages and view the result:
DeepL Translation
Google Translator
The translation button is located under "Catalogue/Products/ProductX" next to the cancel button.
This error can occur if the database table was not created correctly during installation. This can be added with the following SQL commands.
Table 1
CREATE TABLE IF NOT EXISTS biloba_intl_translation_log (
id BINARY(16) NOT NULL,
initiator VARCHAR(255) NOT NULL,
entity_id BINARY(16) NOT NULL,
target_language_id BINARY(16) NOT NULL,
entity_type VARCHAR(255) NOT NULL,
type VARCHAR(255) NOT NULL,
status VARCHAR(255) NOT NULL,
context JSON NOT NULL,
created_at DATETIME(3) NOT NULL,
updated_at DATETIME(3) NULL,
PRIMARY KEY (id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
2. table
CREATE TABLE IF NOT EXISTS biloba_intl_translation_config (
id BINARY(16) NOT NULL,
source_language_id BINARY(16),
target_language_id BINARY(16) NOT NULL,
translation_api VARCHAR(255) NOT NULL,
created_at DATETIME(3) NOT NULL,
updated_at DATETIME(3) NULL,
PRIMARY KEY (id),
CONSTRAINT fk.biloba_intl_translation_config.target_language_id FOREIGN KEY (target_language_id)
REFERENCES language (id) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT fk.biloba_intl_translation_config.source_language_id FOREIGN KEY (source_language_id)
REFERENCES language (id) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
There is a current issue with Shopware that may be similar to your problem. Please have your IT check the corresponding database table and change it to the correct ISO specification if necessary.
To the Shopware Issue
There is currently an error in Shopware that the wrong ISO code is stored in the database table for the text modules. This setting cannot be changed via the admin area, but must be entered directly in the snippet_set database table. Please make sure that the ISO code is also entered that is stored for the language in the settings under Language.
To make the translation button clickable, you have to create and activate the language in the backend as usual. This corresponds to the standard procedure in Shopware. Note, however, that the language only becomes visible in the frontend when you assign it to a sales channel. This way you can use the translation function without making the entire language publicly available.
Shopware uses the following inheritance sequence for the experience worlds:
- The main language inherits from the world of experience.
- The new language inherits from the main language.
If changes are now made to the layout area in the main language, the changes are adopted in the new language, as the new language inherits from the main language.
When the translation is started, the translatable elements from the main shop language are transferred to the new language, which are the text elements. The images are now taken from the original, the world of experience, as the new language no longer inherits from the main shop language, but now from the world of experience and the images are not "translatable".
Shopware 6 currently has an error that the sample images of the world of experience are not displayed, therefore no images are currently displayed after the translation.
The SEO URLs are generated by Shopware from the category title. This part is not translated by the extension.
These links are not recognised as links by our extension because the meta description cannot be edited with an HTML editor.
If these links are not to be translated, it is possible to create a new entry in the lexicon extension and enter this link in all required languages.
The translations of the extension are processed in the background via the Shopware Scheduler.
This stores the individual translations in the database table "messenger_messages" (version 6.5 & 6.6) or "enqueue" (version 6.4) with the help of the message queue. There you can also check whether entries are generated. As soon as a translation has been initiated, work can continue. The translation overview of the main extension shows whether articles have already been translated.
To ensure that the CLI Worker also runs when you are not logged into the admin area, it is recommended that you make the following adjustments recommended by Shopware (Set up CLI Worker).
The translations are processed via the Shopware message queue. To prevent an error on the part of Shopware from generating unnecessary costs at DeepL, we recommend activating cost control at DeepL.
These can be found in the DeepL account under "Consumption".
Auto Translation Pro Language Pack
Auto Translation Pro Bulk
Auto Translation Pro More areas
Auto Translation Pro More areas Bulk
Starte Massenübersetzungen für Kategorien, Hersteller, Eigenschaften, Erlebniswelten und mehr – dieses Bulk-Plugin ergänzt Auto Translation Pro um zusätzliche Übersetzungsbereiche.
With just one click, all content in your selected area is automatically and effortlessly translated - quickly and efficiently.
Auto Translation Pro Lexicon
Auto Translation Pro Lexicon: Frequently Asked Questions
Auto Translation Pro Blog
