Contrib.social

Handle exceptions gracefully when saving node forms

Open on Drupal.org →
Created on 23 October 2016, over 8 years ago
Updated 20 March 2025, 16 days ago

Problem/Motivation

Node forms do not properly handle errors that occur while saving nodes.

Steps to reproduce:

It is possible to hide the node title or other required fields from the form display, but this causes an uncaught exception when saving the node/entity because a title/field actually is required:

Uncaught PHP Exception Drupal\\Core\\Entity\\EntityStorageException: "SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'title' cannot be null

  • Go to Structure -> Content types -> Basic page -> Manage form display
  • Drag Title to Hidden region then click Save
  • Add new content for Basic page
  • You will see "The website encountered an unexpected error. Please try again later."
  • Go to /admin/reports/dblog
  • You will see the Exception in the logs

Proposed resolution

Catch and log errors.

Doing this generically for other entities is handled by #3160721: Handle exceptions gracefully when saving entity forms → . This fixes the most common use case, now, before attempting to fix everywhere in a more standard way ( See #63 🐛 Handle exceptions gracefully when saving node forms Needs work ).

Remaining tasks

None.

User interface changes

A message is shown to the user if the node save fails.

API changes

None.

Data model changes

None.

🐛 Bug report
Status

Needs work

Version

11.0 🔥

Component

node system

Created by

🇨🇳China rcbcool

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

Merge Requests

Comments & Activities

Not all content is available!

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

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024