[Resolved] Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0!

[Author]

Posts

[Valeriia]

I already reported about it by joining one of the tickets, but now I can't find this ticket and I did not receive any emails to follow up (take a note please). So I have no other choice but to post it again:

After updating to 5.5, every time I submit a toolset form, it gived this error:

Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/c/.../.../public_html/wp-includes/functions.php on line 4773

As I said earlier, I tested it on a site where only 3 plugins are installed: Toolset Types, Toolset Forms and Toolset Views.

It only appears after submitting the form made with Toolset.

Besides, when I went to get the Debug Info for the ticket, I found out the following errors on the Toolset Settings page:

Notice: register_rest_route was called incorrectly. The REST API route definition for toolset/v2/search-posts is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /home/c/.../.../public_html/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for toolset-views/v1/views/(?P\d+).* is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /home/c/.../.../public_html/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for toolset/v2/search-posts is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /home/c/.../.../public_html/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for otgs/installer/v1/push/fetch-subscription is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /home/c/.../.../public_html/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for toolset-dynamic-sources/v1/dynamic-sources is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /home/c/.../.../public_html/wp-includes/functions.php on line 5225

Please look into the issue or redirect me to the solution if it already exists.

Thank you

[Minesh Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)]

Hello. Thank you for contacting the Toolset support.

This isssue is known to us and already fixed with our Dev branch.

Please check the following link for more details.
=> https://toolset.com/errata/wordpress-5-5-update-triggers-php-notices-in-toolset-blocks/

[Valeriia]

Hi,

I updated the plugins and the issue with forms still persists.

You seem to have only fixed if for Blocks as you Errata says. Please check.

[Minesh Supporter Languages: English (English ) Timezone: Asia/Kolkata (GMT+05:30)]

Can you please share problem URL and access details so that I can review your setup.

I have set the next reply to private which means only you and I have access to it.

[Valeriia]

Hi Minesh,

The problem is that all the systems where I have this issue for now are for internal use only. I tried to prepare a copy for you removing the content, however, the issue seems to have disappeared when the backup was restored on a fresh WP installation.

Which made me think that it is related not only to Toolset.

In any case, I'm delaying the update on many of the site where I dread that it can happen as I can't dedicate enough time to solving it at the moment.

When I'm more prepared for that and if the problem still persists, I'll contact you again.

Thanks and have a nice day.

[Mukesh]

Hello, Minesh, has been error been resolved for other Plugins besides Blocks? I'm getting the same warning however I"m not using Blocks.