This has been fixed for a long time, it was fixed in 4.1.x
Unfortunately, it did reappear in a slightly different way in 5.0.3, but it is already fixed internally and we hope to have that version out very soon
It is an avoidable bug however read more in the Known issues of 5.0.3 at the bottom of the first post in the thread.
1 Like