Menu Close
    Searching for an experienced Akeneo Development Company ?

    Akeneo Content Translator

    Introduction:

    Akeneo Content Translator is used to translate the localized attribute from one locale to multiple other locales. The store owner needs to map the attribute value and locale and then select the products and perform bulk action to translate the product attributes. The store owner can choose the locale and scope that will be translated to other selected locales.

    Basic Requirements:

    • This module works with Akeneo 2.0.x, 2.1.x, 2.2.x, 2.3.x, 3.0.x, 3.1.x, 3.2.x, 4.0.x, and 5.0.x. Download Akeneo from here
    • Node and Yarn packages need to be installed.
    • This module is compatible with the Akeneo community and Enterprise(Flexibility) edition.
    • If you want to use this extension on Akeneo EE Serenity mode, please contact us.
    • For the Akeneo installation, your Akeneo server should meet these system requirements.

    Features:

    • Translate localized attributes from one locale to multiple other locales.
    • Change Translation of Product and Product Module localizable text and text area type attributes.
    • Auto-translate the data from the base locale to mapped locales after saving a product.
    • Auto-translate the data from the base locale to mapped locales after bulk edit attribute.
    • Select products from the product grid to make the translation of products with a bulk action.
    • Compatible with Microsoft and Google Translation.
    • This module is compatible with Akeneo latest version 5.0.x.

    Installing Module For Version 4.0.x to 5.0.x

    Please follow these steps for installing the Akeneo content translator module in your Akeneo PIM platform.

    1 – Unzip the respective extension zip then merge the “src” folder into akeneo project root directory.

    src-4.x

    2 – Goto config/Bundles.php then add line:

    Webkul\AkeneoTranslatorBundle\AkeneoTranslatorBundle::class => ['all' => true],
    app-kernel-

    in return array.

    3 – Copy the “config” folder into akeneo project root directory for routing.

    conf-translator

    – Run this command after ssh to your akeneo server by the terminal.

    php bin/console cache:clear--env=prod;
    rm -rf ./var/cache/** && php bin/console wk-translator:setup:install

    5. If you are using php-fpm. Then you need to restart the php-fpm services and apache web server.

    sudo service php-fpm7.3 restart

    Docker Installation Command :

    For Akeneo 5

    alias docker_php='docker-compose run -u www-data --rm php php';
    alias docker_yarn='docker-compose run -u node --rm node yarn';
    docker_php bin/console cache:clear --env=prod;
    docker_php bin/console pim:installer:assets --symlink --clean --env=prod;
    docker_php bin/console d:s:u --force;
    docker_yarn run webpack;
    docker_yarn run update-extensions;
    docker_yarn run less;

    For Akeneo 4

    alias docker_php='docker-compose run -u www-data --rm php php';
    alias docker_yarn='docker-compose run -u node --rm node yarn';
    docker_php bin/console cache:clear --env=prod;
    docker_php bin/console pim:installer:assets --symlink --clean --env=prod;
    docker_php bin/console d:s:u --force;
    docker_yarn run webpack;
    docker_yarn run less;

    Installing Module for Version 2.x to 3.x

    Please follow these steps for installing the Akeneo content translator module in your Akeneo PIM platform.

    1 – Unzip the respective extension zip then merge the “src” folder into akeneo project root directory.

    src-akeneo-translator-1

    2 – Goto app/AppKernel.php then add line.

    new Webkul\AkeneoTranslatorBundle\AkeneoTranslatorBundle(),
    translatot-

    3 – Goto app/config/routing.yml then add these lines at top of file

    akeneo_translator:
        resource: "@AkeneoTranslatorBundle/Resources/config/routing.yml"
        prefix: /
    routing-translator

    4 – Run this command after ssh to your akeneo server by the terminal.

    php bin/console cache:clear--env=prod;
    rm -rf ./var/cache/** && php bin/console wk-translator:setup:install

    5. If you are using php-fpm. Then you need to restart the php-fpm services and apache web server.

    sudo service php-fpm7.2 restart

    How to Create Google API Key

    Go to https://console.cloud.google.com/

    To create your API key simply follow the steps below:

    1. Create a new Project from the top bar for that click on select a project.

    select-a-project

    2. After that click to new project then add the name and click to save button.

    New_Project_–_Google_Cloud_Platform

    2. With the new project selected, go to the hamburger menu to the left and visit API & Services from Dashboard enable Google Translate API

    dasboard

    3. Search for translate API and enable it.

    APIs_Services_translation_Google_Cloud_Platform

    4. From the credentials interface create a new API Key.

    create-credentials

    5. Restrict your API Key to a particular website

    restric-key

    After that click to save button.

    save-new

    How to Create Microsoft API Key

    To create your Microsoft API key simply follow the steps below:

    1- First, you need to log into the Microsoft Azure portal and go to create a resource.

    akeneo-translator-1

    2- Then select the Translator service and create.

    akeneo-translator-2

    3 – Provide the required details and go to the next.

    akeneo-translator-3

     4 – After Putting the tag a validation check is run.

    akeneo-translator-4

    5 – After the validation is passed, create the resource.

    akeneo-translator-5

    6 – After the creation of the resource go to the resource which you have created. (In this case akeneo)

    akeneo-translator-6

    7 – Then after that go to key and endpoints.

    akeneo-translator-7

    8 – Here, you can find your endpoint and API keys. 

    akeneo-translator-8

    Configuration

    Akeneo Content Translation after installing the module in Akeneo, navigate to the Akeneo Dashboard. Here, you will see the Webkul Content Translator icon on the left side of the screen.

    Credentials:

    Now to add Google credentials you have to navigate Webkul Content translator>>Credential. After that, select translator API mode(Microsoft or Google translation) then you have to fill the API Token.

    Locale Mapping:

    In source data mapping select a default channel and local for transaltion.

    In the Locale Mapping section, you can map the akeneo locale with the google locale code. Find the link for the locale code here – 

    For google translation https://developers.google.com/admin-sdk/directory/v1/languages

    For Microsoft translation https://docs.microsoft.com/en-us/azure/cognitive-services/translator/language-support

    Attribute Mapping:

    Attributes used to make translation – In this, you can add all the localizable attributes you can add two types of attributes text and text area attributes.

    After that click to Save button.

    Automatic Content Translation

    While creating a new product or updating the product once the user will click on the save button the value will be auto-translate the data from the base to mapped local and mapped attributes.

    As show in below image new data added in English after that click on Save button.

    Once the product will be updated select the local like German data will be automatically updated in the German language.

    In similar way while updating product in bulk action data will be automatic updated.

    Select multiple product at a time in which you want to edit the attribute value.

    After that click to Bulk action to perform the action translation. After that, it will redirect to the new page where you have to select the action.

    Then click on Next button the select the attribute which you want to edit then enter the new data.

    After clicking on next button confirm the value edited the click on the Confirm button.

    Once the job will be completed the value will be updated in all local mapped the you will be notified.

    English

    German

    Bulk Action Content Translator

    To translate the localized attribute from one locale to multiple other locales you have to go to product select the products.

    In this you can select multiple product at a time.

    After that click to Bulk action to perform the action translation. After that, it will redirect to the new page where you have to follow three steps:

    1 – Select Action

    In this, you have to select your action for the bulk action Change Translation. After that click to the next button.

    select-action

    2 – Change Translation

    To change the translation you have to fill the details like:

    • Select from locale and Select from Channel – In this, you have to select the locale and channel from which you want to change the translation.
    • Change to locale and Change to Channel – In this, you have to select the locale and channel in which you want to change the translation. You can select multiple locales in this.
    Mass-Edit

    After selecting the locale and scope click to Next button.

    3 – Confirm

    In this you have to click to Confirm to confirm the process of translation.

    Mass-Edit-1

    After click to confirm you can will recieve a notification.

    After that go to process tracker then check the execution details.

    Process_tracker-1200x597-1

    Now check the product details in different locale.

    English:

    english-2-1200x597-1

    French:

    french-1200x597-2

    Support

    This was all about the Akeneo Content Translator. I hope you must have the got the idea of our module. Thanks for taking the time in reading this blog. And also, please doesn’t forget to share your feedback and suggestions under the comment box given below.

    Moreover, If you have any queries or suggestions, then feel free to add a ticket at our HelpDesk system.

    Current Product Version - 2.1.0

    Supported Framework Version - Akeneo 2.x.x, 3.x.x, 4.x.x & 5.x.x

    Blog Version - Akeneo 2.x.x, 3.x.x, 4.x.x & 5.x.x
    • Version Akeneo 2.x.x, 3.x.x, 4.x.x & 5.x.x
    • Version Akeneo 2.0.x, 2.1.x, 2.2.x , 2.3.x, 3.0.x, 3.1.x, 3.2.x and 4.0.x
    . . .
    Discuss on Helpdesk

    Leave a Comment

    Your email address will not be published. Required fields are marked*


    Be the first to comment.

    Back to Top

    Table of Content

    Hide Index