Support multilingual sites with multiple domains

Created on 6 October 2022, over 1 year ago
Updated 2 April 2024, 3 months ago

First of all thanks for making a good CookiePro module!

Problem/Motivation

CookiePro's IDs are per domain, so for multi-lingual sites which use domain based selection there will be a different Cookiepro Site ID for each domain. Currently this configuration isn't supported by this module.

Proposed resolution

Make the "Script ID" setting translatable so a different ID can be used for each language.

✨ Feature request
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡³πŸ‡ΏNew Zealand fraserthompson Dunedin, New Zealand

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¨πŸ‡¦Canada ClassicCut

    I know this issue is marked as fixed, so perhaps I'm not configuring something correctly. However I can't get the language overrides to work. I have a bilingual English/French site, with language negotiation set to use different URLs. I've configured CookiePro Plus to override the default configuration for the French site (with a different script ID), however only the default (English) config is ever used to find the script ID and insert it into the page HTML. Checking the code in CookiePro.php, the methods to get script ID and URL only ever load the default config and never check for config overrides. Am I missing something? Thanks.

  • πŸ‡§πŸ‡ͺBelgium andreasderijcke Antwerpen / Gent

    @ClassicCut Can you please create a new support issue for your case, and explain it a bit more into detail + some specs? Perhaps also some screenshots of your language and language negotiation setup too.
    The config override is set in event subscriber https://git.drupalcode.org/project/cookiepro_plus/-/blob/1.0.x/src/Event...

  • πŸ‡¨πŸ‡¦Canada ClassicCut

    @andreasderijcke Thank you for the information. Based on what you said, I think part of the problem is that the event subscriber never gets called. I'll do a bit more research and gather up some data to log a separate ticket, if in fact the problem lies with the CookiePro Plus module (I suspect I have other modules that might be messing with event subscribers).

  • πŸ‡§πŸ‡ͺBelgium andreasderijcke Antwerpen / Gent

    Alright, I'll keep an eye out for possible ticket. If there is something we can do to prevent collision(s) with other modules...

Production build 0.69.0 2024