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

CommentFileSizeAuthor
#3 2116885-mig-entity-3.patch2.45 KBandypost
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

chx’s picture

While 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).

moshe weitzman’s picture

I wrote a destination plugin for config system and pushed to this sandbox.

Entity destinations still outstanding.

andypost’s picture

Issue summary: View changes
FileSize
2.45 KB

Taxonomy 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 table

chx’s picture

I 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.