You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These unexpected white sections were associated with empty paragraphs that had been generated by wpautop()
run against the content generated gutenberg_render_block_core_template_part() ...
Actually, my latest version, fizzie_lazy_render_block_core_template_part( ).
I need to check whether or not it's any of my own plugins that are causing this.
The text was updated successfully, but these errors were encountered:
I need to check whether or not it's any of my own plugins that are causing this.
It wasn't. I tested with only two plugins active. Gutenberg 9.3 and oik-bwtrace.
I used oik-bwtrace to view the $content before and after calling wpautop().
Looking at the code in the call stack, there's a comment in do_blocks() associated with code that removes wpautop() from the_content filtering.
// If there are blocks in this content, we shouldn't run wpautop() on it later.
My conclusion is that either wpautop() should not be called, or the comment is wrong.
Given that not calling wpautop() resolves the issue, I think we should obey the comment.
Note: the logic to remove and restore the wpautop() filter hook relies on the fact that wpautop() is the last filter function attached for a particular priority.
If it's not, it becomes the last.
This could affect the results of the filtering.
With the
home-query.html
template part I noticed a number of white sections which were associated with empty paragraphs.Explanation
wpautop()
run against the content generated
gutenberg_render_block_core_template_part()
...Actually, my latest version,
fizzie_lazy_render_block_core_template_part( )
.I need to check whether or not it's any of my own plugins that are causing this.
The text was updated successfully, but these errors were encountered: