We thought we fixed that bug. might just be some left over JS validation. we'll get into it.