Feature request: native <!--more--> split support for {post_content} dynamic tag

Description:

WordPress core has a built-in “Read more” feature (the <!--more--> tag, inserted via the block editor’s “More” block) that splits post_content into a teaser and the rest of the content. This is a standard WordPress feature. But Bricks’ {post_content} dynamic tag currently outputs the full content only, with no way to retrieve the split parts.

This makes it hard to build a common pattern natively in Bricks: showing a teaser/excerpt with a “Read more” toggle (e.g. an unfold using <details>/<summary>) using the author’s own chosen split point, rather than an auto-truncated excerpt.

Requested feature:

Add tag variants (naming is just a suggestion) that expose the split:

  • {post_content:before} — content before the <!--more--> tag
  • {post_content:after} — content after the <!--more--> tag

Reference implementation:

Core’s own get_extended() has a known issue: splitting raw post_content on <!--more--> and then running apply_filters('the_content', ...) on each half breaks Gutenberg block markup (orphaned <!-- wp:paragraph --> / </p> fragments), which can cause the “after” half to render empty.

This gist works around that by stripping the block comments manually and re-wrapping paragraphs, avoiding the block parser entirely: split get content before / after read more tag outside loop #php #wordpress · GitHub

Might be a useful reference for a robust core implementation.