->fill() does not work with SpatieMediaLibraryFileUpload
I am trying to implement a form where users can come back and edit their answers or upload new files but whatever I try to fill the
SpatieMediaLibraryFileUpload with the data fails. If I provide uuid, path, url it doesn't give any error but also doesn't populate the field. If I were to give UploadedFile, Media or MediaCollection it gives an error with Filament\Forms\Components\SpatieMediaLibraryFileUpload::{closure:Filament\Forms\Components\SpatieMediaLibraryFileUpload::setUp():90}(): Argument #2 ($file) must be of type string, array given
this error originates from closure used in$this->getUploadedFileUsing when the function setUp has been called. It's driving me insane.
I have also tried to just use relationship but still the same problem!
...Solution:
For any one having similar problems here is the solution
1. Define your model in the
mount() function
2. Because lazy loading is disabled for Media model, add ->load('media') to the model you are fetching
3. Explicitly define ->model($this->yourModel) in the SpatieMediaLibraryFileUpload
4. Fill the field using the uuid of the media you're trying to use...
v4 Page number pagination
Is the click on page number type of pagination still a thing on v4 (example pic I found from v3)? I can only get previous/next buttons to work.
I tried
->paginationMode(PaginationMode::Default), but it's still just previous and next buttons. Maybe I'm missing something. 🤔...Solution:
Repeater limitation
I'm having an issue while adding a new feature to the
repeater. I want to limit the delete functionality, since I don't need to delete the first repeater item but I do need to delete the others.
I tried setting it up with deletable as mentioned in the documentation, but I couldn't achieve the desired result, because it takes the repeater in a general way
This is my code:
```
Repeater::make('members')...
Select with enum options bug in v4
I had a custom select extending Filament’s select, mainly to load enum options and set a default label (used repeatedly in the app). There’s also a cast so values are saved in the DB as the ordered days of the week. This worked fine in v3, but after upgrading I’m facing a bug: when editing a record, the already-selected days still appear as selectable options. If I pick them again, they duplicate and trigger a validation error on save. I suspect this might be related to my cast, but I’m not sure what changed.
I attached the code...
