“Cookie Policy” — two questions

Hi Frank,

I am happy that you like the plugin.
To answer your questions:

1. Translation is atm only possible if you use the json configuration. You have to add this line
"policy": "Cookie Policy", right after the line which begins with “dismiss”. You can change then the text “Cookie Policy” to whatever you like.
2. At the moment this is only possible with a hack. You could use this link. Please test it carefully.
<a style="cursor:pointer" onclick='(function nscCookieBannerDisplay(){var banner = document.querySelector("div[aria-label=\"cookieconsent\"]"); banner.classList.remove("cc-invisible"); banner.style.display="";})()'>Cookie Policy</a>

In future releases I will implement those features into the plugin, to make the configuration more easy. Thanks a lot for your hints.

Regards
Nikel

• This reply was modified 5 years ago by Support.

@frank-j
Hi, just released a new version:
it allows you to change the text easily and deactivate the “cookie policy” tab and use a custom link instead. This link can be placed everywhere with a shortcode. I think this is exactly what you needed. Thanks again for your feedback,

Regards

Hi Nikel,

that’s good news, thank you! I will check that soon — and will give you a feedback then.

Cheers, Frank

Hi Nikel,

I didn’t forget this — there were just too many other things to do. Heard that before? ??

I implemented the shortcode [cc_revoke_settings_link_nsc_bar] and tested it. It works (https://fliegende-ente.de/cookies/).

What I would expect though is that clicking on the shortcode generated string would make the banner appear again (which has been the user interface to accept or deny the use of cookies for first time visitors).

I would not go as far as saying that a user is “used” to that bar and would expect it (instead of a plain string) — but in a way this assumption is not completely wrong: Most Cookie Policy user interfaces come as a bar, box or similar.

Just clicking on a text string — and that was it — to change my cookie decision is something that I would not expect — even though the changing text string tells me that something must have happened :-).

Cookie policies are a pain in the neck (and in most cases user won’t read provided information or understand what it is all about). Your solution makes things easier. Thank you a lot for your work, Nikel!

Cheers, Frank

Testing the plugin’s visual component with different browsers (all latest versions) on a desktop Windows computer:

Firefox and chrome: looks good

IE: The “Deny Button Text” overlaps the “Accept Button”.

Just two more cents: I never understood why the “Deny Button Text” in your plugin has no button. Two buttons would be more intuitive.

Selectable colors would be nice for that: So that I [a good one] can make the “no button” green whereas the bad guys could make the “yes button” look more friendly. ??

Cheers, Frank

Hi @frank-j,

thanks a lot for your support. With IE you mean probably IE11, right?
Regarding the Banner I am using this OS library: https://github.com/osano/cookieconsent/tree/master

I am waiting for their version 4 release, hoping this will fix this issue.
For easy upgrading reasons I did not got involved in changes regarding the banner code itself.
So please be a bit patient regarding the IE bug.
For the buttons I am depending on their library as well.

I expect some improvements regarding v4 otherwise I guess i am going to fork their project.

Regarding the cookie opt out link: you are right. But I won’t do reopening of the banner. What do you think of having a second shortcode only with the status.

Then you are able to do the following, for example:
Your optin status: agreed change <- this will be a link then.

Until this is released, probably you can change your text to this?
Cookie Opt-In Status: cookies abgelehnt, zum ?ndern hier klicken.

Not perfect, but maybe less confusing? See screen as well: https://nikelschubert.de/images/screenshot_15.png

Regards
Nikel