kbi_user

PS: I checked it was all other plugins off; only SafeSVG and Avada active.

While looking at it, it applies especially to that element: Content Boxes

So it seems its an Avada issue, if you are sure you are correct ??

You can check the images on the main page. Size is 300x200px. Without Safe SVG, Avada applies the correct image sizes. With Safe SVG turned on, the updated height and width attributes (updated by Avada) are not applied. Instead the default height entry is used (35px), while the width enty is correct.

Bottom line: With SafeSVG active, the wrong value for height is used. Maybe just an issue with lazy loading?

Since we found a compatibility issue, I assume it’s up to the definition of the wording “no compatibility issue”. For now we have to disable your plugin after upload of SVGs.

To my mind that’s a compatibility issue.

See: https://www.xspera.com

That’s how it looks, when SafeSVG is turned on:
https://www.xspera.com/wp-content/uploads/2019/07/Unbenannt.jpg

@daryll

Wow I didnt expect ya that fast ??

Sohaib from Avada support just figured that issue out.

You rock ?? Thx for adding it ??

A hitn would be kinda cool ??

issue solved

Thank you a lot, it was a blast.

You are right ?? Issue solved.

Will the dev version automatically update upon release(s)?

what is the recommended usage?

network-wide or per-site?

All is ok now.

From my experience it is different:
1. I refreshed all Caches all the time
2. Despite 1. I still had the “wrong” xml

Conclusion: Apparently it took time until the plugin applied the changed options and refreshed the page internally. Be it scheduled on purpose or plain “blocked” by something else.

Still it works and is cool, so thank you ??