According to this:
This:
And this:
Would it be a safe bet to assume that this issue has been resolved in the “freshly baked” version 5.0.2 ?
I’m kind of reluctant to try…
