Problem/Motivation

I have term conditions used in a context. When I upgrade from 2.0.1 to 2.0.3, all those term_conditions are now blank, thus still breaking backward compatibility. The only way to recover is to roll back.

Steps to reproduce

Create a context with term_condition 2.0.1, then upgrade to 2.0.3, condition in context is now blank.

Proposed resolution

The supplied patch loads terms by tid if uuid is not present, preserving backwards compatibility

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#5 backwards-compatibility-3384350-5.patch2.14 KBkwfinken
#4 backwards-compatibility-3384350-3.patch2.14 KBkwfinken
#2 3384350-backwards-compatibility-1.patch2.17 KBkwfinken

Comments

kwfinken created an issue. See original summary.

kwfinken’s picture

kwfinken commented
StatusFileSize
new 3384350-backwards-compatibility-1.patch2.17 KB
kwfinken’s picture

kwfinken commented
Status: Active » Needs review
kwfinken’s picture

kwfinken commented
StatusFileSize
new backwards-compatibility-3384350-3.patch2.14 KB

oops. 1st patch still contained dpm/debug info

try this one.

kwfinken’s picture

kwfinken commented
StatusFileSize
new backwards-compatibility-3384350-5.patch2.14 KB

Not my day, Try 3

kwfinken’s picture

kwfinken commented
astonvictor’s picture

astonvictor commented
Status: Needs review » Closed (outdated)

yeah, the issue was that an array of term ids was replaced with an array of term uuids.
as I can see, we already have an update hook to migrate data. It was resolved in the #3363916: 2.0.2 breaks backward compatibility issue
make sure that you executed database updates after updating the module version. e.g. via drush updb

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.