Project

General

Profile

Actions

Bug #98333

open

Inconsistent behavior while saving content elements with *required* fields

Added by Julian Mair almost 2 years ago. Updated 11 months ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2022-09-12
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
8.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Summary
If you edit an element with required fields and click the normal save button (in the top headerbar), you can get an alert which says that some are not correctly filled. But with the save and view button, you can bypass the whole check and leave the element broken in place. The Fluid code has not always a check if such a field is not given – we would rely on the backend to prevent this.

I tested it with the "Categorized content" element, the Selected categories field is required. But I think every element with required fields has problems.

Expected behavior
The "Save and view" button gives the same alert message as the normal one – preventing to save the element.

Actual behavior
The "Save and view" button bypasses the expected behavior and saves/shows the element in a new tab.

Tested Typo3 versions
  • v11.5.15
  • v10.4.31
  • v9.5.31
  • (maybe also v12 or older versions than v9 – I didn't test them)

Files

Actions

Also available in: Atom PDF