Groundspeak Portal

Recently we have been having some dating problems. No, these are not relationships but when entering new or editing waymarks the date variable errors (enter date in mm/dd/yyyy format). Whatever we put in it won't accept it. What are we doing wrong, it didn't do it before and is anyone else suffering?

Dragontree:

Recently we have been having some dating problems. No, these are not relationships but when entering new or editing waymarks the date variable errors (enter date in mm/dd/yyyy format). Whatever we put in it won't accept it. What are we doing wrong, it didn't do it before and is anyone else suffering?

This is being fixed.  The format to enter will be m/d/yyyy (no leading zeros).   It will accept that format currently however currently on save it reformats it back to mm/dd/yyyy so if you do an edit you will have to strip the leading zeros.  This bug is being worked on and should be fixed soon.

At the moment, the simple date field is not accepting dates for years earlier than 1000.

This is a problem reported to me by someone trying to submit a waymark to the Grave of a Famous Person category for an individual born in 699.

The date has now been fixed to accept m/d/yyyy down to year 1000 and it will retain its format.  Do not put in leading zeros in month or day.  Groundspeak is aware of 1000 year limit, it used to be 1600 or something like that.

Are there any workarounds for getting in a date with a three digit year?

cache_test_dummies:

Are there any workarounds for getting in a date with a three digit year?

Have you considered Islamic or Hebrew? Wikipedia on Calendars

Or of course you could try Star Date conversion.

BQ

Good thinking!

Ok, I've changed the variable types on all the date related fields in all my categories from 'simple date' to 'Islamic/Hebrew/Star Date'.

Dates must now be entered in the following format:



Remember that because of a bug, you have to drop any leading characters.

Thanks, BQ!