• Resolved Metalgurke

    (@metalgurke)


    Hello ACF team,
    Since the ACF-Pro update to version 6.2.5 I have received the following messages:

    “ACF PRO — 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…

    text (journal_page_builder_0_text) – rendered via the_sub_field

    code (journal_page_builder_11_code) – rendered via the_sub_field”

    So far so good.
    I have already followed your advice
    see the link
    https://www.advancedcustomfields.com/resources/html-escaping/#customization

    After that didn’t work, I replaced all functions in my template theme with “the_fiel(…)” with “echo get_field(…)” and “the_sub_field(…)” with “echo get_sub_field(.. .)” replaced. However, I still get the same warning messages (see above).
    As far as I know, an ACF shortcode ([acf …]) does not exist on the website.
    Deleting the unsafe HTML tags etc. is also not an option.

    Maybe I missed something or did something wrong?

    Thank you and best regards

Viewing 2 replies - 1 through 2 (of 2 total)
  • CDHeumann

    (@cdheumann)

    I have the same problem.

    I have adjusted the marked field, but the test does not seem correct to me. I have many “text” fields. And only one was noted, even though I have at least 5 that are just in a different field group, but otherwise identical. On other websites, no field is noticed after the update. I am very skeptical. I output almost all fields in my theme with “the(_sub)_field”.

    Hi there!

    ACF Support Team here. This forum is generally used by ACF users to help each other out.

    However, we would love to continue investigating and troubleshooting these issues, please can you create a ticket using our ?support form and we can look into it further.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘ACF-Pro update to version 6.2.5 warning message’ is closed to new replies.