Enhancement
Critical
Major
Detail
Detail
As part of ticket #26183, it was fixed that layouts from the file system are dynamically reloaded after changes. In particular, each time the cache for the file system layouts is accessed, it is checked whether it is still up-to-date. If not, the cache is updated.
When exporting layouts, the new layout is written to the file system first, and then the old, now invalid, layout is removed from the cache. The changes made by overlays are now in the exported layout. Therefore, the cache of the overlays is adjusted or the overlays for this layout are removed.
This sequence causes problems due to the changes in ticket #26183. When removing the old invalid layout, the new layout is already in the file system. Before deleting the old layout, it updates the cache. Since a new layout is in the file system, he reloads it. The overlays have not been removed yet. I.e. when he tries to create the layout, he tries to apply the old overlays to the new layout. But the changes are already in the new layout. This leads to errors about duplicates or not unique component names.
Test
Fit 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, e.g. the help editor. Then export the layout to the file system. Expectation: No error.