Section fieldtype deprecation has no replacement for a fieldless, always-visible editor note #1475

Activity

1. jackmcdade commented on Jul 23, 2026

   

   jackmcdade

   on Jul 23, 2026 via email

   Member

   More actions

   What about the HTML fieldtype? That’s a display only field you can do basically anything with. On Jul 23, 2026, at 7:23 AM, ChrisLCarrBF ***@***.***> wrote:ChrisLCarrBF created an issue (statamic/ideas#1475) Summary The Section fieldtype is deprecated in v6 and scheduled for removal in v7. The upgrade guide recommends using blueprint-builder sections instead. That covers structural grouping, but not the display-only "note to the editor" use case, and none of the existing alternatives reproduce it. The use case A display-only, always-visible line of instructional text placed inside a Replicator/Bard set — with no associated data field. This is used heavily by page builders (e.g. the Peak starter kit) to explain what a given set does, especially for sets that render content automatically and have few or no editable fields. Steps to reproduce the gap In a Replicator or Bard set, add a Section field with instructions text (e.g. "This displays all items in the FAQ collection"). Try to reproduce the same always-visible note using only non-deprecated features. Expected A supported way to show persistent instructional text inside a set without attaching it to a data field. Actual No non-deprecated feature does this: Blueprint-builder sections render as top-level tabs and don't apply inside a set. Set-level instructions render only as a hover ⓘ tooltip — not always visible. Field-level instructions are always visible but require a host field, which these sets don't have. Suggested resolution Provide at least one of: A first-party display-only fieldtype that isn't slated for removal, or An "always visible" mode for set-level instructions, or An always-visible instructional text block on sections that also works inside sets. At minimum, it'd help to keep the Section fieldtype until an equivalent exists, so the removal in v7 doesn't drop functionality with no migration path. Environment Statamic: 6.x Peak starter kit (page builder pattern) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
2. ChrisLCarrBF commented on Jul 23, 2026

   

   ChrisLCarrBF

   on Jul 23, 2026

   Author

   More actions

   Ah, that's not a bad idea! Even though the HTML fieldtype then displays a mandatory Display Label, I can make use of this.
   Perhaps then the documentation can be updated: https://statamic.dev/getting-started/upgrade-guide/5-to-6#section-fieldtype-has-been-deprecated
3. duncanmcclean commented on Jul 23, 2026

   

   duncanmcclean

   on Jul 23, 2026

   Member

   More actions

   If you don't want the label, you can turn it off to the right of thr input in the field's settings.

   🎉React with 🎉1Reacted by ChrisLCarrBF
4. ChrisLCarrBF commented on Jul 23, 2026

   

   ChrisLCarrBF

   on Jul 23, 2026

   Author

   More actions

   If you don't want the label, you can turn it off to the right of thr input in the field's settings.

   Ah, fantastic. Thanks!