asked on September 1, 2025
Hello,
We are using vue2:
"vue-flexmonster": "^2.9.55",
We keep getting an error and console log of the the below when viewing grids. The grids are accessible after this.
VM1040:2 Something went wrong.
To fix the issue please try the following:
1. Check if the componentFolder parameter is defined correctly.
2. Check if the path to the css file is valid.
3. Check if DevTools (press F12) has an exception.
4. Ask the support team for help
There are no errors showing in the accelerator (v2.9.36).
Is there any reason why this is happening?
Kind regards,
Craig Button
⋅ September 2, 2025
Hello, Craig!
Thank you for reaching out to us.
We were not able to reproduce this issue on our side. The error you see usually occurs when the Flexmonster library files are not loaded correctly, for example, if an incorrect path is pointed to the Flexmonster JS files or assets. This can sometimes happen due to how the application is bundled. We suggest checking our troubleshooting page for more details: https://www.flexmonster.com/doc/typical-errors/#lib-folder
We recommend updating vue-flexmonster to the latest version and following the Vue2 integration guide from scratch to ensure all parameters are set correctly: https://www.flexmonster.com/doc/integration-with-vue-2/
If the issue persists, please share any errors you see in the browser console so we can help further.
Best regards,
Maksym
⋅ September 4, 2025
Hello, Craig!
Thank you for providing more details via the inbox.
It is difficult to pinpoint the exact cause from the error message alone. Could you please share a reproducible example? For instance, you could modify our GitHub demo project pivot-vue to illustrate the issue or provide code snippets and steps to reproduce it. That would really help us investigate and provide a more accurate solution.
Looking forward to hearing from you.
Kind regards,
Maksym
⋅ September 11, 2025
Hello,
Hope you are doing well.
We are wondering if you tried following our guide to reinstall vue-flexmonster package to resolve the issue.
Please let us know if you need any further assistance.
Best regards,
Maksym
⋅ September 11, 2025
Apologies for not coming back to you. This problem has seemed to disappear after we moved from a temporary key back to a permanent key.
⋅ September 12, 2025
Hello,
Thank you for your reply.
We are glad to hear that you were able to resolve the issue by changing the key.
Feel free to contact us if more questions arise.
Best regards,
Maksym
