CSS not working after fresh install of filament | Filament | Page 1

paper halo Oct 10, 2024, 4:56 AM

#

The login page and the authenticated dashboard page don't load the CSS. This is on a fresh install.

drowsy falconBOT Oct 10, 2024, 4:56 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

vale shale Oct 10, 2024, 6:28 AM

#

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)

fiery aspen Oct 10, 2024, 8:28 AM

#

.env url is likely dirrect to the accessed url or filament assets are not published

craggy valley Oct 10, 2024, 8:44 AM

#

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.

fiery aspen Oct 10, 2024, 8:53 AM

#

once you upgrade run:

npm run build
php artisan filament:upgrade

mental light Oct 10, 2024, 10:39 AM

#

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.

#

@craggy valley have you find any solution to your problem please ?

craggy valley Oct 10, 2024, 10:45 AM

#

Well, I revert to version 3.2.115 for now.

fiery aspen Oct 10, 2024, 10:46 AM

#

Can you create an issue in Git please

mental light Oct 10, 2024, 10:47 AM

#

I'm under version 3.2 in my composer.json. I have done something wrong ?

fiery aspen Oct 10, 2024, 10:49 AM

#

mental light 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

mental light Oct 10, 2024, 10:52 AM

#

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 @fiery aspen .

fiery aspen Oct 10, 2024, 10:55 AM

#

mental light I'm unable to see colors in my backend. So while I was "googling" I fund that I ...

If you right click inspect browser, what issues do you see in console?

mental light Oct 10, 2024, 10:56 AM

#

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 @fiery aspen @craggy valley 👌👌👌

trail hull Oct 14, 2024, 8:55 AM

#

craggy valley I also have problems suddenly with my backend. It seems that not all the CSS is ...

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.

paper halo Oct 15, 2024, 2:46 AM

#

Error persists with 3.2.117.

paper halo Oct 27, 2024, 3:53 AM

#

Still haven't resolved this. Any solution?

paper halo Oct 27, 2024, 4:51 AM

#

Figured out what it was. The ASSET_URL was set and it was causing issues with path resolution I'm assuming.

#CSS not working after fresh install of filament