Upgrade task to handle %A date format specifier change #24077
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.
Overview
See #24032 (comment)
Alternative to #24070
As @seamuslee001 noted there is some difficulty in accurately detecting use of %A with date_format (as opposed to crmDate) where it's ok and correct to use %A, and in fact the event receipt template currently does use it. But I think I've got it pretty close.
Before
After
If it detects you are using %A in a message template it might look something this:
Otherwise it looks like this (this will be the typical experience):
Technical Details
See #24032 (comment)
Comments