nikiforova

@qtwrk – could somebody take a look at this?

Thank you muchly for the pointers Andrew, most helpful and much appreciated!

On point 1. I’ll start with a local test of ImageMagick resize and see what it does to jpg/png metadata. That should help me track down/isolate the issue (whether it’s WP or the imagick PHP extension).

On point 2. Yes I’ve seen that WP source, and without further investigation, I took these comments literally (i.e. ONLY exif: Orientation data was preserved, etc…).

But, it seems this protection does indeed apply to ALL metadata fields (as my results have indicated). So I removed lines 856-858 from /wp-includes/class-wp-image-editor-imagick.php and yes, the image_strip_meta filter with either __return_true (metadata is now stripped) or __return_false (metadata preserved) callbacks now works (for JPG’s at least, obviously I still need to figure out PNG’s per point 1.).

My question now for the WP world at large is…

What’s the point of the image_strip_meta filter, when all of the major image metadata types (exif/iptc/xmp) are protected anyways?

Especially seeing as though there is no way to filter the protection in the WP source code (no that I could find). Meaning without the change I did to the core file, there is no way to actually use this filter?

Thanks again!

Is it High/Med/Low priority?
Is it assigned to a Dev as yet?
Is it tagged against a sprint/milestone for a particular release (e.g. QuadMenu 2.1.5 or 2.2)?
Surely you can provide some indication of the status of the issue? How will we know when it’s fixed?

And to be clear, I’m not asking you to edit plugin files, but if you can describe an interim workaround, then more advanced users can manually apply the fix themselves, whilst we wait for the plugin to be patched.

Do your Dev’s know of a fix and can they please share it?

Cart/Checkout pages look bad at the moment with a lot of notification icons broken.

Thanks @sebastopolys, great to hear! This is affecting PRO sites too.

Can you indicate a time frame for a fix?

And can you suggest an interim fix/workaround?

And here’s some screenshots, where you can seen the f06a icon broken & working.

No QuadMenu (f06a displays fine): https://snipboard.io/hGwfzC.jpg
QuadMenu w Dashicons (f06a displays fine): https://snipboard.io/YQGsLD.jpg
QuadMenu w FontAwesome5 (f06a broken/f058 fine): https://snipboard.io/EDo1cN.jpg, https://snipboard.io/kGrcvm.jpg