URGENT: translation not working! (other than on Safari 11.0.3!) , showing both languages after functioning properly before!

Questions & Answers › Category: Questions › URGENT: translation not working! (other than on Safari 11.0.3!) , showing both languages after functioning properly before!

0 Vote Up Vote Down

laura asked 6 years ago

As of today our website is showing both of our languages. It worked well previously. On Safari, any older version and on chrome and internet explorer it started showing both.

Looking forward to a prompt response with a solution.

website: sympower.net !-- Multilingualizer v3.91 -->!-- Multilingualizer v3.91 -->
<script>var mllanguages = []; mllanguages["English"] = 0; mllanguages["Finnish"] = 1; </script><script src="//www.multilingualizer.com/mlcode/multilingualizer.js?v=3.91"></script><script>var mltextblockboundary = '....';</script><style> #multilingualizerloadingscreen { position:fixed; width:100%; height:100%; background-color:white; background-repeat:no-repeat; background-position:center, bottom right; z-index:99999999; top:0px; left:0px; } #multilingualizerloadingscreen.loaded { display:none; } </style>

Laurent replied 6 years ago

Same issue here! On all our website! Thanks

3 Answers

0 Vote Up Vote Down

Filippo Ponzetti answered 6 years ago

I have the same issue. Please solve it before my Client got upset!
Many Thanks

0 Vote Up Vote Down

Ramón answered 6 years ago

The error comes from the version problem. The short solution here is to change the version number from v=3.91 in your code to v=3.92 – then clear browser cache and it works again.

Filippo Ponzetti replied 6 years ago

Many thanks Ramón, it works!

0 Vote Up Vote Down

Freddy Jones answered 6 years ago

Thanks Ramón. This was a bug that was resolved within half an hour and the only affected users in this window. It would have fixed itself had you left it.

Ramón replied 6 years ago

Thanks Freddy Jones. I had not the impression that this bug was only 30 minutes around – but that doesn’t matter. It was Dave who brought up the version number which was the correct solution between 2018-01-29 18:59 till the next day where I had to correct it back. So that would be my perspective here.

I do believe that your comment in this open issue (which should be closed / resolved according to your info) could have been communicated earlier – like a week ago. In the end I’m glad you guys found a solution and your service works.