fbpx
Skip to content
Questions & AnswersCategory: QuestionsTranslation not working on nested pages.
JUSTIN asked 8 years ago
 Hello,  On most pages in the navigation panel of my Squarespace website (NL-EN) it works flawlessly. I notice the translations don't work when linked pages nested under the STIJLEN..STYLES panel just show both languages and the dots. Here's a link (http://www.indigodans.be/stijlen/#/yoga/). Click the next button underneath the page and you'll notice this again.  Am I doing something wrong? Coz these pages are working fine e.g (http://www.indigodans.be/home/ ) as well as (http://www.indigodans.be/ontmoet-de-docenten/). Can you please help me with this issue? Thanks in advance.  Cheers,  Justin..
Dave Hilditch replied 8 years ago

Hi – thanks for bringing this to my attention. It doesn’t look like you’re doing anything wrong – you have the formatting correct etc. It looks like your theme is using JavaScript to alter the content and yet somehow this change is not firing the event that the Multilingualizer listens to. I’m going to send you an email so you can invite me as contributor and I can take a look directly on your site to figure out a solution.

JUSTIN replied 8 years ago

Ok thanks that would be fantastic.

1 Answers
Best Answer
Dave Hilditch Staff answered 8 years ago

 Ok – can you check it now? I’ve added the following code – if anyone else has a problem where every page is working when loaded directly but when you’re navigating around it doesn’t – your SquareSpace theme updates content using JavaScript (you can often tell by there being a # in the URL as you navigate around). Add the code below to fix:
 

<script>window.setInterval(function() { mutated = true;}, 250);</script>

Add the code line above at the bottom of your Code Injection area. This problem occurs on *some* SquareSpace themes so don’t use it if you’re not seeing the problem – the value of 250 means to check for translations every 250 milliseconds – so if you’re seeing a bit of lag in the translations when you move from page to page you can reduce this value but don’t reduce it too far as it will use CPU on the clients browser.

JUSTIN replied 8 years ago

Super. It seems to have fixed it. Thanks Dave.

We use cookies

We use cookies for various things on our site, including our on-site chat bubble (if you use it), our comment forms (if you use them) and for session handling (if you log in).

Other than that, we use cookies to identify where traffic came from to help us understand which traffic turns into sales, we use a cookie for Google Analytics traffic analysis and we use a cookie to customise adverts for our own products we think you'll be interested in.

You can read more detail in our privacy policy page. Please click 'Accept' or 'Decline' to continue.