One Button for Language and Currency Selection

Store Design

Topic summary

A Shopify store owner is trying to create a single button that switches both language and currency simultaneously for two markets: Lithuania (LT EUR) and Netherlands (NL EUR).

Current Problem:

  • Two separate buttons exist for language and currency selection
  • Hiding one button causes products for the NL market to display incorrectly
  • When both buttons are visible and set correctly, products display properly per market

Technical Issues Encountered:

  • Custom code using Shopify’s localization form works inconsistently (LT→NL switches correctly, but NL→LT fails)
  • Browser console shows multiple cookie-related warnings about missing “SameSite” attributes
  • Suspected code conflicts from a previously installed GLC Geolocation app
  • Code behavior is unstable, sometimes working then failing without changes

Attempted Solutions:

  • Community member provided sample code using Shopify’s localization form with a single submit button
  • User has spent 3 days working with GPT on various code iterations without success

Status: The issue remains unresolved. The user is seeking help identifying where code conflicts might exist and questioning why separate currency buttons are needed for EU countries sharing the same currency.

Summarized with AI on November 1. AI used: claude-sonnet-4-5-20250929.
5

Thanks for your help.
I am doing 3 days with GPT.
Looks like some code is blocking. Because a few times worked my code and then no more. Without editing.
Before was installed GLC Geolocation probably left some code. But not sure.

In console, I get this error message
Content-Security-Policy: Ignoring ‘block-all-mixed-content’ because mixed content display upgrading makes block-all-mixed-content obsolete. nl
Removing unpermitted intrinsics lockdown-install.js:1:52832
Cookie warnings 7
Cookie “localization” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite nl
Cookie “cart_currency” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite nl
Cookie “wpm-test-cookie” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 nl
Cookie “localization” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite search
Cookie “cart_currency” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite search
Cookie “localization” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite search
Cookie “cart_currency” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite search
Cookie “wpm-test-cookie” has been rejected for invalid domain. 2 nl