Hello again. If you mean that the navbar cannot be pinned for the 1200px, the expected behavior is not satisfied. Normally, it should be pinned if the size is 1200px and wider, and open on hover if the width is less. But, it seems working in both cases.
I have also checked on different browsers such as Safari, Opera and Firefox. If you are getting this error for another browser type, I can assist further.
Hello, we weren’t able to resolve the issue just yet, but it is on track to be fixed by the end of the next release. Thank you for your patience, and apologies for the wait.
This fix will be released by the next patch version for 8.X.X. Thank you for your cooperation.
As mentioned earlier, the approach will depend on your specific business needs. Here are two options you can follow to customize the relevant sections. If your goal is simply to hide certain elements, you can achieve this easily by overriding them with CSS properties.
As an alternative, you can use the npm-force-resolutions tool to temporarily address these dependency issues. This solution allows us to enforce specific versions and maintain stability in the short term. Rest assured, we’re actively working on a more permanent fix, which will be included in the upcoming release.
Hello, this component is not directly replaceable. You can either try to customize the root component that has the eAccountComponents.PersonalSettings , or customize the form using the extension system based on your requirements.
I am still unable to replicate the issue on my end.
Thank you for providing extra details. For the best stability, we recommend using Yarn for managing dependencies, as it handles compatibility more smoothly. However, if switching to Yarn isn’t possible, adding the --legacy-peer-deps flag to NPM can also maintain stability by bypassing certain version checks. Our priority is to keep your application stable and reliable, so please let us know which approach works best for you.
Thank you for sharing additional details. I was able to achieve a successful build without any issues, which leads me to believe this may be related to specific customizations in your setup. Could you provide us with a sample project to help us investigate further? Please feel free to reach out via email at sumeyye.kurtulus@volosoft.com.
Hello, I could not duplicate the same problem considering these configurations. May I ask how you have configured our modules in your app.module.ts ?
