Despite the COVID-19 outbreak, our team continues operating at full speed. We are always here to support and answer all your questions.

Feel free to reach out by filling this quick form.

Fill the form
Get Free Trial

Which versions are considered stable?

Viktor Szőke asked on October 13, 2020

We are using ng-flexmonster with an angular application. We upgraded from v2.8.5 to the latest version (v2.8.17) because there was a bugfix for an issue when changing views.
After the upgrade we noticed multiple issues with modals, like the Save button was unclickable or the formula editor was also partially hid under the pivot grid. We tried several other versions, but it was quite easy to find a bunch of other bugs and issues.
Are there any versions that are considered stable? Because we roll out releases in every 3 months, we cannot upgrade for every minor release. How can we make sure that when we are committing for a version for our release, we are using a well-tested, stable version?

2 answers

Vera Didenko Flexmonster October 14, 2020

Hello, Viktor,

Thank you for reaching out to us. 

Our team would like to explain that each new release of Flexmonster (both minor and major) is considered stable and has been thoroughly tested. Bug fixes and improvements are introduced with each new release. Therefore, when rolling out a new release, we highly recommend updating to the latest version of Flexmonster.

We would like to explain that the 2.8.16 Flexmonster update introduced particular accessibility improvements, which involved changing specific CSS configurations for many elements of Flexmonster UI.
With that in mind, the mentioned UI issues might be caused by your browser’s caching or the CSS file not being updated properly.

Our team suggests the following steps to resolve the issue: 

  1. First, uninstall the flexmonster module: 
    npm uninstall flexmonster
  2. Next, reinstall the ng-flexmonster module:
    npm install ng-flexmonster
  3. Also, please make sure that the style CSS file is imported from "flexmonster/flexmonster.min.css", like in our Angular sample project on GitHub:
  4. In addition, our team kindly recommends clearing your browser’s cache and reloading the page. Please check that the latest 2.8.17 version of Flexmonster is being used (you can check this information by clicking on the grid and pressing Ctrl+Alt+i).

Please let us know if this helps to resolve the issues.

Looking forward to your feedback.

Kind regards, 

Vera Didenko Flexmonster 2 days ago

Hello, Viktor,
Our team would like to kindly take an interest in whether you found our previous response helpful.
Did the provided steps help to resolve the issues?
Please let us know if everything works.
Kind regards, 

Please login or Register to Submit Answer