major
minor
major
minor
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
defect
tl:StructuredElement defines the methods remove() and removeChild(StructuredElement child). However, these methods not only remove an element from the structure tree, but also delete that element from the database at the same time. Therefore, it is not possible to use these methods to move an element to a different location.
These methods, which have an unexpected effect, have been removed.
Code Migration
To ensure semantic consistency during the migration, ...
- se.tDelete() must now be called instead of se.remove().
- se.tDelete() must now be called instead of p.removeChild(se).
Caution: With #26739, remove and add methods with the same names are being reintroduced, so failure to follow the migration instructions will result in an unnoticed change in semantics.
Test
Refactoring, no new test.