Configure consent management to be non-intrusive

Consent management is now configured completely non-intrusive. That means:

• There is no widget visible by default, i.e. the user doesn't notice that consent management is even present on the page.
• Instead, there is a link in the footer menu called "My privacy settings". If clicked, the consent management popup will be opened allowing the user to review and change their consent.
• That said, privacy is still being taken care of, i.e. only required cookies will be allowed and external content (e.g. YouTube videos) will be replaced with their thumbnails until the user gives consent, that the external content should be loaded and displayed.

This is setting all Drupal CMS sites into an ideal privacy compliance state while most users on most sites will never ever get distracted by any of this. I'm sure this will create even higher acceptance out there in the world.

Note: there is one final test failure with a config schema issue which is being addressed at 🐛 Redundant library.notice_as_modal still in default config Active .

I've just tested the issue fork and this works and looks fine to me. The only thing I noticed was a composer error during drush site:install because of missing module menu_link_attributes (installed it manually then to test).

Another finding is that when you load a page with a video for the first time (no consent given so far), the option that comes with the thumbnail is "Yes". If you open the klaro dialog with "My privacy settings" and switch "Embedded external content" on, the content shows up as expected. If you do this again and switch it off, the thumbnail an the question appear again, plus a second option "Always" appears next to "Yes". Does anyone know why "Always" is not an option in the first time?

I've just tested the issue fork and this works and looks fine to me. The only thing I noticed was a composer error during drush site:install because of missing module menu_link_attributes (installed it manually then to test).

That's strange. It is contained in the require section of the composer.json and listed in the recipe.yml for installation. Have you run a composer update after checking out the MR?

Does anyone know why "Always" is not an option in the first time?

I remember there has been a discussion about that in the Klaro issue queue somewhere. But I can't find it any more. So, as this is not an issue about the way this is being integrated, but an issue in Klaro itself, I suggest to open an issue there so that it can be addressed upstream.

Schema issues have been fixed upstream, so the tests are now green again.

No technical objections; assigning to Pam for manual testing and final approval.

This is much better, that widget was driving me nuts!

Merged into 0.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.