CSS not working after fresh install of filament
The login page and the authenticated dashboard page don't load the CSS. This is on a fresh install.
Solution:Jump to solution
Figured out what it was. The ASSET_URL was set and it was causing issues with path resolution I'm assuming.
18 Replies
How is your vite file looking? Maybe there is a miss.
also try runing
sail npm run dev to start the watcher and it should work. If you would like to run without the watcher, you should run the sail npm run build to create the files. (you can omit the "sail" if you dont use it).env url is likely dirrect to the accessed url or filament assets are not published
I also have problems suddenly with my backend. It seems that not all the CSS is loaded. After updating to the latest version.
No console errors
OK, when reverting back to version 3.2.115 the issues are gone.
once you upgrade run:
npm run build
php artisan filament:upgrade
Hello 👋
I have the same issue. I didn't have have any color in my backend. I've run
npm run build
php artisan filament:upgrade but the issue is not resolved.
@Daniel Plomp have you find any solution to your problem please ?
Well, I revert to version
3.2.115 for now.Can you create an issue in Git please
I'm under version 3.2 in my composer.json. I have done something wrong ?
No, if you want to upgrade then you need to change the version to 3.2
I'm unable to see colors in my backend. So while I was "googling" I fund that I have to upgrade to solve the problem but. It's not solved the issue Mister @toeknee .
If you right click inspect browser, what issues do you see in console?
There's nothing in console.
A screenshot of my console.
I fund solution to my problem. I've upgraded to 3.2.115. Run npm run build. Delete vendor folder in resource/view. So it's working...
Thank you for your answers @toeknee @Daniel Plomp 👌👌👌
same issue here, I've updated to the latest version and my css got all messed up, also reverted back to 3.2.115 for now.
Error persists with 3.2.117.
Still haven't resolved this. Any solution?
Solution
Figured out what it was. The ASSET_URL was set and it was causing issues with path resolution I'm assuming.