Oh sorry, the quote is only for this post. Date format is set correctly on the website.
date format is ‚d.‘ as I only need the first numeric day of the month.
ACF PRO — ACF now automatically escapes unsafe HTML when rendered by the_field or the ACF shortcode. We’ve detected the output of some of your fields will be modified by this change. Learn how to fix. Hide details
datum_beginn () – rendered via acf_shortcode
Warning is only shown in the backend but not in front end
That‘s what I‘ve read and understand. But I don‘t know why I get this warning with info of one special custom field I am using with simply a text/date value … maybe I should create a support ticket?
@hube2 So all shortcodes will broke in the next update, right? I also use the function to enable the new behavior with
add_filter( 'acf/the_field/escape_html_optin', '__return_true' );
But all shortcodes still work as it is only text based or did I misunderstand stgh?
Hi.
I am only using the shortcode [acf field="field_name"] but the ACF message in WP backend says:
field_name () – rendered via acf_shortcode
What should I do or at least what do I have to check?
