Overrides of cookie descryption and cookie name

Version EPRIVACY Package -> 3.10.5
Joomla 3.8.8

First of all: thank you for the enormous amount of work that you have put in the development and updating of the eprivacy extension.

Now for my question: you suggest that for a translation of the cookie name and the cookie description (for a multilingual website), one could use the constants PLG_SYS_EPRIVACY_COOKIENAME_ and PLG_SYS_EPRIVACY_COOKIEDESC_ but although I have translate several constants, these two I cannot find. Searching by their English value gives no result either. Just putting these constants directly in the override fields to see if that would do the trick doesn’t work, because Joomla cannot find the constants to override. I am overlooking something?

Thanks for any suggestion,
Janbol

P.S. Hope you get some sleep from time to time…

This is super easy

in your site, find the /language folder. Inside, you may see a folder named "overrides" - if not, create it. Inside of /language/overrides/, for each language you have installed on your site, create an override file:

en-GB.override.ini
fr-FR.override.ini
nl-NL.override.ini

Inside of this overrides file is where your translations live.

Let's say you created a cookie definition for Google Analytics and made the constants PLG_SYS_EPRIVACY_COOKIENAME_GA and PLG_SYS_EPRIVACY_COOKIEDESC_GA

Inside of each of these overrides files, you would translate the constant:

en-GB.override.ini:
PLG_SYS_EPRIVACY_COOKIENAME_GA="Google Analytics"
PLG_SYS_EPRIVACY_COOKIEDESC_GA="We use Google Analytics to better understand user traffic and traffic patterns on our site so we can sell more stuff."

fr-FR.override.ini:
PLG_SYS_EPRIVACY_COOKIENAME_GA="Google Analytics"
PLG_SYS_EPRIVACY_COOKIEDESC_GA="Nous utilisons Google Analytics pour mieux comprendre le trafic des utilisateurs et les modèles de trafic sur notre site afin que nous puissions vendre plus de choses."

And so on.

Easy, right?

P.S.: I just fixed a major bug - I'm definitely sleeping tonight!

Michael,

The words « …and made the constants… » in your reply made all the difference.

I was assuming that these constants existed already, like others, so of course the overrides didn’t work, no matter how you created them. So putting the constants in the respective fields, does the trick. Satori.

Thanks,
Janbol

Yeah, I was afraid that would be confusing.

If the constants begin with PLG_SYS_EPRIVACY_COOKIENAME_ or PLG_SYS_EPRIVACY_COOKIEDESC_ - then the plugin knows it's supposed to translate them.