You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After displaying this error, the page cannot be saved anymore.
Here is the SVG:
I believe that some XSS feature is recognizing that there are "xlink:href" and < defs >. This happened to me because I had exported an SVG that contained "meshes" from Adobe Illustrator.
Now how to resolve this (for me):
delete the cache folder
open site in private browser (or delete your cookies / cache of your site). It seems that the error still gets displayed even when the image gets deleted, some information is stored in the browser that causes this infinite message.
now saving works again
to reupload the SVG, delete all the < images > in your svg and remove the "< defs >" tags.
The text was updated successfully, but these errors were encountered:
I have also come across this issue. I have a similar setup: a file field saving to self@ within a modular blueprint. I also get the Failed to save entry: SVG file XSS check failed on on_events error on page save.
The svg I am attempting to save is fairly benign, but it does have the xmlns attribute in the svg tag: xmlns="http://www.w3.org/2000/svg".
sanitize_svg is set to true in /user/config/security.yaml. If I set this to false, the svg file saves to the page correctly. Ideally, I wish to keep sanitize_svg on.
When I upload a specific SVG to a custom modular (see comment below), the page will display the following error:
Failed to save entry: SVG file XSS check failed on on_events
TypeError: can't convert undefined to object after using defaultProps
After displaying this error, the page cannot be saved anymore.
Here is the SVG:
I believe that some XSS feature is recognizing that there are "xlink:href" and < defs >. This happened to me because I had exported an SVG that contained "meshes" from Adobe Illustrator.
Now how to resolve this (for me):
The text was updated successfully, but these errors were encountered: