Johnny asked 8 years ago
Johnny answered 8 years ago
Fixed :). Found the below to work i.e link tip from a shopify related question. I used the same recommendation from Dave and it works with both Explorer and Firefox, both of which failed with the “old” link method. The only minor snag is that when linking to the first language/button (en) on the cover page, Explorer opens a new tab. When pushing the second button (swedish) it opens the (se) site in the original tab. Not knowing why this happens since the code really is the same in both buttons just calling different languages. Could possibly be Squarespace related ? Is there a way to force script to stay on the same tab?
Pasting Daves solution below which was found elsewhere on this excellent forum.
……
Dimitrije asked 1 week ago
Hi there, I am having trouble understanding this step of my shopify store setup ”
Change language AND change page
Create a URL link in your menu and enter the following instead of the URL:
javascript:changeLanguageAndMove(0, '/');
This will switch to language 0 (whichever you have set as language 0) and move to your home page.
or
javascript:changeLanguageAndMove(1, '/specific-page/');
This will switch to language 1 (whichever you’ve set as language 1) and move to /specific-page/ on your website.”
1 Answers
0 Vote Up Vote Down
Hi – the instructions need updating.
A better way to achieve this since the launch of the latest version is to simply append the ?lang=fr parameter to the URL.
This will set the language for a particular page.
i.e. you don’t need to call javascript:changeLanguageAndMove() any more – just do a normal link to http://www.yourdomain.com/your-page?lang=fr (2 digit ISO code for countries) and it will have the same effect.
Please login or Register to submit your answer
I am beginning to think this might be firefox related. Seems other browsers are more stable. With the latest release of multilingualizer is there still a footer script to be used for the cover page in squarespace?
Hey Johnny, apologies for the delay. If the issue occurs only with Firefox, then it’s most surely related to the browser itself. Dave is currently working on an array of fixes regarding stability – we expect them to be out fairly soon. Thanks for your patience.