wp_make_content_images_responsive() deprecated in version 5.5 of Wordpress about timmy HOT 3 CLOSED

You are right, thank you for the fix!

from timmy.

Hey @thomasansems

I didn’t have this on the radar yet, thanks for reporting! But are you sure that Timmy is causing the deprecation warning and not another plugin, like Advanced Custom Fields? Because Timmy doesn’t call the wp_make_content_images_responsive() function, which would trigger that warning. There’s only this line, which removes the filter:

remove_filter( 'the_content', 'wp_make_content_images_responsive' );

In my understanding, this shouldn’t cause a deprecation warning.

Of course this doesn’t mean that I don’t have to account for the new wp_filter_content_tags() function, which is called instead of wp_make_content_images_responsive(). I hope I can release a fix this week.

from timmy.

I added a fix in 58eeb0c, so that for WordPress 5.5, the correct filter will be removed. The fix is released in the 0.14.5 release.

And I’m going to close this issue. If you still think that Timmy is the reason for your deprecation warnings, then I’ll gladly reopen it and investigate further.

from timmy.