Problem

Sometimes during development fields get removed and the entity that provided gets deleted before the fields are purged via field_purge_batch() leaving field_deleted_* tables in the database that can't be removed.

Proposed resolution

Provide a warning when skipping to tell the administrator that the fields can't be removed because the entity is gone. Hopefully giving them a clue that the entity needs to be re-created for the purge to go through.

CommentFileSizeAuthor
#2 2862308-2.patch1.36 KBjoelpittet
Members fund testing for the Drupal project. Drupal Association Learn more

Comments

joelpittet created an issue. See original summary.

joelpittet’s picture

Status: Active » Needs review
FileSize
1.36 KB

Ideally I'd prefer if they got deleted but this seems to be a safer patch in my head.

joelpittet’s picture

Issue summary: View changes
joelpittet’s picture

Title: Provide more fedback when skipping deleted fields » Provide more feedback when skipping deleted fields during field_purge_batch()

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.