I have a bunch of events in a non-drupal site. Each event is associated with a facility. On the new drupal site, each facility will be represented by a different domain, using the domain access module.
It would be helpful if the domain ownership could be exposed to the content set. I almost think that it could be done already, as the domain-ID can be seen in Views, so perhaps I've missed it.
Hmm, if I have nodes for the facilities. And if the nodes contain the facilityID from the original data, can I modify the orig_event view to include the domain-ID from those facility nodes? Nope, that still won't help because the domain-ID is not being exposed in the list of destination fields.
Comment | File | Size | Author |
---|---|---|---|
#7 | migrate_extras-domain_access-710742-7.patch | 1.15 KB | joshuajabbour |
#5 | domainaccess.inc_.patch | 943 bytes | mrkschan |
Comments
Comment #1
frankcarey CreditAttribution: frankcarey commentedSo to clarify, you need a field to import to (you can already get your domain-ID as an input field from views). If your domain-ID field is a CCK field, then you should be able to import it fine. If it makes it's own field, but not through CCK, then you need to write a hook to add the field called MYMODULE_migrate_fields(), if you need to massage the data, then you need to write a hook MYMODULE_migrate_prepare_node() so that the field will be saved when you are done. Please submit it back if you get it to work.
Comment #2
dusedd CreditAttribution: dusedd commentedany luck resolving this issue...if so, please post back your solution
Comment #3
mikeryanV1 is no longer supported, bumping request to V2.
Comment #4
bstoppel CreditAttribution: bstoppel commentedI'm working upgrading my sites from Drupal 6 to Drupal 7. Both use Domain Access. I'd like to work on a generic solution to this problem using the Migrate module as the base for the solution. I'm having a little bit of trouble understanding how the destination handlers work. Here is what I have grokked about the process so far:
I am assuming that I need to build a destination handler with prepare and fields methods and probably a few more. But I am not sure where to start. I've looked through the migrate_extras handlers to try to clue in on a solution, but haven't been able to grok an approach. It doesn't seem like any of the migrate examples are grabbing extra data from the source database to migrate to the destination database. I could be wrong though. Can someone point me in the right direction and/or to similar code that I can gain insights?
Thanks.
Comment #5
mrkschan CreditAttribution: mrkschan commentedFind attached a simple patch that makes migrate works with domain access :)
Tested with ...
Drupal 7.8
migrate 7.x-2.2
migrate_extras 7.x-2.2
domain 7.x-2.13
Comment #6
mikeryanPlease roll an actual patch file.
Thanks.
Comment #7
joshuajabbour CreditAttribution: joshuajabbour commentedHere's a proper patch. Haven't tested it yet...
Comment #8
agentrickardI added Migrate support to DA 7.x.-3.x-dev a few weeks ago. See #1702856: Fix Destination Handler registration