Updated patch with compatibility for version 2.1.1
Hi,
this behavior may happen if cookie storage fails, this may happen if the OneTrust script is configured for a different that current domain or another module is conflicting with it.
For starter, in order to debug this, would it be possible to share a list of errors logged in console?
As Drupal 8 is long dead this issue can be closed.
Just to be safe I tested this in Drupal 9 and Drupal 10 and could not reproduce the issue.
Hi @gisle
thank you for your message.
I opened those request representing an organization because we have quite a lengthy list of projects we want to co-mantain.
We already contacted maintainers and/or owners of several projects that we use and that didn't have any activity for a long time. Problem is that usually there was no response or the response was that maintainers/owners moved to different stacks and don't have time for Drupal.
Should we still open a issue in project's issue queue if the project has not activity and we already contacted maintainers/owners ?