Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • December 12, 2020 at 11:04 pm #1266806
    doug1234

    Hi Friends,
    Does anyone have a fix for the following error? (seeing after a WordPress 5.6 upgrade):

    “Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in C:\inetpub\wwwroot\tsp\wp-includes\functions.php on line 4859”

    Thank you.

    December 14, 2020 at 6:23 am #1267028
    Rikard

    Hey doug1234,

    Please send us a temporary WordPress admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.

    Best regards,
    Rikard

    December 14, 2020 at 3:40 pm #1267191
    doug1234
    This reply has been marked as private.
    December 15, 2020 at 4:11 pm #1267502
    Yigit

    Hey,

    Thanks for contacting us!

    Due to our policy, we only access to sites that are publicly accessible.

    Please make sure that you are using the latest version of Enfold which is currently 4.7.6.4 – https://kriesi.at/documentation/enfold/theme-update/. If that does not help, please try to clear cache.
    In our code, we use “wp_make_content_images_responsive” in WP versions older than 5.5 and “wp_filter_content_tags” on versions 5.5 and newer so you should not get such warning :)

    Cheers!
    Yigit

    December 18, 2020 at 9:34 pm #1268490
    doug1234

    Hi Yigit,

    Thank you for your suggestions.

    Unfortunately, I am running the latest enfold – 4.7.6.4

    I did clear my cache and tried two different browsers. The same error appears in each.

    Do you have any other suggestions?

    Thank you.

    December 19, 2020 at 5:30 pm #1268649
    Nikko

    Hi doug1234,

    A temporary solution is to disable Responsive Images in Enfold > Performance > Responsive Images And Lazy Loading.
    However, if your Enfold version is 4.7.6.2 and up it should be fixed as Yigit mentioned and the issue most likely is caused by caching.

    Best regards,
    Nikko

    January 3, 2021 at 4:38 pm #1270053
    doug1234

    Hi Nikko & Yigit,

    Happy new year!

    Thank you for your help. I did take a peak at the code that the error referred to:

    if ( WP_DEBUG && apply_filters( 'deprecated_function_trigger_error', true ) ) {

    I then changed WP_Debug to false in web-config.php and the errors went away. All this to say, it seems that the deprecated code is being purposely called. I am confident that I have cleared the browser cache and I am not running an old version of the theme.

    I’d also like to share:
    “Private Content (link to your website, login credentials, FTP credentials, etc – only visible for moderators)” is the title of the box that allowed me to enter my private URL. The title suggests that this is acceptable.

    Thanks again,

    Doug.

    January 5, 2021 at 2:29 am #1270284
    Ismael

    Hi,

    Thank you for the update.

    By setting WP_DEBUG to false, you are disabling the debugging mode, which also prevents warnings or errors from displaying in the frontend. This is fine because the debugging info that you posted above is merely a warning and should not cause any critical errors in the site.

    Best regards,
    Ismael

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.