Closed ttstauss closed 1 year ago
This is the default ACF behavior. In normal cases you need to run wpautop (https://developer.wordpress.org/reference/functions/wpautop/) function over the ACF field, should you need it. The handling of the output is left on us. Which is fair and right.
Hi @twentyfortysix, thanks for the information.
That's interesting. So even though the WYSIWYG
editor lets a user pick Paragraph
and even gives you a link at the bottom left to highlight the paragraph your cursor is currently in, the data returned is stripped of the very <P>
elements that the user dictated they wanted?
I understand what you're saying about it being fair and right, but it's a bit misleading.
I'll see if I can figure out how to use wpauto
.
@ttstauss obviously I'm late to the party here, but I'm not sure this issue is in the right repo. WPGraphQL for ACF doesn't output an attributesJSON
field?
Perhaps you meant this issue for this repo https://github.com/pristas-peter/wp-graphql-gutenberg-acf?
I'm going to close this issue as I don't believe it's intended for this repo, but if you feel it is still a valid issue, please open a new issue, reference this one, and provide clear steps to reproduce, including a JSON export of the ACF Field Group in question.
Hello,
When I make the following request:
I get the following response:
The
attributesJSON
content (i.e.accordion_0_content
) results don't include the<p>
/</p>
tags (other tags like<em>
or<strong>
do come through). This is true for both theWYSIWYG
andText Area
field types (set in ACF).Is there any way to include the
<p>
/</p>
tags?