Trying to migrate some node revisions using the drupal migration system (Drupal 8.8), I am getting the following error:
Call to a member function getTranslation() on null in Drupal\Core\Entity\ContentEntityBase->hasTranslationChanges
It seems that it cannot get the original entity and call the function getTranslation() on it. So, possibly, a check for the existence of the original entity, could avoid this error, although the root of the problem may be that an original entity should always exist and it should never be null (then there might be a problem with the migrated content).
Migrating an updated entity that exists in the destination:
Migrating a new entity that exists in the destination:
1. Check whether the entity loaded by revision id found in the destination database has the same destination entity id.
2. If not, if the destination entity id exists in the destination database, create a new revision.
3. If the destination entity id does not exist in the destination database, ensure that a new entity is created with a new revision.
4. Throw a migrate exception when a translation is not found, but expected.
The current patch ignores the fatal error, but results in a caught error being thrown for some content but not all content being migrated.
- Figure out if the merge request approach works.
- Write kernel tests based on steps to reproduce.
No
TBD
No
Needs work
9.5
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I just ran into this today - patches ok to use on D10.3.5 ? Thanks for any thought
I ran #38 against D10.3.5 and it applied clean.
Ran my misbehaving migrations and it got me caught up to the D7 site I'm working with!
Thank you!