Background of the issue:
I'm using WPML in 'separate domain per language' mode. The default domain canasity.com works perfectly. However, on the secondary domain canasity.ro, the cookie banner (whether using CookieYes via GTM or Complianz plugin) does not appear on first load in incognito — it only shows after a page refresh or navigation. I tested both CookieYes (via GTM with consent mode v2) and Complianz, and both have this delay only on canasity.ro. CookieYes also shows this GTM debug error: Error: Consent doesn’t update. Rocket.net support responded as 'I checked it and couldn't find why it's happening; it'd be great to contact WPML support to know if they need some cookie to be whitelisted when using this subdomain feature. I checked the non-cached version and it's still delaying to display.' I need help determining if WPML’s domain routing or output timing could delay JavaScript on the secondary domains.
Symptoms:
The cookie banner does not appear on first load in incognito mode on the secondary domain canasity.ro; it only shows after a page refresh or navigation. CookieYes shows a GTM debug error: Error: Consent doesn’t update.
Questions:
Could WPML’s domain routing or output timing delay JavaScript on secondary domains?
Does WPML require any specific cookies to be whitelisted when using the subdomain feature?
