If I create a new date field and simply accept all defaults, I get this error: Dates without hours granularity must not use any timezone handling.

This requirement is not stated on the page. Also, good design principles suggest that accepting all defaults should not cause an error condition.

Comments

karens’s picture

karens commented
Status: Active » Fixed

That makes sense, but I'm not re-writing the current version. I put something like this in to the 5.2 version that I'm working on in HEAD.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)