The discussion focuses on the Discourse Cookie Consent Banner theme component by tshenry, which integrates the Osano open-source banner. Users praised its ease of use for adding a customizable consent UI Anatolia, ScammerRevolts. However, significant debate centers on GDPR compliance. Krischan argues that modern EU regulations require advanced consent controls (active opt-in for specific cookies), suggesting this should be a core feature. codinghorror counters by questioning why major sites like Amazon lack it, though Krischan cites recent court rulings and the Amazon fine as proof of legal risk. The author repeatedly warns that the component is unlikely to be sufficient for GDPR compliance, especially regarding third-party cookies, and advises consulting legal counsel. Users Iceman and Jagster debate whether the plugin should be tagged #official. While AquaL1te desires the official label for stability and maintenance assurance, Stephen warns that an official tag might mislead admins into thinking it alone satisfies legal requirements. The consensus is that #official implies code stability, not legal compliance, with Heliosurge noting that other official components also require careful configuration. Technical issues were raised regarding missing settings (resolved as a UI navigation issue by merefield), inability to decline cookies without clicking eextra, and CSS color overrides Olle11. More recently, Richie reported a deprecation warning in 2025. tshenry confirmed the update fixed the warning but reiterated uncertainty about long-term support given the component’s limited legal scope. The original warning banner, present since 2022, remains a critical caveat RGJ, emphasizing that admins must independently verify legal compliance.
At this time, it is highly unlikely that this theme component will be enough to comply with GDPR regulations. This is particularly the case if you are using services that introduce 3rd-party cookies.
It is highly recommended that you talk to your lawyer and figure out your individual needs. Please also see Cookie Consent, GDPR, and Discourse
This theme component will allow you to add a customizable Cookie Consent banner to your forum. It simply provides an easy way for Discourse admins to make use of the open source Cookie Consent banner by Osano.
I am not a lawyer. Please make sure this meets your individual legal needs at the time of installing. If there are ways to improve the usefulness of this component, please share!
Apparently, it’s mandatory in the EU now that websites have an advanced cookie consent banner, i.e. with the options for the user to choose exactly which cookies are set. Shouldn’t this be part of Discourse core and support all the Discourse supported tools like Google Analytics etc. in order to make a standard installation in the EU legal from scratch?
Edit: I don’t know whether this is true for other European countries, but there’s a flourishing cease and desist letter writing industry in Germany - that’s what makes the matter so unpleasant.
There is now a ruling by the highest German court that users must give active consent to cookies, and I see more and more pages within the EU that have this functionality. Any chance that this component supports this as well any time soon? Or do you know of any third party services that work well with Discourse? Thanks!
Meanwhile amazon.co.uk and probably all major european websites offer this option. Is there any new information on the subject? Can we contribute something to get things moving?
Thank you!
The question is for more specific management. it seems that not only you need to allow to “select” which ones to use but also you need to ask first and then deploy. For example this topic that is also linked in the first post:
The main worry comes from the fact that third-party “cookie managers” can not only “fail” to do the trick for Discourse but also hinger it in some fashion. Hence my question. The Amazon fine stands as proof that this ain’t something to brush off lightly.
Will this theme component be included in official one day? I tend to stay away from unofficial stuff as much as possible due to maintenance and stability reasons. But since this plugin is from a Discourse developer (right?) and since the plugin is already a few years old, I suppose it’s mature and maintained well enough to get the official label?