The website encountered an unexpected error. Please try again later.</br></br><em class=“placeholder”>Symfony\Component\Routing\Exception\RouteNotFoundException</em>: Route "cookieconsent.cookieconsent_admin_form" does not exist. in <em class=“placeholder”>Drupal\Core\Routing\RouteProvider->getRouteByName()</em> (line <em class=“placeholder”>201</em> of <em class=“placeholder”>core/lib/Drupal/Core/Routing/RouteProvider.php</em>).
Thanks for the link to the issue. When will 2.2.0 be deployed then?
Given that that plugin seems to have been implying that the “Cookie concent” module was activated, should it be on by default?
Is there a recommendation to enable or disable this plugin? Do CERN regulation require that module to be enabled?
The issue was initially caused because there was a reference to Cookie consent in the CERN Toolbar settings. However this creates an issue when the Cookie consent module is not enabled. The “Drupal way” to fix this issue is to create a dependency between the 2 modules, so that when the CERN Toolbar is enabled it will forcely enable the Cookie Consent too.
The CERN Toolbar module used to have this dependency but at some point it was removed because it was creating some implications. The fix I applied actually checks if the module is enabled before referencing it, so that the two modules won’t need to have a dependency between them.
The fix will be deployed in the next module/theme update so approximately during the next 2 weeks.
Yes, I understood that the CERN toolbar has a hidden dependency on the Cookie Consent.
I was wondering if this hidden dependency was due to the assumption that this module should be enabled at CERN: What’s the recommendation/requirement? Is there any policy requiring it?
Yes it is recommended the users to have the cookie policy enabled and thank you for mentioning it. We will publish an article in the Webtools website during the upcoming days regarding the Cookie Policy - why you should have it enabled and what it should include.
