TYPO3 Core

Adding a new page either via context menu ("New") in the page tree or via drag and drop of the new-page icon can behave differently.

We had a multi-checkbox field in table pages with a default of "3" (first two boxes checked by default) in ext_tables.sql but no explicit default set in the TCA overides for pages.php. When adding a page via drag-drop the database-row gets created and the default is set via SQL and the checkboxes are set. When adding via context menu, however, only the page-edit window is shown without persisting the new page to the database first - so the default was not set.

Obviously we solved this by setting an explicit default in the TCA as well.

While not being technically an "implementation bug" (obviously the TCA was not configured fully, triggering this), this should still be considered as a "behaviour/user experience bug". A user expects that same actions behave identically - independent of the exact way how the user triggered them - so also a mis-configuration should lead to the same "non-functionality". I did not test it, but I wonder which value the field had if the page was added via the DatanHandler directly from some CommandController, for example. I'd expect the same result as via drag-drop, too, but with this bevahiour inconsistency I'd be highly confused if this is really true. So there are at least three ways (context, drag, direct DataHandler) of adding a new page, where at least two of them behave differently.