The "display_id" entity type does not exist.

Created on 27 June 2023, over 1 year ago

Problem/Motivation

When I have fieldable_path enabled. If I edit a taxonomy term or create a new one. (I don't have a fieldable_path field attached to any taxonomy. I get this error:

Drupal\Core\Entity\EntityStorageException: The "display_id" entity type does not exist. in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 822 of /var/www/html/web/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).

Steps to reproduce

I am not sure this is reproducible on a clean install. But the steps above reproduce it on my instance and I can narrow it down to this module using xDebug and enabling or disabling this module and or it's ability to save.

Proposed resolution

Patch coming

Remaining tasks

none

User interface changes

none

API changes

none

Data model changes

none

πŸ› Bug report
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States dobe

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

Merge Requests

Comments & Activities

  • Issue created by @dobe
  • Status changed to Needs review over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States dobe

    Attached is a patch, basically:

    $params are coming in as an array of [taxonomy_term: myid, view_id: iForget, display_id: page_1]

    $param_keys = array_keys($params);
    $entity_type = array_pop($param_keys);

    Then we are sending display_id as a $entity_type to SqlContentEntityStorage->save() where it throws a white screen of fun.

    The proposed patch checks if it is a valid $entity_type before continuing.

  • Status changed to RTBC about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States el1_1el

    I had this issue after an update from core 9.5.8 to 9.5.11 as well. I rerolled the diff patch to remove the empty .DS_Store differ binary.

  • First commit to issue fork.
  • Merge request !2Fix #3370771 β†’ (Open) created by vensires
  • πŸ‡¬πŸ‡·Greece vensires

    The MR doesn't provide any changes from the patch in #3. But it helps validate that it still applies in 8.x-1.x.

Production build 0.71.5 2024