I know it wasn’t mentioned in the changelog, but tried my luck anyways, and I can report that this issue wasn’t fixed in 3.8.3.
Could we maybe have a second look at this problem?
I know it wasn’t mentioned in the changelog, but tried my luck anyways, and I can report that this issue wasn’t fixed in 3.8.3.
Could we maybe have a second look at this problem?