Use rendered entity as content source

Created on 29 May 2025, 3 months ago

For content with paragraphs and different field types, would it be easier to use the rendered entity instead of field values?

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States mortona2k Seattle

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @mortona2k
  • Merge request !16Master β†’ (Open) created by mortona2k
  • πŸ‡ΊπŸ‡ΈUnited States mortona2k Seattle

    mortona2k β†’ changed the visibility of the branch master to hidden.

  • πŸ‡ΊπŸ‡ΈUnited States mortona2k Seattle

    I added a patch for altering the content before extracting tags.

    In a custom hook, I rendered the entity and stripped tags to get the full text including paragraphs and layout builder content.

    This works for now, but a better way to go would be to create a new plugin for the field widget. It's tricky because the javascript loads values from the form to pass to the controller.

    Some additional logic might be needed, like a way to ignore certain fields or values that might be more like labels and not relevant for content tags.

Production build 0.71.5 2024