- Issue created by @hoporr
- Status changed to Closed: won't fix
12 months ago 2:25pm 16 November 2023 I was able to resolve this with an update hook like this:
$type_manager = \Drupal::entityTypeManager(); $type_manager->clearCachedDefinitions(); $entity_type = $type_manager->getDefinition('privatemsg_message'); \Drupal::entityDefinitionUpdateManager()->installEntityType($entity_type); $type_manager = \Drupal::entityTypeManager(); $type_manager->clearCachedDefinitions(); $entity_type = $type_manager->getDefinition('privatemsg_thread'); \Drupal::entityDefinitionUpdateManager()->installEntityType($entity_type);
It would be intersting to know why this error happened (during migration), but it is gone now so from my end please close this again.
- ivnish Kazakhstan
hi hoporr!
There is no migration from D7 to D9+ now. How did you do it?
Yes, that's a good question.
I checked my migration logs, and there is no private mssage migration.
However, I was running the V1 branch of privatemsg, and somehow all the data was there. Potentially, I had just copied the DB tables over back then, and it just worked with V1 ?
When I upgraded for D10, this switched over to the V2 branch, and it did not work anymore. I noticed that the DB structure was different as well.
So I reverted back to V1, and I get the message.