Change
Frozen topic modification should cause exception
Issue description
Currently modifying a frozen topic constitues only a warning, which is logged in the log files, but otherwise is not accesible to the administrator. This causes long error hunts which could be avoided if there is a clearer signal that something went wrong. In the case at hand imports were successfully finished, but only a fragment of the data was updated, since frozen topics where modified – or not modified. When there is large import data sets, this goes unnoticed until later.
Developer comments
This causes a DeveloperException now.
This could be changed to a FrozenException later. But this would go unnoticed, since the admin does not receive any information after that.
|
Work sessions2
Start |
2023-09-19T08:00:39
|
End |
2023-09-19T08:13:00
|
Participant |
Robert Cerny
|
Start |
2023-09-20T08:00:00
|
End |
2023-09-20T09:30:00
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.