apsuhos

Thank you for your quick response and for addressing the issue. I’ve updated to version 1.1.0, and everything is now working perfectly. I really appreciate your time and effort.

Sure thing @jarnovos. I just sent an email at the provided email address.

• This reply was modified 2 years, 6 months ago by apsuhos.

Hey @jarnovos

thank you for your time figuring out what the problem is. So to sum up there is nothing that can be done? I will let the plugin in sync with cookiedatabase.org as this seems to solve the translation issue about the “purpose” of the plugin. As for the service descriptions the issue still remains.

Hi @jarnovos

Concerning the categories found in the Wizard dropdown (for the ‘secondary’ language), you should be able to select the intended category/purpose, even if displayed in English instead of Greek as shown in your screenshot. The translation should still appear on the front-end.

This is what I expected too but it is not happening. The front end outputs it as two different categories/purposes.

https://snipboard.io/Bn7sM5.jpg
https://snipboard.io/x9e1vn.jpg

When syncing those (non-manually) added cookies with CookieDatabase, the translations will be pulled from CookieDatabase.org instead.

Yeah, I figured that as pointed in my previous message (4).

What about the service descriptions? Do you have any idea why these strings in Polylang are being ignored but the ones on the banner are not?

Unfortunately I am giving up. I tried numerous ways to make it work but I just couldn’t. What I figured out so far.

1) Translating strings on Polylang have no effect except on the banner. All other strings are just ignored.

2) My site’s default language is Greek (as set by Polylang). I set the site’s language on the backend as Greek (Settings>General>Site Language). I activate the Complianz plugin and get a banner in Greek. Great! In “Polylang > String translations” under the group complianz I get 23 strings. All of them but 5 translate the banner. These 5 are wrongly prefilled.

https://snipboard.io/WSYEpm.jpg

3) If I set the site’s language on the backend as English (Settings>General>Site Language) and activate the complianz plugin then under string translations in the complianz group I get 82 strings. These 59 extra strings (82 – 23) are the service descriptions. Again, after I translate each one of them the only strings that have an effect on the front end are the ones that have to do with the banner. All the others are ignored.

4) If I check the “sync cookie info with cookiedatabase.org” it translates the function of the cookie and the purpose correctly. But if I try to add a cookie manually, the options on the dropdown list of the “purpose” option are in English.

5) The service descriptions strings are not present in Polylang when I set the site language in any language other than English and activate the complianz plugin. (see 2 above)

6) The documentation regarding the translations is not very well structured.

7) I decided to have the cookies scanned and sync automatically as this seems to at least translate the purpose of the cookie. About the service description I may leave it in English or hide it with CSS.

• This reply was modified 2 years, 6 months ago by apsuhos.
• This reply was modified 2 years, 6 months ago by apsuhos.

Hey @aahulsebos

No, that is the issue I currenlty have. When I add a new cookie the non-default language does not get filled, which is what I would have expected.

https://snipboard.io/1sWCx2.jpg
https://snipboard.io/nfpI7s.jpg

Here are two images. The first one is from the cookies description section and the other one from the service descriptions. As you can see in the dropdown menu, even though the label is in greek and all strings have been translated through the Polylang plugin it keeps showing the english terms.

I will do some more digging to see if there is something wrong on my end and I will come back.

PS snipboard seems great. Thanks for that!

Hello. This also happens with the WooCommerce Stripe Payment Gateway by Woocommerce plugin. Unchecking the Disable WordPress Admin restores it.