Standardize basic content entity form logic in ContentEntityForm

Created on 13 December 2016, almost 9 years ago

Updated 5 September 2025, about 1 month ago

Problem/Motivation

As a followup of https://www.drupal.org/node/2669802 → . We noticed that most forms extending ContentEntityForm implement the things below (and not all in the same way). It might be good to standardize this a bit more in ContentEntityForm. This means less logic for people implementing it.

Form():

Standardize form title: $form['#title']

Save():

Saving the entity
Standardize message for new/changed entities

Maybe some more?

Proposed resolution

Discuss what to standardize and how.
Actually change the code.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

entity system

Created by

🇳🇱Netherlands seanB Netherlands

Live updates comments and jobs are added and updated live.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 month ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024