Skip to content
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

Undefined variable $getMaxParallelUploads error on latest FilamentPHP update #15372

Open
zaiimrq opened this issue Jan 18, 2025 · 4 comments
Open

Comments

@zaiimrq
Copy link

zaiimrq commented Jan 18, 2025

Discussed in #15364

Originally posted by zaiimrq January 17, 2025

Package

Form builder

Package Version

v3.2.1.33

How can we help you?

Undefined variable $getMaxParallelUploads error on latest FilamentPHP update

Describe the bug

After updating to the latest version of FilamentPHP (released last week), I encountered the following error when loading a page that includes a FileUpload field:

To Reproduce

Steps to reproduce the behavior:

  1. Update to the latest version of FilamentPHP.
  2. Use the following FileUpload configuration in a form:
    FileUpload::make('image')
        ->imageEditor()
        ->image()
        ->directory('projects')
        ->optimize('webp')
        ->required(),
  3. Load the page where the form is displayed.

Expected behavior

The FileUpload field should work as expected, especially since the maxParallelUploads feature appears to be specific to multiple file uploads, and I am not using the multiple() option in my code.

Environment

  • Operating System: Windows
  • PHP Version: 8.4
  • Filament Version: Latest (updated last week)
  • Web Server: Built-in PHP server (php artisan serve)

Additional context

The error occurs even though maxParallelUploads should be irrelevant for a single file upload configuration. This issue seems to be a regression introduced in the latest update.

@danielschweiger
Copy link
Contributor

same here

@zaiimrq
Copy link
Author

zaiimrq commented Jan 18, 2025

same here

Do you have any solution?

@danielschweiger
Copy link
Contributor

I am back on 3.2.132 for my live app now. no issues there. had no time to investigate in detail.

@danielschweiger
Copy link
Contributor

@zaiimrq
see: #15309

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants