[TYPO3-core] RFC: #15278: imagefile_ext is used too restrictive

[Xavier Perseguers]

Hi,

> I think the bug is that<img>  tag is rendered with empty values. I would
> expect a warning in Admin panel and no IMAGE output at all in this case. I
> expect the same problem will happen if the file simply does not exist.
>
>>> Sadly I have to give -1 for pure formal reasons. I recognize the problem
>>> you faced and I agree that it *is* a problem.
>> But what can the solution be? In my case editors are limited to pngs?

I agree with Dmitry, the description of this setting is really clear and 
the use you made of it is sadly not correct as you noticed it.

I do not really see the point of limited images to png (as such, read on 
to see what I mean) but if this is really intended, I would suggest:

- Add a setting to limit the image types that may be uploaded
- Use the hooks I added recently to "delete" invalid files after the 
upload (not nice but working), with some flash message explaining it
- Use the extension I created recently (image_autoresize) to dynamically 
convert non-PNG files to PNG upon upload (without applying size 
restriction, some side-use of image_autoresize). Which can then be based 
on user group or directory and as such is much more powerful than 
deactivating non-PNG for everybody.

Cheers
Xavier