try to import a file larger than 1MB, a validation error will occur.

[bzy107]

Package

filament/filament

Package Version

v3.2.80

Laravel Version

v11.7.0

Livewire Version

v3.4.12

PHP Version

PHP8.3.7

Problem description

If you try to import a file larger than 1MB, a validation error occurs and the import fails. This is likely a validation error on the front end from Livewire or Filepond, but the exact cause is unclear.
This occurs when a file is selected or dragged and dropped.

The importer has a feature to specify the maximum number of rows with maxRows(), but there is no feature to specify the file size. It would be very useful to have control similar to a maxSize() feature.

Please consider this.

Expected behavior

Should be imported

Steps to reproduce

On the /admin/patients screen, perform the import using ./storage/export-1-patients_over1M.csv.

Reproduction video:

2024-05-17.23.47.40.mov

Reproduction repository

https://github.com/bzy107/filament-select-bug

Relevant log output

No response

[petrisorcraciun]

check config/livewire.php -> temporary_file_upload -> 'max:...',

[bzy107]

check config/livewire.php -> temporary_file_upload -> 'max:...',

I tried it, but it didn't work.
The same error occurs when the size exceeds 1MB. So, it seems to be caught by the validation before it even reaches livewire.php, but I don't understand the lifecycle well enough to pinpoint the exact issue.

when 'rules' => ['max:1024']:

when 'rules' => ['max:1023']:

[aSeriousDeveloper]

File Upload size validation is handled by the minSize and maxSize functions on the form component: https://filamentphp.com/docs/3.x/forms/fields/file-upload#file-size-validation

This is because FilePond, the JS package used for file uploads, has its own validation for file size that filament hooks into.

However, with the FileUpload component being baked into the Import Action, there's no easy way to modify these values yourself.

The max filesize should automatically be set to null if it isn't provided automatically, which would make me assume that any size would work. Can you check your phpinfo(); for your upload_max_filesize ?

Where values are set within the blade component

filament/packages/forms/resources/views/components/file-upload.blade.php

Lines 72 to 73 in 81949c0

	maxSize: @js(($size = $getMaxSize()) ? "{$size}KB" : null),
	minSize: @js(($size = $getMinSize()) ? "{$size}KB" : null),

Where the FileUpload component is made in the ImportAction

filament/packages/actions/src/Concerns/CanImportRecords.php

Lines 80 to 83 in 81949c0

	FileUpload::make('file')
	->label(__('filament-actions::import.modal.form.file.label'))
	->placeholder(__('filament-actions::import.modal.form.file.placeholder'))
	->acceptedFileTypes(['text/csv', 'text/x-csv', 'application/csv', 'application/x-csv', 'text/comma-separated-values', 'text/x-comma-separated-values', 'text/plain', 'application/vnd.ms-excel'])

[bzy107]

Thank you for your reply. I have already checked the same points.

Since $getMinSize in FilePond is not set, it should be null.
upload_max_filesize is also set to 2MB, so that’s not the issue.
Therefore, I’m stuck.

[bzy107]

So, does this mean that currently in the importer, we can't set minSize() and maxSize(), so we should add methods for them?
I need to investigate a bit more.

[bzy107]

Progress Update:

I modified the CanImportRecords.php file to add maxSize(), but it didn't work. Further investigation is needed.

maxSize set 100MB:

[bzy107]

I found the cause.
It was not on the Filament side but on the Nginx side, where I overlooked a 413 Request Entity Too Large error.

I resolved it by adding the client_max_body_size setting.

server {
    client_max_body_size 10M;
    ....

I hope this helps anyone who encounters the same issue.