Need a special offer?Find out if your project fits.
+

Localization problems (Maximum call stack size exceeded)

Resolved
Guillaume BREDIF asked on April 20, 2018

Hi,
 
We are trying to translate our pivot grid (v2.416) to french (fr.json that we get from the github)
but it doesn't seem to work and it throws a lot of errors in the browser console.
The fr.json file is loaded (see screens) and we tried other files (en.json, es.json ...).
 
Whenever we try to add localization to the Flexmonster instance (global), the pivot grid can't be drawn and we get a
"Maximum call stack size exceeded" in the console. (flexmonster_global.jpg)
 
On the other hand, when we put the localization directly into the report, the pivot grid is drawn but only the Fields sub-screen
is partially translated. (flexmonster_report_fields.jpg & flexmonster_report_console.jpg)
 
Any ideas would be really appreciated.
 
Thx in advance

6 answers

Public
Guillaume BREDIF April 20, 2018
Public
Dmytro Zvazhii Dmytro Zvazhii Flexmonster April 23, 2018

Hello Guillaume, 
Thank you for your question. Please find the example of applying localization here: http://jsfiddle.net/Lz8sjbnf/67/. Also, we have attached the latest localization file with all the necessary properties. Please note, that some of the properties may be untranslated. In such case, you will need to search them in the file and replace the English translation with the French.
Please let us know if everything works fine for you.
Regards,
Dmytro

Attachments:
fr.json

Public
Guillaume BREDIF April 24, 2018

Thanks for the answer Dmytro.
I used that exact example to implement localization (and tried your fr.json file) but I get the same errors.
I think another framework is causing the issue. Our pivot grid is embedded in an ExtJS 3.4 container or panel.
Everything works just fine if we don't use localization, but when we do : https://jsfiddle.net/zh2fevr0/
Regards,

Public
Dmytro Zvazhii Dmytro Zvazhii Flexmonster April 24, 2018

Hello Guillaume,
Thank you for the detailed feedback. We have managed to reproduce the issue on our side. The necessary fix will be added to the next minor release ETA May 7.
Best regards,
Dmytro

Public
Dmytro Zvazhii Dmytro Zvazhii Flexmonster May 7, 2018

Hello Guillaume,
We are glad to inform you that the version with the fix has already been released. You are welcome to update the component.
Regards,
Dmytro

Public
Guillaume BREDIF May 14, 2018

Thanks Dmytro, everything works just fine with the last version.
Best regards,

Please login or Register to Submit Answer