@dan @Aaron This beta release still does not fix this bug introduced in beta 5 and 6. Can you please, please, fix?
Refer to this post please