v3.2.139

[danharrin]

What's Changed

• Patch breaking SPA mode changes in Livewire.
• Bump vite from 4.5.5 to 4.5.9 in /docs-assets/app by @dependabot in Bump vite from 4.5.5 to 4.5.9 in /docs-assets/app #15564
• Update Armenian Translation by @arshaviras in Update Armenian Translation #15566

Full Changelog: v3.2.138...v3.2.139

---

This discussion was created from the release v3.2.139.

[jf-hellotess]

SPA mode errors seem to still be there ...

[danharrin]

Please share the errors in an issue with reproduction

[jf-hellotess]

It seems to be an issue with the package i am using ( i guess the filament global search modal is not fully compatible with alpine v2)

[kjjd84]

@danharrin

since updating to this version tables now flicker white for a split second on each pageload in dark mode

[danharrin]

Which browser and OS are you using? I can't see that in Chrome

[kjjd84]

@danharrin i am using chrome on macos on my prod server (digital ocean)

heres a video of what happens: https://imgur.com/jJtRrNu

see how theres a white flicker in various ui elements when navigating between pages

[kjjd84]

@danharrin i should mention this does not happen on local but does on prod, its like network latency affects this

[danharrin]

Can you please try v3.2.140, @kjjd84? I don't encounter flickers on that release, do you?

[kjjd84]

Can you please try v3.2.140, @kjjd84? I don't encounter flickers on that release, do you?

@danharrin v3.2.140 seems to have resolved the issue. THANK YOU DAN!

[melvinmihaylovnulabg]

Hey, guys!

For me this update broke the js. All of the clickable components like dropdowns, checkboxes, selects just stopped working. Bulk buttons were visible even if no records were selected. The selects were empty and unclickable.
The web browser i am using is Chrome and Safari, they both did not work.
I rolled back the upgrade until it is fixed.
If you need more information, i am open to collaborate.

[danharrin]

If you read the error I do not think this is related though? Livewire is no longer available on your server, we do not control that asset

[melvinmihaylovnulabg]

I'am going to rollback and upgrade to this version of the filamentphp and then can i share the problem with you, so you can give me suggestion how can i fix it?

[danharrin]

I don't know how to suggest a fix for this, I don't know what is going on in your production server

[melvinmihaylovnulabg]

I understand that debugging this issue remotely is quite challenging, but any collaboration on resolving it would be greatly appreciated. Our users rely on these panels in production, and ensuring their stability is a top priority. If you have any insights or suggestions, we’d be extremely grateful for your support.

The problem occures only when i update the version from 3.2.137 to 3.2.140. I am updating filament with this command - composer update "filament/*" --with-dependencies.

Update "filament/actions" version from "v3.2.137" to "v3.2.140".
Update "filament/filament" version from "v3.2.137" to "v3.2.140".
Update "filament/forms" version from "v3.2.137" to "v3.2.140".
Update "filament/infolists" version from "v3.2.137" to "v3.2.140".
Update "filament/notifications" version from "v3.2.137" to "v3.2.140".
Update "filament/support" version from "v3.2.137" to "v3.2.140".
Update "filament/tables" version from "v3.2.137" to "v3.2.140".
Update "filament/widgets" version from "v3.2.137" to "v3.2.140".
Update "kirschbaum-development/eloquent-power-joins" version from "4.0.1" to "4.1.0".
Update "livewire/livewire" version from "v3.5.12" to "v3.5.19".
Update "spatie/color" version from "1.7.0" to "1.8.0".

[danharrin]

The errors are because the Alpine/Livewire Javascript is not loading properly, they do not look related to Filament. I have also not had this report from any other Filament user so I expect it is an issue just on your server. Please make sure all your caches are cleared, and do not publish the Livewire assets if you do not need to change them.