WAIT: Dynamic tag fails if the fallback is {post_content}

Bugs
1

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.

A fallback of {post_content} causes the dynamic tag to fail and for the fallback post content to be rendered. This happens whether the tag requires the fallback or not, and whether the fallback of {post_content} is rendered with :plain or not. Other tags such as post_title and post_date behave as intended.

This is an example of the output on the front end:

{acf_custom_field @fallback: ‘The is the post content … ‘}

And this is the tag in the editor:

{acf_custom_field @fallback: '{post_title}'}

This setup is required in my case because of a need to set the default query type of a component to ‘Repeater’, but to accommodate a fallback to cases when the component is just looping over a Post Object.

2

Hey @robbiedawson,

I can’t replicate it. What is your post content?

Matej

3

The problem does not appear if there is a single block in Gutenberg post content, but once I added a second heading block the problem appeared. In my test a heading block was first and a paragraph second, but it might just be the presence of multiple blocks of any type.

4

Hi @robbiedawson,

Thank you. I was able to replicate it when I added the heading element as a second block, then I saw the issue. But with only a paragraph element, it works.

I have created a local bug report, and we will update this topic once we release a fix.

Thank you so much,
Matej