It looks like you have a theme or plugin that is calling one of the WordPress image-related functions with a bad parameter — using an array instead of a size name (which is a string). This trickles down to the editor_max_image_size() filter, which should receive a size name as its second parameter, but in your case, it’s an array.
You should find the plugin / theme responsible and open a support ticket with them. Just disable each plugin one by one until the problem goes away, and you’ll know which one it is.
Meanwhile, I’ll add some extra error checking in the next version, but that won’t solve your issue – only bypass it.
js.
Hi –
I have the same issue. It is this plugin (NextGEN) that causes it. it just happened when I updated the plugin to the latest one.
Thanks
Same here. Started after latest update. Deactivated all other plugins. Still broke images. Haven’t touched the theme in weeks. I’ve had to deactivate NextGEN+ and now I’m scrambling to make sure my OG data is good. DID NOT NEED THIS ON VERGE OF HOLIDAY.
DID NOT NEED THIS ON VERGE OF HOLIDAY.
@comicref,
In that case, you may want to hold off installing updates until it is more appropriate for you to do so.
@everyone else,
WordPress is passing along incorrect values to its editor_max_image_size() filter. I’ll have to report the issue to the WordPress DEVs. Meanwhile, I’ve already coded a work-around in the next release. Although it’s not a critical issue, it seems to be affecting a few people, so I’ll release the update shortly (in the next hour or so).
js.
Version 6.20.1 is now available.
Sorry for any inconvenience – NGFB Open Graph+ pushes many limits, and the WordPress editor_max_image_size() filter is one of those little known filters that has some “flexible” argument combinations. :-p
js.
Thanks JS – awesome of you to fix this on a holiday. Great customer service. Happy New Year to You!
I totalu agree with findlay, awesome!
