Impossible to install without body field

Created on 12 March 2025, 23 days ago

Problem/Motivation

On my website, I don't have a field with the system name "body." When I try to activate the module, I get the following error:

Unable to install Push Framework due to unmet dependencies: core.entity_view_display.node.page.push_framework (field.field.node.page.body)

Proposed resolution

Do not add the "body" field by default in the view mode and remove the dependencies in the configuration file core.entity_view_display.node.page.push_framework ?

🐛 Bug report
Status

Active

Version

2.3

Component

Code

Created by

🇫🇷France rmpereira

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

Comments & Activities

  • Issue created by @rmpereira
  • 🇫🇷France rmpereira

    I think it could also be a problem if we don't have a "page" content type.

  • 🇩🇪Germany jurgenhaas Gottmadingen

    I was actually wondering, when we implemented this a few years ago, whether this issue would ever come up. Now, it actually happened, but I'm not sure if we can address this. The whole notification template system is built around the assumption that a notification has a subject and a body. That's what most channels also require, the most popular example being an email notification.

    I don't think we have a way to provide a generic solution that wouldn't even have that common ground. Unless, there is something I'm missing, it looks like this module is not for sites that are restricted that much and would allow for a body field.

Production build 0.71.5 2024