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.I imported a lot of nodes via PHP Script module but thought Server issues (aborting/downtime) i have now few differences with nodes and fields. See Screenshots.
If i use D2D D7 to D7 Migrate it migrate only the correct assigned nodes and fields via id?
The issue is:
I have nodes qty: 2,990,574
Field Quantity: 2,990,219
The both values needs matching because all nodes use this simple text field.
My idea is to use D2D Migrate to Migrate only all which are correct assigned with IDs Drupal Database.
| Comment | File | Size | Author |
|---|---|---|---|
| Bildschirmfoto 2014-12-16 um 08.24.26.png | 294.67 KB | alexander.sibert | |
| Bildschirmfoto 2014-12-16 um 08.23.52.png | 338.01 KB | alexander.sibert |
Comments
Comment #1
mikeryanSorry, it's not exactly clear to me what you're asking. You're saying you imported nodes into D7 by some means other than migrate_d2d (not sure what "PHP Script module" means, I know of no module named "PHP Script") and you ended up with 355 of the nodes missing this field_geoname_id value, correct? I assume you have verified that it is populated for every single node on the source side. Are you asking if you could use migrate_d2d to reimport only those 355 nodes, and fill in the missing field? If all you're trying to do is fill in those missing fields, it may actually be simpler to skip migrate_d2d and use Migrate directly, using the system-of-record feature (set to Migration::DESTINATION).
Comment #2
alexander.sibert CreditAttribution: alexander.sibert commentedI try to explain ;). We imported the GeoNames database with own custom D7 module but the Server was sometimes down and i needed to continue the Import. Now i have more node entries than the field entries in Database. I think there are now unused and not assigned field values and i don't need these.
My idea is to setup a fresh D7 and Migrate the Data like a Import to have clean database (only correct nodes and fields will be imported). The missed 355 nodes i will don't need. I can later create a sync script to add missed nodes.
Comment #3
mikeryanBe sure when adding info to an issue with the "Postponed (maintainer needs more info)" status, to change the status back to "Active", for better visibility.
Yes, it sounds like migrate_d2d should fit your needs well. The one bit of custom coding you would want would be to override the node class query() method to add a filter on the field - simply adding an inner join to the field table should do the trick.
Comment #4
alexander.sibert CreditAttribution: alexander.sibert commentedJust read your reply thank you very much and wish awesome Christmas days!