There is functionality duplication between this module and https://www.drupal.org/project/gdpr_onetrust

Is there any reason why both could not be merged and join efforts?

Comments

alexmoreno created an issue.

andreasderijcke’s picture

Based on both Drupal code and involved scripts, these look like 2 different tools from OneTrust.

leon kessler’s picture

My understanding is that the gdpr_onetrust module uses the "legacy" mode for embedding OneTrust. And cookiepro is the new way of using OneTrust.

Possibly things had different names before. Cookiepro isn't mentioned inside my OneTrust dashboard, but I can see most of the docs are for "CookiePro". E.g. https://community.cookiepro.com/s/article/UUID-5394213a-70b9-c4e6-d68c-f...

Slightly confusing. Would be worth clarifying on the module homepage (as it took me a while to realise which module to use).

andreasderijcke’s picture

@Leon Kessler: It's a separate tool, and the CookiePro dashboard is https://app.cookiepro.com.

leon kessler’s picture

Hmmm, but on my Onetrust dashboard it provides the same embed scripts as CookiePro does.

I'll ask OneTrust to clarify.

leon kessler’s picture

Okay I have spoken with OneTrust.

CookiePro is a standalone product, but it is also included in the OneTrust platform. So they are almost the same, but with slight differences in terms of the licenses, and the dashboard, etc.

Not quite sure where that leaves this module. I think it's possible it could be easily adapted to support both. Main issue is the name.

andreasderijcke’s picture

Checkout https://www.drupal.org/project/cookiepro_plus, it supports both out-of-the-box.

I tried to get my version into this module over the past year, but OneTrust could/would not make time to make this happen.. So separate module it is. Also, supporting module(s) for content blocking, which we'll release separately will be up soon (target end of sept 2022): https://www.drupal.org/project/consent_support.