Attached the patch by quicksketch on #64984
I am sure we agreed to lower the priority and move this to the "file system" component. "wont fixes" will be forgotton. This should not be forgotton.
For it remains a bug.
I forgot to mention, that there are other ways around this issue. For example image.module does this. They are not solutions, but simply ways to not run into this form api bug.
* do not set the required flag on a file field.
* then validate it yourself in a validation hook.
The downside is, that the "required" mark (by default the *) is not printed on the file form.
This works. It fixes the issue.
but:
* Its a HACK, spelled in capitals all along. Whether or not we allow such a hack to get in to solve this issue, or not, is not up to me.
* Will it not open up a bit of a security hole? I mean: if we are making exceptions that will allow certain "things" not to pass by the validation, we are moving on slippery ice (or whatever the saying is).
but:
again: it solves the issue. Tested, and confirmed with a few flexinode file fields.
thanks. but I dare not give it a + or - 1. Such issues, IMO are for Dries to decide.....