On Thu, Nov 20, 2025 at 2:00 PM Andrey Andreev <[email protected]> wrote: > > Hi Brady, > > I agree that E_WARNING is a poor way to handle this limit, and IMO a fatal > error should be triggered instead. The ability to suppress and ignore is the > root cause of why your situation is possible at all, and Laravel's behavior > in this instance also did you a massive disservice. > > That being said however, this is also an extreme and self-inflicted edge > case. 1k is an absurd number, even 100 input vars should be a sign of poor > code logic. I urge you to redesign your solution entirely instead of looking > for a quick workaround.
In our case, we had a multi-select (<select> with the 'multiple' attribute) that listed a few thousand users. You can select them all, and each selected value counts towards the 1000 fields being submitted. You could argue that it's poor design, and, maybe, it could be. But it's still a valid use-case IMHO. -B.
