has something changed Filament v3.3.37?
I'm using Forge, and it has updated filament files, and now a basic boolean always returns true. with a check and icon
Tables\Columns\IconColumn::make('is_published')
->boolean(),
in the DB is 0
Was there a recent update to JS files?
thanks
11 Replies
GitHub
Comparing v3.3.36...v3.3.37 · filamentphp/filament
A powerful open source UI framework for Laravel • Build and ship admin panels & apps fast with Livewire - Comparing v3.3.36...v3.3.37 · filamentphp/filament
Doesn't look like anything related to IconColumns. Are you sure you were on 3.3.36 before?
This is so weird, if i click into table row, the is published column is showing as a toggle and its off, so it reading the DB properly on this view, but the table view all records are showing as true when some are false, do you know what i could check? On my local its fine but in prod its got the isses, thanks
it was an SSR issue i turned SSR off, and it's working again. Is there something I need to do to get SSR working on Forge with Filament? something specific to Filament? Thanks
SSR? What do you mean? How can you turn off Server Side Rendering for PHP?
yes I get you but if I turn SSR on for the inertia side, it seems to be conflicting with filament. the ui issues, if I have SSR enabled via Inertia on Forge.
Hm. That's interesting.
ive rechecked, with inertia on in Forge, the ui is not following what's in the DB. The issue is only on the table, though. I turn off SSR and it works perfectly. so weird
What is "turning on SSR in Forge" acutally doing?
So 'turning on SSR in Forge' basically:
Enables SSR in the config - flips inertia.ssr.enabled to true
Starts an SSR daemon - Forge runs the Node.js SSR server automatically
The weird thing: When SSR is on, Filament's boolean columns get confused. Like, a tinyint(1) column with value 0 shows a green checkmark instead of an X.
But when I turn SSR off, everything works perfectly.
Setup: Laravel 12, Filament 3.3.37, Livewire 3.6.4, PHP 8.3, MySQL 8.0.43
Seems like there's some hydration mismatch happening between server and client rendering. Any ideas? Is this something you've seen before? Thanks
No, but I never had a scenario with SSR and Filament.
ah ok, maybe you could send to the team to see if they can check the issue? Thanks