nielsdscrd
Table actions on separate row - without split?
Thank you for the suggestion. I tried it just now. I would work if I could put some actions at the start, others at the end. With 4 actions at the start, people will not see what they're paying and still have to scroll horizontally. The Split solves the scrolling, but it messes up the layout, regardless of where I put the action buttons.
5 replies
adding trait Translatable will make all fields Translatable
Much like my own, this is a work-around, not a true fix. Replacing the incorrect data at the moment of Saving means the problem may pop up in other places as the actual cause is not resolved. It may be difficult for us to trace it back to the root, but hopefully @Dan Harrin or someone else with deeper knowledge of Filament can find the time to have look at this.
79 replies
Is there a thing like hot reload for Filament resources?
Although Filament's documentation mentions that you should use @vite('resources/js/app.js') when using your own Livewire components, Filament itself does not seem to include this. Hence the Vite listener is invoked on your regular pages, but not Filament panels.
41 replies
adding trait Translatable will make all fields Translatable
I use this modified save() function. It merges the correct data into every locale. I tried filtering out the data initially, but then validation may fail due to required fields.
79 replies
adding trait Translatable will make all fields Translatable
@larazeus just added my comment to your GitHub issue. I have the same issue. Initially all fields are updated in the database correctly. Then unexpected additional queries reset all non-translatable fields back to their original values.
79 replies
Show a NavigationItem to admins only
v3.0.0-beta10. The segfault can be fixed with this: https://github.com/livewire/livewire/pull/6008 (My error also occurs without this fix. In my case I hit the error prior to the other segfault error occurring).
11 replies