Weird css styyling after v3 to v4 upgrade
Hi folks, I just upgraded from v3 to v4 this simple app, it just 2 basic Resources. First screenshots are v4 screens and last two ones like it used to be on v3. I was using custom theme on v3, after checking for some solutions around I disabled custom theme and ran all suggested commands I found. But still could not get it running fine. What else shloud I check to solve this? It is a simple app, if no easy solution, I've no problem to start fresh app on v4.
Thanks in advance for your help
9 Replies
You need to upgrade your custom theme to use tailwind v4 too. https://filamentphp.com/docs/4.x/upgrade-guide#high-impact-changes
Hi, thanks for the quick response. Already updated to v4 format and the same. I disabled custom theme on Panel Provider, ran npm run build, deleted assets, publishing again, npm run build and other cominations and not neigher has effect. I'm not using any custom page or blade/layout. Just plain resources. Navigation look s fine, the problem seems to be just on Tables and Forms
Do you have the views published?
Not sure, let me check that.
Were not published. Just published, but still the same. Also ran npm run build just in case, but the same. Must I add resources/views/vendor/filament/* to any place?
They shouldn’t be published unless you absolutely have to.
In the link I shared, the second item shows how to change the custom theme css file. If you have a tailwind.config.js in the root you might need to remove that too.
There’s so many different things it could be.
Do you have a repo you can share? Feel free to DM if you don’t want to post it here.
Is this happening locally or on the server.
Locally on my machine, I have not upgraded production yet
Will try a couple more of things, if no success will prepare some repo for you to check. But this will be tomorrow. I'm going out now. Thanks for your answers
No hurry.
I have seen this where the config isn't configured in the css to search the views folder for the css classes being used.
In other cases people still had the
postcss.config.js which messed up Tailwind stuff.