Bug
Tailored CSS code for service reverted to initial state
Issue description
The css file of a GET service was reverted unintentionally to the initial state. The actually served file GET.css_ was still in the original state.
Developer comments
It might be related to [12709, this bug].
A parameter was removed from the service shortly before.
Here is what happend. The AFTER FORM trigger removed unnecessary format files on every change to a service. Given the HTML service S1 had tailored code in GET.css, after a change to the service, the GET.css file was removed since there is a otherwise unproblematic naming collision with the file creating the output for a service that produces CSS code, something which actually never exists.
|
Work sessions3
Start |
2024-02-28T16:37:59
|
End |
2024-02-28T18:00:00
|
Participant |
Robert Cerny
|
Start |
2024-02-29T08:33:48
|
End |
2024-02-29T09:33:59
|
Participant |
Robert Cerny
|
Start |
2024-03-02T06:37:38
|
End |
2024-03-02T07:45:52
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.