Try workaround in the post below.
I think the fix is scheduled for 1.37.x - Release #6. And I think this update (1.37.113) is 1.37.x - Release #5, but don’t hold me to that! It gets really confusing sometimes…
Try workaround in the post below.
I think the fix is scheduled for 1.37.x - Release #6. And I think this update (1.37.113) is 1.37.x - Release #5, but don’t hold me to that! It gets really confusing sometimes…