- 🇺🇸United States ryankavalsky
Is there a solution for this issue, yet? I seem to have run into it myself with Drupal 9.5.11 and daterange_compact 2.0.1.
- 🇺🇸United States ryankavalsky
Never mind - I've learned that the compact date formats I had set up must not have transferred when upgrading Drupal from 8 to 9, or perhaps when upgrading this module. After re-creating my default compact format, everything worked again.
- 🇮🇳India Shreya_98
Shreya_th → made their first commit to this issue’s fork.
- Status changed to Needs work
11 months ago 7:11am 8 December 2023 - Status changed to Needs review
11 months ago 7:45am 8 December 2023 -
erik.erskine →
committed 39bfdc7e on 2.1.x
Handle missing config entity gracefully #3248081
-
erik.erskine →
committed 39bfdc7e on 2.1.x
- Status changed to Fixed
8 months ago 7:33am 2 April 2024 - 🇸🇪Sweden erik.erskine
This error happens when the formatter is passed a non-existent config entity ID, as described in #8.
I looked at how the core date formatter handles this situation. If the format doesn't exist or is invalid, a
fallbackdate format is used. This `fallback` format is included as part of the module's default configuration and locked.So it would make sense for this module to behave the same way. Added to 2.1.0.
Automatically closed - issue fixed for 2 weeks with no activity.