Consent Banner plugin not working

Plugins
,
#1

Hi, I’ve installed the Consent Banner Plugin, configured it but nothing shows up and I don’t know why. I’ve tested it with two different wikis, three different browsers, logged-in, logged-out – nothing happens. (I also re-installed.) Has anybody had a similar experience and could help me with this :question:

#2

What is the “Consent Banner Plugin”. Do you have a link?

#3

I’m guessing this one:

https://tiddlywiki.com/#Consent%20Banner%20Plugin

Seems to be an official plugin.

#4

Yes @Xyvir, that’s the one!

Unfortunately, there is also no developer contact (email, website or sth.) in the plugin. I’ve just discovered it on Github opened an issue but my issue doesn’t show up.

I’m on TW 5.3.8, work on MacOS and iOS.

#5

I did try it with empty.html and it seems to work as expected.

1 Like
#6

Good idea @pmario, I also tried with an empty.html but something strange happened:

  1. When I opened the file in Browser 1, the consent banner was displayed. Clicking the «Accept» button made the banner disappear forever, even when I opened it in a private browser window.
  2. Made a second empty.html and opened it in browser 1, clicked NO button and additionally opened the file in browser 2 and 3. I exptected the banner to be displayed also in these two browsers but nothing showed up.

I don’t really get how this plugin works. Does it register cookie acceptance for the PC not just for the browser? Is this expected behaviour? When the banner never shows up again the users consent would be forever?!

#7

I can not replicate this one. I did try it with FireFox Windows 11

  • If I open empty.html from a file the plugin info is stored in the browser local storage
  • If I open it in a private browser, dialogue is opened again

With F12 Browser Def-tools, Storage-tab you can inspect the different storage areas. The values are different in normal window and private window.

If you open a second empty.html from the file:// URL browsers treat the file:// URL as the same domain.

That’s a major problem with file URLs and browser security settings. Because all wiki’s opened from a local file share the same browser storage.

For local files and the consent-banner, IMO that’s not really a problem, because for local wikis the consent is not needed.

With the config tab of the plugin the setting can be changed afterwards.

Hope that helps.

#8

Hi @pmario, I’ve tried a third time with a new local TW and this time it works as expected! But my online wiki still doesn’t show the banner. It sets the cookie though if I click the buttons in the plugin config. So basically it works. I also re-installed two times and deactivated my other plugins one after another … just to check if sth. weird was going on there. (And tested on three different devices.) Now I really don’t know what else I could check?

#9

Whilst this in a known limitation of browsers, the name and keys to storage are not. If we use the field path or a wiki name it would be easy to store wiki based entries in local storage, thus able to differentiate. Perhaps the decision to have a consent banner for file wikis can be a separate mechanism but this feature could be extended for other features like a wiki could detect when it was last opened and/or a banner or message by looking at is corresponding file storage.

  • A few simple mechanisms could support more feature development in this space
1 Like