Get Free Trial

How to debug errors?

Artem asked on June 25, 2020

I am currently in process of upgrading Flexmonster version from 2.7 to 2.8 and faced following issue:
When I click “Apply” in fields popup after adding new field to any category console error is shown(attached) and nothing else happens.
Judging by the migration guide the only thing that needed fixing is usage of availableAggregations:!api-upd
But refactoring code to use mapping object didn’t help, so I’m not sure how should I proceed. Unfortunately I can’t reproduce it in some online code sharing tool, so it’s likely that problem is on my side, but maybe you can help by answering a couple of questions.

  1. Maybe you have an idea what’s wrong by the look of an error?
  2. Is there any way to get more detailed error description? Debugging minified code to understand what should be there instead of undefined is not an easy task 🙂


3 answers

Vera Didenko Vera Didenko Flexmonster June 25, 2020

Hello, Artem,
Thank you for reaching out to us. 
We would like to explain that last week our team fixed the same issue. 
Could you please update to the latest minor version of Flexmonster (v. 2.8.9, build 06/23/2020 14:33:55)? This should resolve the issue.
As for a more detailed error description, we would like to kindly explain that it is not possible due to the fact that Flexmonster’s code is minified.
When debugging errors, first of all, we highly recommend making sure that you’re using the latest version of Flexmonster (you can check this information by clicking on the grid and pressing Ctrl+Alt+i). If not, please try updating to the latest version, as your bug may have already been fixed. If the latest version of Flexmonster is being used, the general approach is to check the browser dev console for errors, check the Flexmonster initialization code, API call usage, report configuration. In case the cause for the error is not found, you can always reach out to us and we will investigate the issue further. When reporting an issue, providing any related details will greatly help our team to solve the problem, for example:

  1. Steps on how to reproduce the error
  2. Screenshots of the browser dev console
  3. Your report configuration
  4. Your browser version 
  5. The used data source type
  6. Sample (dummy) data 
  7. Code samples or access to the environment where the issue is reproducible. For example, you can modify the following JSFiddle so that the issue is reproducible and share it with our team:

Please let us know if this helps.
Waiting for your reply. 
Kind regards, 

Artem July 1, 2020

Hi Vera,
I am updating Flexmonster through NPM and had 2.8.9 version when error was happening. Updating to the latest version(2.8.9-2) helped.
By the way, are there any benefits in updating Flexmonster through manual package download instead of NPM?

Vera Didenko Vera Didenko Flexmonster July 2, 2020

Hello, Artem,
We are glad to hear that everything works fine for you.
As for updating through manual package download or NPM, both ways are equivalent. 
The difference lies in how Flexmonster is integrated into your project: whether it is imported as an npm module or referred to from the downloaded package.
Please let us know if any further questions arise. 
Kind regards, 

Please login or Register to Submit Answer