enhancement
critical
major
minor
minor
#25907
Layout editor: inconsistent behavior of unfold state, selection and reaction to object creation
#25951
Application tests: CheckLabeledExecutabilityOp fails to assert non-executability of literal ResKey reasons.
#25952
Model Editor: Enum default provider does not work for enum references for which singleton link storage was explicitly selected
#26002
ConfigurationItem-valued properties with format annotations may cause an attempt to create abstract config items when deserializing null values
#26012
Help editor crashes when a user has chosen a language that is not in the supported languages of the application
#26039
Gridcomponent: Display of context menu for new (transient) row object leads to UnsupportedOperationException
#26085
An attribute of type tl.model.search:Expr is not displayed in the form above a TL script editor
#26111
Context menu commands for table rows are erroneously executed on the table model when opening the context menu in the background of the table
#26153
Migration: Replay fails if string values with line breaks are contained in the dataset where a line ends with a semicolon
#26171
A TL script expression entered in a wizard template is reformatted when transferred to the final template
#26223
TL script: Under unfavorable conditions wrong parameter values when evaluating local functions
defect
As part of Ticket #26183, an issue was fixed where layouts from the file system are dynamically reloaded after changes are made. Specifically, every time the cache for file system layouts is accessed, the system checks whether it is still up to date. If not, the cache is updated.
When exporting layouts, the new layout is first written to the file system, and then the old, now invalid, layout is removed from the cache. The changes resulting from overlays are now included in the exported layout. Consequently, the overlay cache is updated, and the overlays for this layout are removed.
This sequence causes problems due to the changes in Ticket #26183. When the old, invalid layout is removed, the new layout is already present in the file system. Before deleting the old layout, the system updates the cache. Since a new layout is present in the file system, it reloads it. The overlays have not yet been removed. This means that when attempting to create the layout, it tries to apply the old overlays to the new layout. However, the changes are already present in the new layout. This results in errors regarding duplicates or ambiguous component names.
Test
Customize a layout that has and uses at least one overlay.
Example: Navigate to Administration > Development and create a new tab next to the other in-app editors, such as the Help Editor. Then export the layout to the file system. Expected result: No error.