API Default to "yyyy-MM-dd" for date format #2841
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The motivation for this was to avoid using "MMM" in particular, since it causes inconsistencies in month
names between jQuery UI and Zend_Locale_Format.
One example of that was "mar." (jQuery UI( vs. "mars" (Zend_Locale) as a danish short month name.
This means if you set a default locale of
de_DE
for example,the date format will still be
yyyy-MM-dd
(rather thandd.MM.yyyy
).You still get that one as a suggestion in the member profile,
and can set it as a global default through
i18n.date_format
config API,its just not auto detected any longer. This also makes
i18n::get_date_format()
obsolete, since we can now simply use the Config API without any dynamic calls.
I've implemented the same changes for consistency in
time_format
as well.Fixes silverstripe/silverstripe-cms#544