Console error in version 2.7.1

posted on March 16th, 2019

Closed

Ravi asked on March 16, 2019

Hi Team,
I am an licensed user.
We are facing below issues in latest flexmonster version 2.7.1.

Two console errors when 'Days Ago' filter setting is applied for the pivot chart
Due to this, chart legend-text comes 'undefined'

But, we don't see these issues in 2.6.14 version.

Note: We have also attached snapshot for the above two issues, please get it.

Attachments:
consoleError_v2.7.1.png

4 answers

Public

Vera Didenko ⋅ Flexmonster ⋅ March 18, 2019

Hello, Ravi,

Thank you for writing to us and for providing us with a screenshot.

A similar problem has been reported to us and we are currently working on a solution.
The fix will be available in the minor release with the ETA March 25th.

In case you would like us to check the fix on your sample, please provide us with a sample or a JSFiddle example.

Please let us know if this works for you.

Best Regards,
Vera

Public

Ravi ⋅ March 18, 2019

Hi Vera Didenko,
As you requested, we have provided our demo samples in the below JSFiddle links, please get it.

Console error: 'O4n.substr is not a function' - chart-view
https://jsfiddle.net/abufiddle/wg7maby5/3/
Console error: 'f1w.replace is not a function'
https://jsfiddle.net/abufiddle/wg7maby5/11/

Notes:

At default, this sample gets referred to the 'latest v2.7.1' and so you will get the above mentioned console errors for the 'pivot chart/table view'
To make it work, just refer the v2.6.14 script file(flexmonster_V2.6.14.js) at last. Now, the sample works fine without errors.

Public

Vera Didenko ⋅ Flexmonster ⋅ March 19, 2019

Hello, Ravi,

Thank you for providing us with the JSFiddle examples demonstrating the issues.
It helps a lot and we will check the fix on your examples to ensure that everything works for you.

The fix will be available in the minor release with the ETA March 25.

Please let us know if this works for you and if you have further questions.

Best Regards,
Vera

Public

Vera Didenko ⋅ Flexmonster ⋅ April 1, 2019

Hello, Ravi,

We are glad to announce that the fix is now available in the 2.7.2 version of Flexmonster.
We have checked the fix on the samples you have sent and the issues are resolved.

You are welcome to update the component.

Best Regards,
Vera

This question is now closed