I was thinking it might be an idea to try and match the API exposed by Cookie Control to provide a simpler upgrade path from D6 -> D7. It could also prove useful in cases where a 3rd party module is updated to work with the cookie module (it's nicer to present the maintainer with one API to implement across 6.x and 7.x).

Thanks for your time

Comments

Miszel’s picture

Miszel commented

I started looking into it and it seems to me that I would have to:

- provide a way to configure the pop-up by country (geo targeting)
- add extra API functions
- add js callbacks (onaccept etc)

I will investigate further.

Miszel’s picture

Miszel commented

Another issue: Cookie control does not provide support for multilingual websites. That would have to be implemented in Cookie control.

Miszel’s picture

Miszel commented
Status: Active » Postponed (maintainer needs more info)
andyf’s picture

andyf commented

There's an issue for i18n (#1499478: how to get text in different languages ?) but it doesn't look like it does very much just yet! Depending on where the text comes from i18n might not have a big impact on the API you expose to other modules (which to my mind is the thing you want to be keeping similar to Cookie Control's).

By the way, I don't know Cookie Control at all well, so I'm not saying its API is good or anything, just speaking out for consistency!

Thanks

Miszel’s picture

Miszel commented

Api can be matched if geo targeting is added. The question is if we really need geo targeting ??? What do you reckon?

Miszel’s picture

Miszel commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

I am closing this issue as:
- there is now a 7.x release of this module
- matching the api with cookie control would require adding extra features that I am not planning to develop for EU cookie compliance for the time being.