Hello,
I have the following problem. My page is no longer displayed correctly because JS or CS is probably loaded incorrectly and I can't explain why this is, in any case everything I use the <x-base-layout> for is not displayed correctly or headers and Aside Blade not loaded correctly (see pictures). Are there any ideas as to what this could be? I have already run npm run dev several times and checked webpack mix and base blade, unfortunately no results.
Where can i search for the problem?
Would be amazing if you could help me out. I am sitting on this error for hours now.
The problem is shown in this screenshot, you see first page (from the past) looks good and sidebar loading fine, also header has spacing.. The Screenshot above shows the actual look and it is not loaded correctly, sidebar not showing only if i turn: data-kt-drawer="true" from true to false but then its showed in different look. Some settings from KT are not loading correctly.
https://f71.workupload.com/image/nCRwkDWKHeq
Thank you very much,
Thomas
Great to hear that you fixed it! If you run into any more issues, feel free to reach out!
I fixed it by changing the webpack mix js {demo} parameter path to demo3 (static non dynamic) and that worked for me!
Thank you very much for your quick feedback. Indeed something is wrong in the style bundle, I have now downloaded a pre-made style bundle for demo 3 and replaced it in the /public/ folder as style bundle, then everything is displayed correctly. That means Laravel Mix has problems to generate the correct style bundle using SASS.
In the copied style bundle, for example, the class .aside is preserved 90 times, in my generated SASS style bundle only 1 time. This means that the code is not generated correctly. I have already tried to reinstall npm several times to change things, but have not yet found out where exactly the error could arise. Now I have to do some more research.
If you have any ideas on what to do, please let me know. I am happy about every suggestion.
Thank you very much !!! I will post here when the problem is solved and how I solved it.
Hi
Hi Thomas Stabel
There might be a conflict between the assets from Demo 1 and Demo, each demo has different assets and JavaScript that initializes components. Make sure to separate the assets loading for each demo.
Also, open your browser's developer console and look for any JavaScript errors or missing assets.
Thank you