12-19-2019, 04:27 AM
I took at look and it seems that these fixes were merged into the current 4.7 branch. I just tested and am still experiencing this error. @listy can you verify if it is still a problem on your end (just to make sure I have it in place correctly)?