Make fallback date format editable rather than hard coding to US notation

11.2 (not 11 before that) - It's been a while but for the first time dates are now automatically formatted in English i.e. ddmmyyyy when British English is chosen as the default language and the previously uneditable fallback is now in the correct format.

Thanks to whoever got this sorted out.

If what @vortexcentrum says is true, I would like to find the exact commit this was fixed in. I couldn't find any recent changes to the same files the patches here proposed.
Maybe the fix happening in Drupal v11.2 is related to one of the following issues but I might be completely off: 📌 [11.x] php 8.3 follow up for enum in Datetime range formatter Active , 🐛 Date based template_preprocess BC code is incorrect Active , 💬 Support to use the datetime-local element Active

Finding the exact commit that fixed the issue might also help generate a future-compatible patch for still supported earlier versions.

@vensires

I did nothing except install D11.2 and when I went to change the date formats, they were already correct.

It just works. I have no idea how or why but I'm grateful :)

@vensires have a look at https://git.drupalcode.org/project/drupal/-/commit/6810f24aef13523c17d35...

Thank you both for your feedback. I am sure I wasn't clear enough but my question was actually focused on this issue's context.

💬 Support to use the datetime-local element Active was focused on the DateTime Element type as used in a render array. On the other hand, this exact issue was created in order to address . An example code came from Webform's created/completed/changed columns as displayed in https://git.drupalcode.org/project/webform/-/blob/6.3.x/src/WebformSubmissionListBuilder.php?ref_type=heads#L887.

Ah, I see.

No, the fallback format is not editable but at least now it's in the format as the other formats, rather than being isolated when other formats are set correctly.

I've not gone, and have no need to go, beyond the resolution of the frustration of having dates in a format we don't use anywhere on any site.

@vensires - you are more focussed on the tech whereas I'm more focussed on everyday use which, after the debacle that was D8, is slowly beginning to get more recognition. Drupal was, prior to 8, a powerful CMS for non-techies. Starting with 8, it became a much more technical product. 11 (in both the CMS and Core versions) is helping to reclaim the ease-of-use ground that has been lost to Wordpress.