Prevent publishing when block values do not #validate

Created on 19 August 2025, 10 days ago

Overview

In testing πŸ“Œ ComponentSourceInterface::submitConfigurationForm and validateConfigurationForm are never called Active it was discovered that we could publish content that included a webform block, even if the entity reference field referenced a non-existent block. This was discovered with webform, but could occur on any entity reference that requires that value to reference an entity that exists.
If we publish content with this invalid block field value, then the Page will crash on render.

In standard forms, validation prevents this from happening:

We know that #validation callbacks run on value changes as of πŸ“Œ ComponentSourceInterface::submitConfigurationForm and validateConfigurationForm are never called Active , but it seems like (please verify) they do not prevent publishing from occurring. If this isn't the reason, lets be sure to update the issue summary to remove that theory.

Proposed resolution

User interface changes

πŸ“Œ Task
Status

Active

Version

1.0

Component

… to be triaged

Created by

πŸ‡ΊπŸ‡ΈUnited States bnjmnm Ann Arbor, MI

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

Comments & Activities

Production build 0.71.5 2024