Held entity path changes if deleted and created with the same UUID

Created on 6 April 2024, 8 months ago
Updated 20 April 2024, 7 months ago

Problem/Motivation

In some scenarios, held content entity could be deleted and re-created with the same UUID, e.g., when created by default content in different environments. If such case, the content entity path changes and the stored one in the holder entity no longer matches. This was added at 🐛 Request path condition does not apply in blocks in holded pages Fixed .

Steps to reproduce

With an existing entity holder populated:

  1. Set a request path condition in any existing block instance to hide on the holder page.
  2. Delete the content held the holder.
  3. Create a new content with the same UUID.

The block will be visible in the holder page.

Proposed resolution

Do not store the canonical path of the held content entity in the holder and user another way to resolve the holder path from the current request/route.

Remaining tasks

Review.

User interface changes

N/A

API changes

Not expected.

Data model changes

The held_entity_path holder property will be removed with this change.

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇪🇸Spain manuel.adan 🌌

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024