Handle deleted fields / content types provided by Drupal PM

Created on 26 July 2015, over 9 years ago
Updated 24 February 2023, almost 2 years ago

Spawning from discussion #2538414-3: How to safely remove fields from create content .

Drupal PM doesn't lock its content type nor does it lock its fields. So it is possible that the admin could delete them from the ui. The purpose of this issue is to discuss how to handle this, and then implement it.

References:
1. node_type_set_defaults - "custom" attribute.

2. Field API - "locked" attribute.

📌 Task
Status

Closed: outdated

Version

3.0

Component

Code

Created by

🇩🇪Germany D34dMan Hamburg

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

Comments & Activities

Not all content is available!

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

  • 🇩🇪Germany D34dMan Hamburg

    All feature request against 7.x would be closed. The focus is now on Drupal 10 release. If you feel this issue is relevant for Drupal 10 version of the project, please feel free to re-open and update the issue. Thanks for the discussion/contribution.

    You may follow 📌 Port PM to Drupal 10 Active to know more about Drupal 10 status.

Production build 0.71.5 2024