Updating from 3.2.94 to 3.2.135 breaks my menu

Hi, recentrly I'm having some performance issues with my filamentphp project, after some readings, I decided to update from my current version to the newest, and luckily my resource has improved, I noticed that some files were published into the public directory, as I have made some changes in tailwind classes (for example to add some color in a row) I added a custom theme, so after updated my project I ran the npm run build, but unfortunately the menu it's now over my main panel, so: - should I run the npm run build? - should I use something else? I was testing between versions, and even though on some of them my menu is working well, some errors of livewere appear, which I can see in the newest releases are resolved. So I'm trapped in the update process, idk If I need to do something else given I have a custom theme? is it the problem? Ty, I appreciate some guidance.
No description
Solution:
yes, that was the problem, those are the initial parts of my theme.css, I started removing things and finally, I found the solution: resources/css/filamentphp/app/theme.css @import '/vendor/filament/filament/resources/css/theme.css'; @import '/vendor/awcodes/filament-table-repeater/resources/css/plugin.css';...
Jump to solution
9 Replies
Rolland
Rolland4w ago
i thought people normally run the npm build whenever this kind of problem occured
awcodes
awcodes4w ago
Do you have the filament views published? That’s the only thing I can think would be the problem here.
hizmarck
hizmarckOP4w ago
do you mean something like this?
No description
hizmarck
hizmarckOP4w ago
btw I'm using your table repeater, It's amazing! 💯 ironically running that command breaks the ui :S
Rolland
Rolland4w ago
LMAO
awcodes
awcodes4w ago
That actually looks ok. Maybe view cache?
hizmarck
hizmarckOP4w ago
I removed my theme, ->viteTheme('resources/css/filament/app/theme.css'); Now that the menu is working, I know that the problem is the theme. but how it was working in the 3.2.94 version but it doesn't in the new one?
awcodes
awcodes4w ago
That could be a few things. Could be content paths in the tailwind config or even specificity in your theme. Hard say without any code.
Solution
hizmarck
hizmarck4w ago
yes, that was the problem, those are the initial parts of my theme.css, I started removing things and finally, I found the solution: resources/css/filamentphp/app/theme.css @import '/vendor/filament/filament/resources/css/theme.css'; @import '/vendor/awcodes/filament-table-repeater/resources/css/plugin.css'; @config 'tailwind.config.js'; @tailwind base; @tailwind components; @tailwind utilities; ... more code... these 3 ones: @tailwind base; @tailwind components; @tailwind utilities; tyvm to both, I really appreciate their time.

Did you find this page helpful?