closed as duplicated Report of #14356

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/16795

Re-opening. #14356 is specific to com_fields and this is more generic

Looking into this it's caused by line 294 on
libraries/cms/helper/media.php

'xml', 'xmp', '!DOCTYPE', '!--',

to be exact. Each of these is a match within an SVG.

My only thought is to add an exception here if it is an <SVG and run a basic sanitizer through it?

@tonypartridge any Progress on this?

I tried to go to his site... way uncool

This might be a viable solution.. https://github.com/darylldoyle/svg-sanitizer

@tonypartridge idk where you got that path from.. It doesn't exist in current J! staging.

@N6REJ The path has changed for 3.8 I believe. it is now:
/libraries/src/Helper/MediaHelper.php

As an intermediate step could svg upload/edit support be added in Templates:Customize?

That would have the ACL restrictions for uploading already taken care of. It also allows for the more likely use case of svg's as a template elements rather than end user uploads via media manager.

try this: #13499

As @dgt41 stated, webp is not implemented either so this would be a perfect time to make this happen.

why add support for an image format that is not supported on the set of browsers joomla supports

Users can deploy Joomla sites with higher requirements than what we offer support for out-of-the-box.

so this would be a perfect time to make this happen

Are we talking for Joomla 3 or 4 here?

@dgt41 thanks for the suggestion. My use case is for uploading and editing svg's within the template manager. I am able to upload but not to edit within the code editor at Templates:Customize. I am not even making a big push for svg inclusion in media manager. I am advocating for the ability to make adjustments to existing svg's as template elements. As I suggested above, inclusion in just templates provides better ACL control than broader implementation and provides for the most likely scenario of using them as template design elements rather than content items.

@genr8r so you need something like: #14485 and then allowing svg files to be manipulated in the com_template options...

@dgt41 exactly. Just thought other developers might also appreciate this flexibility rather than having to break out an IDE to tweak a color or other parameter on an svg element used in a template. I am sensitive to @brianteeman comments about unsupported image formats and I am aware of the security concerns that svg's introduce. It is just that I am seeing more svg implementation in templates and frameworks (specifically Gantry).

Please test PR #28599.