major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
defect
major
#25242
Template für In-App-Tabbars erzeugt dopplete Security-Layouts mit undefinierten Keys
The problem is that an attempt was made to treat the legacy case and the in-app configuration as one and the same.
The old template , `templates/tabbar.xml`, assumed that it would be expanded directly within an enclosing tab bar and therefore had to generate its own security layout and tab info.
However, in-app-configured components use standalone layouts for the tabbar, the tab, and its content. Therefore, the conversion of the old template into a typed template cannot be used for in-app configuration:
Instead, the upgrade of the legacy configuration must use a legacy-compatible template. The in-app configuration, on the other hand, must use a streamlined template without additional security layouts.
Code Migration
- The migration from #24085 has been adjusted: templates/tabbar.xml → com.top_logic/legacyTabbar.template.xml instead of com.top_logic/tabbar.template.xml.
Test
- Create a new top-level tab.
- Create a new tab bar with tabs A` and `B within it.
- In the Rights Administration, verify that no additional level with an undefined key is created (see image above).