Fix for date input problems!.

Have you tried this with inline translations disabled?

I tried a lot of permutations and deleting the keys was the only solution that worked.

To ensure you get it correct you even have to clear your browsers cache if you still have problems (probably browser dependent, - works fine in Chrome 10)

Private User and Private User

These "<span statements" will appear on some places only if:
A) Inline translation is enabled and
B) these translated phrases are not locked.

Have you tested both?

P.S. The Date Format Localization seems not working at all Today.
I already Yesterday changed my default input format to DD MM YYYY but when I tried to input new date to some profile (textual view - Basics tab) then 18 03 2011 gave "Invalid Date" message - I was able to input only
03 18 2011 as in US (MM DD YYYY) format.

Deleted for Norwegian but as it isn't possible to lock phrases without a translation there is a risk that someone will translate it again.
(The option of locking a non-translated phrase disappeared with the most recent TR8N version; reported as bug.....).

....and any comment attached to the phrase also goes "invisible" (e.g. Don't translate this phrase).

Not quite invisible, comments flashes up in some fractions of a second before it goes away.

Please not that the safest way to enter a date is spelling the month. "20. mar 2011", - even "20/3 2011" woks.

Again: deleting the tree keys seem to at least activate the date parser until Geni comes with a fix of you are not using US English

When you have entered a date hit return, tab or click outside the field to activate the parser. A gray text to the left of "❌ Ca". gives you feedback if the parsed date or an error message.

If you don't get something try to delete those tree keys.