Extension talk:CookieWarning

Howdy. When examining the extension, I found out that it displays the cookie warning after (!) creating the session cookie. The "okay" button is fake because there is no way to say "no". It just creates another cookie to suppress the banner next time. Yet GDPR requires the user's active agreement before storing anything on their computer. Is there another extension that we can use to get the user's agreement before creating the session cookie? Or a hook where I can place my own code? Best place would be before showing the page content.

Yes, the consequence of denying cookies will be to not allow the user to use our wiki. And yes, GDPR is crazy, for sure.

Is it possible for a user of the extension to add explicit user consent for cookies of services like Google Analytics or AdSense, as required by the GDPR?

What exactly do you mean? There's a task for making some adjustments to the extension (https://phabricator.wikimedia.org/T249248). Is that, what you mean?

Yes. I'm the one who created the task you mentioned.

Then there's nothing more to say here, isn't it? :D

No, there isn't. Actually, I had made this post here before starting the task on Phabricator. Since there is a task there, any developments can be mentioned in the relative task.

I think the Extension:Privacy is a bit closer to what you are referring to. I am not sure that it will load all scripts in non-GDPR countries, but it seems to have the logic to turn some cookies on or off depending on consent from the user. And integration with Matomo.

It also adds some additional GDPR functionality such as tools for anonymization and data retreival.

The problem with the extension is that you need to install a bunch of additional BlueSpice extensions, which may not be desirable. It is not in my case.

At some point I want like to look into whether it is easy to modify the Extension:Privacy so that it can be used on its own.

That thing does not work outside of the BlueSpice variant of MW.

An ideal implementation would be one similar to the example's I mention in Phabricator: https://phabricator.wikimedia.org/T249248

We use varnish for our non-logged in users to display already rendered pages. However, the cookie warning state is cached and has different results based on different browser cookie states. This will also affect mediawiki file based cache.

Any thoughts on moving this to a JS based display logic?

Could someone please indicate what the expected schema is for the geolocation API?

The example in the documentation leads to freegeoip shutdown, which hasn't been working for quite a long time.

{

"ip":"172.217.23.132",

"country_code":"US",

"country_name":"United States",

"region_code":"CA",

"region_name":"California",

"city":"Mountain View",

"zip_code":"94043",

"time_zone":"America/Los_Angeles",

"latitude":37.4192,

"longitude":-122.0574,

"metro_code":807

}

Is there an alternative API to freegeoip.net?

Today I noticed (after receiving email from "Google Search Console Team") that the message that CookieWarning produces does not seem to go through the MobileFrontend extension (one can easily see this on a desktop browser by appending ?useformat=mobile to the URL). Rather, the cookie message that appears on the mobile phone seems to be overlapping (probably "below") the MobileFrontend-formatted message. It also does not appear to have the same width as the screen.

What can I do to fix this? Thanks!

Hi,

on my side the Cookie Warning does not appear anymore with the new MediaWiki 1.35 and the vector skin. If I change the skin, for example to Monobook, it is shown. Also on the Minerva Mobile Skin.

Is this a bug on my system, or is there another problem with the vector skin.

Another thing was, that with vector skin, my gadgets in the sidebar were not shown. Perhaps this is kind of the same problem. Anybody has the same Problems?

cheers

Andreas

Short Update. Tried the Master Branch of this extension, with that it works again. But I want to use the REL1_35 branch. So any chance to update that branch?

After Testing again, it does not work with the master branch, too. So I just opened a ticket for that. https://phabricator.wikimedia.org/T267436

I also have a problem with the Vector Skin in 1.35 (until v1.34.4 everything worked great)

An entry in the Sidebar does not work (SkinBuildSidebar function).

In my case the problem is that for inexplicable reasons  the content of the section was generated, but "hidden" by a CSS class (.emptyPortlet with display: hidden).

Try to check and workaround if it is something similar.

yes same here, too. Fixed that problem by adding

.emptyPortlet {
        display: block;
}

to Mediawiki:Vector.css but that did not fix the CookieWarning Problem.

Yes, I too solved in this way in a few minute but is very strange. It's like that CSS class (.emptyPortlet with parameter "display:none") is used to hide an item detected as "blank".

My wiki has always had a banner in the sidebar that with the v1.35 is not showed, but the weird thing is that you can still see it in the HTML code of the generated page, so... that item was not blank!

Do not edit the .json files directly but the respective system message pages on the wiki itself.

Hello, using the CookieWarning. Are there variables to set the text for each of the two buttons, and also for the Cookie Alert itself? --Jeffmcneill (talk) 13:52, 14 April 2017 (UTC)

Never mind, found the file i18n/en.json --Jeffmcneill (talk) 13:57, 14 April 2017 (UTC)

Do not edit the ".json" files since your changes will be overwritten on every update of the extension. Rather edit the respective system message on wiki. I have changed the documentation to make this noticeable.

Could it be possible to add support for wiki links and etc. code?

Also it would be nice to have <br> code working in it.

Currently this is indeed not possible. I am not sure if I would like to have this option since it invites to add unnecessary information. @Florianschmidtwelzow:

I don't think, that html in this message makes any sense. What is your actual use case? You could add more information about how you use cookies on the page you link with the <code>$wgCookieWarningMoreUrl</code> configuration option. What exactly do you mean with "wiki links" and "code"? A wiki link could be added into the <code>$wgCookieWarningMoreUrl</code> configuration URL by adding the full URL of it. What is the use case of adding code to the message? :/

I need to use Link to other site -wiki link two times in my cookie warning text.

I didn't get that <code>$wgCookieWarningMoreUrl</code> work if it is meant to put in to MediaWiki:Cookiewarning-info page.
I did make MediaWiki:Cookiewarning-more-url page where I put one of my links to other site.

I also need <br> code or something similar to move some text apart. Now it's all going to one long sentence.

So i need to use link to my advert media site in cookie warning text.

Best would be like in wiki link style as Link to other site.

Can you please ad this support?

So can we have that link support or not?

It would be nice to have somekind of line break too because now all my text in GDPR-info is not in so readable form.

Today I noticed (after receiving email from "Google Search Console Team") that the message that CookieWarning produces does not seem to go through the MobileFrontend extension (one can easily see this on a desktop browser by appending ?useformat=mobile to the URL). Rather, the cookie message that appears on the mobile phone seems to be overlapping (probably "below") the MobileFrontend-formatted message. It also does not appear to have the same width as the screen.

What can I do to fix this? Thanks!

Use the CSS provided. This is however not recommended.

What must i do? Thanks for help

Add the following in one of the stylesheets:

.mw-cookiewarning-container {
    top: auto;
    bottom: 0;
}

Thanks @Ciencia Al Poder for the answer :) @Evetro Please note, that the bottom is probably not prominent enough for the warning. It would also be possible for a user to click the links in the personal tools bar to e.g. create an account or login, which will potentially add more cookies to the users browser without having him read the cookie notice.

Link changed to point to extension's docu page in master and 1.31

Seems to have a bug with the extension pointing to an unrelated website under the Special:Version page.

It indeed points to DroidWiki, which is the wiki of the extension's developer. I also think that it will be better to point the link to the extension's docu. In the end a matter of taste. @Florianschmidtwelzow: FYI.

Oops, my fault! See task T201076