Issue #501: Timeline field update is incomplete. #502
Closed
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
donquixote
force-pushed
the
issue-501-timeline-field-update-incomplete
branch
from
aea2e0e
to
52e456a
Compare
|
Closing in favor of: #504 |
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.
OPENEUROPA-[Insert ticket number here]
#501 (nothing in Jira, yet)
Description
oe_content_timeline_field_update_8101()misses field storage definitions with no field instances.Change log
oe_content_timeline_field_update_8101().Commands
Notes
The PR attempts to cover two cases:
oe_content_timeline_field_update_8102()has not run yet.oe_content_timeline_field_update_8102()has already run, in the old version.