@aremiaskfa Just a quick follow-up on your:
This issue has now been addressed as part of our ongoing GitHub Milestone towards the next stable release.
See the release notes just published here on the forum:
Note however it will not be untill the next release that we will have full field testing given the nature of this change. But I think we do have this sorted now.
Thanks again for the excellent reporting, this has been an issue for a long time now and it just needed a ‘sponsor’ of sorts.
Hope that help, and remember to keep an eye on this when we have our next release (likely 4.5.8-0) as that is when we will have the proof-in-the-pudding as it were.