Make the body field optional and deletable

Created on 20 November 2024, 5 months ago

Problem/Motivation

Spin-off from 📌 Change automatic body field creation to use formatted text field instead of text_with_summary Active to see if we can do the absolute minimum to unblock Drupal CMS. That issue will still be relevant.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

11.0 🔥

Component

node system

Created by

🇬🇧United Kingdom catch

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

Merge Requests

Comments & Activities

  • Issue created by @catch
  • Merge request !10273Move the body field to optional. → (Open) created by catch
  • 🇬🇧United Kingdom catch
  • Pipeline finished with Success
    5 months ago
    Total: 708s
    #345182
  • 🇬🇧United Kingdom catch

    Already deleteable via the API, just not via the UI.

  • 🇨🇭Switzerland berdir Switzerland

    I don't think that changes much in practice so far, if it doesn't have dependencies that might not be fullfilled, still going to be always installed?

    If it's optional, we need to change node_add_body_field() to return early if the field doesn't exist and document that it might return null, which is a bit of an API change?

  • 🇵🇱Poland dmitry.korhov Poland, Warsaw

    If that's for Drupal CMS and not for every installation, why not to use separate `node/config/install` sub-folder that will install the relevant config?

  • 🇬🇧United Kingdom catch

    The idea was to allow recipes to install node module with a text_long body field, but recipes can already do that since they skip installing module config. So yeah this doesn't do anything, we need 📌 Remove node_add_body_field from NodeTypeForm Active instead. Closing as duplicate of the other two isseus.

Production build 0.71.5 2024