Support

Account

Register Login

Home › Forums › General Issues › Warnings with new 6.2.5 pro version

Solved

Warnings with new 6.2.5 pro version

  • Why am I seeing these warnings all of the sudden?

    ACF warning

    At first I thought it’s because I used ampersand instead of " " so i changed it – but the warning is still there

  • It likely means that there is something in your field that would be removed by wp_kses().

    See this document that explains what it’s doing and how you can modify how it does it https://www.advancedcustomfields.com/resources/html-escaping/

    This is just a guess on my part, if you want a definitive answer you should open a ticket on your account to ask the developer.

  • Hey @zzaaxx,

    We’ve published some sample code as a gist which will let you debug this easier on the frontend: https://gist.github.com/lgladdy/e4cb5816c835b11dd2d8f482b16fdcb6

    It will output a backtrace where the error is happening, so only useful for local development instances.

    Could you let us know what the raw value is for the second row in that repeater? It is likely to be some other character which has become a safe htmlentity.

  • Thanks! I used the gist from above and yes, ampersands are causing the warnings. What I don’t get is the warning is still the, but I can live with it, I guess.

  • Could you let us know what the raw value is for the second row in that repeater? It is likely to be some other character which has become a safe htmlentity.

    Is this it?

    #2  WP_Hook->do_action(Array ([0] => the_sub_field,[1] => title,[2] => Array ([ID] => 0,[key] => field_646373c60350d,[label] => Title,[name] => steps_0_title,[aria-label] => ,[prefix] => acf,[type] => text,[value] => Discovery & planning,[menu_order] => 0,[instructions] => ,[required] => 0,[id] => ,[class] => ,[conditional_logic] => 0,[parent] => field_646373b60350c,[wrapper] => Array ([width] => ,[class] => ,[id] => ),[default_value] => ,[maxlength] => ,[placeholder] => ,[prepend] => ,[append] => ,[parent_repeater] => field_646373b60350c,[_name] => title,[_valid] => 1),[3] => )) called at [/Users/dusan/Local Sites/holycode2/app/public/wp-includes/plugin.php:517]

  • I sometimes use ACF options page to store Google Analytics code, output with the_field(). Is there a way to bypass the additional check?

  • Use get_field() instead

  • That works – thank you John, appreciated

  • This reply has been marked as private.
  • This reply has been marked as private.

  • Hello Igglady,

    Where do we have to put that code?

    I have put that code in functions.php archive but I don’t see more information than this, in the backend:

    ACF — ACF will soon escape unsafe HTML that is rendered by the_field(). We’ve detected the output of some of your fields will be modified by this change. Learn how to fix. Hide details

    campo (campo) – rendered via the_field

    I changed the_field code for this: echo wp_kses_post( get_field(‘oferta-descripcion’) );
    but I get the same error, does not dissapear.

    I may have put that code, the_field, somewhere else, but I don’t know where.

    Thank you!

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.