#28091 Transaction monitor: Reason if a revert is not possible

Enhancement

Major

#28073

Optimierter Attributzugriff auf historische Stände

#28101

Enlarge scroll bar

Detail

#28040

Redesign of the JSP pages of the maintenance page in the technical administration

#28077

CoreTheme: Correction of icons in tree structures

#28100

Insert logout button in the sidebar

#28137

Alias %HOST% also when starting from the development environment

#28138

Aliases in test scripts

Bugfix

Detail

#28086

Missing statements in SQL Monitor

#28091

Transaction monitor: Reason if a revert is not possible

#28097

TLScript: Copy(): Error if target type attribute not defined.

#28103

TLDoclet must not generate invalid XML for {@code ...} sections must not generate invalid XML

#28113

Setting components do not listen to updates of the edit mode channel

#28120

Layout editor: Tile context menu command is not offered

#28129

Transient objects: Incorrect/insufficient value conversion when setting values

#28141

Rendering safety: Subsequent errors after error handling of errors in template variables

#28142

Error when inlining layouts: ThreadContextManager not started

Bugfix (User-visible)

Detail

#28091

Transaction monitor: Reason if a revert is not possible

TransactionMonitor

Currently, the transaction monitor does not provide any explanation if the revert of a transaction is not possible. The problem cannot be understood either from the message or from the log.

Test

Revert of a revision that cannot be reverted.
The database error should also be displayed in the message.