asked on August 23, 2022
Hello team.
I've a problem with multilevel hierarchies, when there is a an Array.prototype declared as in example, when a user expand a hierarchy (image : bug1.JPG) and then collapse the same hierarchy is launched and error in console (image : bug2.JPG)
Logs:
14:44:23.924 flexmonster.js:1044 Uncaught TypeError: b[d].slice is not a function
at f.Yha (flexmonster.js:1044:356)
at set sf [as sf] (flexmonster.js:1044:121)
at f.J4 (flexmonster.js:882:410)
at f.Lp (flexmonster.js:947:312)
at f.dz (flexmonster.js:1781:372)
at f.KD (flexmonster.js:1780:318)
at b.<anonymous> (flexmonster.js:1746:258)
at b.Fa (flexmonster.js:76:393)
at b.Fa (flexmonster.js:154:123)
at b.Hk (flexmonster.js:1932:380)
Yha @ flexmonster.js:1044
set sf @ flexmonster.js:1044
J4 @ flexmonster.js:882
Lp @ flexmonster.js:947
dz @ flexmonster.js:1781
KD @ flexmonster.js:1780
(anonymous) @ flexmonster.js:1746
Fa @ flexmonster.js:76
Fa @ flexmonster.js:154
Hk @ flexmonster.js:1932
(anonymous) @ flexmonster.js:1922
Fa @ flexmonster.js:76
Fa @ flexmonster.js:154
$U @ flexmonster.js:1859
(anonymous) @ flexmonster.js:1843
How should i prenvent this error ? is it a bug?
thank you
Massimo
⋅ August 25, 2022
Hello, Massimo,
Thank you for reporting the issue.
Our team will take a look at the described behavior and provide a fix with our minor release with the ETA September 19. We will notify you in case of any updates on the matter.
You are welcome to write to us in case further questions arise.
Kind regards,
Nadia
⋅ September 21, 2022
Hello, Massimo,
We are happy to inform you that the issue with extending Array.prototype was fixed.
This is provided in the 2.9.34 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-34/
You are welcome to update the component. Here is our guide on upgrading to the latest version: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please let us know if the fix works fine for you.
Best regards,
Maksym
⋅ September 28, 2022
Hello, Massimo,
Hope you are doing well.
We were wondering if you had a chance to test the updated version. Could you please confirm if the fix works well for you?
Looking forward to hearing your feedback.
Kind regards,
Nadia
⋅ October 3, 2022
Hi team,
I confirm the bug was fixed!
Kind regards,
Massimo
⋅ October 3, 2022
Hi, Massimo,
Thank you for the feedback.
We are glad to hear that the fix works for you!
As always, feel free to contact us if other questions arise.
Kind regards,
Nadia
