Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We need destination plugins for all the major entity types and for config() system. The entity plugins will all be very similar so they should inherit from a base class.
We also need plugins for some odds and ends like path aliases that are outside of the entity system
Comment | File | Size | Author |
---|---|---|---|
#3 | 2116885-mig-entity-3.patch | 2.45 KB | andypost |
Comments
Comment #1
chx CreditAttribution: chx commentedWhile some entities do have non-entity parts, like the taxonomy hierarchy I talked to timplunkett who confirmed that config entities do not have such dangling ends so the generic entity dst plugin will cover all those (and most of content too).
Comment #2
moshe weitzman CreditAttribution: moshe weitzman commentedI wrote a destination plugin for config system and pushed to this sandbox.
Entity destinations still outstanding.
Comment #3
andypostTaxonomy term import from custom table works (id, name), will try hierarchy later
Patch just clean-ups the plugin code -
import()
should return ID of the entity to properly populate "destid1" field in map tableComment #4
chx CreditAttribution: chx commentedI enrolled this patch into https://drupal.org/node/2150407 where the entity destination plugin in its infancy is submitted for core. I have also added tests to the user role migration test to ensure the idmapping works. Thanks for pointing it out it didn't. We need to make advances of looking at errors from the executable in tests.