Translating GDPR Cookie Consent plugin with Polylang

GDPR Cookie Consent plugin is compatible with some of the most common multilingual plugins like Polylang, WPML, qTranslateX etc. In this article, we will share deep insight into how the GDPR Cookie Consent plugin can be translated into your desired language via Polylang.

Refer Translating GDPR Cookie consent plugin with WPML to know how the cookie plugin is translated using WPML.

Once the Polylang plugin is installed and activated, you need to first configure it for the desired languages. Once the languages have been set up, navigate to Languages > String Translations as shown below for customizations w.r.t the plugin:

GDPR-Cookie-Translation-with-Polylang

From the String Translation page that opens up, filter the group by selecting webtoffee_gdpr_cookie_consent from the drop down as shown below:

GDPR-Cookie-Translation-with-Polylang-Select-webtoffee_gdpr

Note: In this case, the language is switched to French prior to translating the strings of GDPR cookie consent plugin.

For instance, let us see how the string on the Accept button is translated into French.

GDPR-Cookie-Translation-with-Polylang-Change-string-to-French

The string on Accept button is changed to Accept in French indicating the translated text in French. On loading the website, the cookie accept button will be as shown below:

GDPR-Cookie-Translation-with-Polylang-Cookie-button-in-French

 

7 thoughts on “Translating GDPR Cookie Consent plugin with Polylang

  1. Ralph says:

    The information is not complete. On top of the “string translations” you will also need to translate all items from the “cookie list” (if you have that populated), otherwise they will not show up in the “privacy overview” pop-up where the user can selectively turn cookies on or off.

  2. Jerome says:

    Hi,
    I don’t see any webtoffee_gdpr_cookie_consent content in string translation.? I just have Widget and wordpress.
    What can I do to get them?
    Best regards

Leave a Reply

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