Can someone target this bug on the 5.0.7 client release ? It's already fixed so it'll just make the change log easier to write.
Can someone target this bug on the 5.0.7 client release ? It's already fixed so it'll just make the change log easier to write.