Yo,
I checked it out and it seems to already have been fixed in our internal versions, so it should be fine for post-2.7.2
Thanks for the headsup tho
Arthur
I checked it out and it seems to already have been fixed in our internal versions, so it should be fine for post-2.7.2
Thanks for the headsup tho
Arthur