CRM-20011 fix loss of data for yyyy-mm custom field #10003
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
eileenmcnaughton
commented
Mar 17, 2017
•
eileenmcnaughton
commented
- CRM-20011: Profile date fields using YYYY-MM or MM YY don't work
|
@eileenmcnaughton confirmed the problem and confirmed that this fixes it, due to the fact this data loss happens should we alter this and put it against the RC? |
|
@seamuslee001 this isn't a new regression so I think it can wait until next month. I'll merge it based on your testing though |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.