-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during load #46
Comments
And what is the error? you can follow this example: use DigitalCreative\Filepond\Filepond;
class Post extends Resource
{
public function fields(NovaRequest $request): array
{
return [
Filepond::make('Images', 'images')
->storeOriginalName('name')
->storeSize('size')
->multiple(),
// or you can manually decide how to store the data
// Note: the store method will be called for each file uploaded and the output will be stored into a single json column
Filepond::make('Images', 'images')
->multiple()
->store(function (NovaRequest $request, Model $model, string $attribute): array {
return [
$attribute => $request->images->store('/', 's3'),
'name' => $request->images->getClientOriginalName(),
'size' => $request->images->getSize(),
'metadata' => '...'
];
})
];
}
} |
Storing metadata in your documentation works perfectly. I use this method when I wish to keep the original name of my uploaded files and when I wish to create a custom path :
With this method available in the Nova documentation, I use the Now when I use Filepond, the original file name is perfectly preserved in my upload folder and the custom path is created too:
But the error appears in If I check the image column in my database: When I edit the syntax in the path, it doesn't change anything: The error message doesn't display the original name of the image The error appears during load. |
Having the same problem, it seems the last commit f27930e is causing this issue and removing the change done fix the issue. |
Awesome package.
Just one error when i try to keep my
filename
and store to mymedia disk
.The text was updated successfully, but these errors were encountered: