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.In the attachment the MigrateFieldHandler implementation for the tablefield field type.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | tablefield_migrate-support-2317245-6.patch | 1.81 KB | paolomainardi |
| #3 | tablefield_migrate-support-2317245-3.patch | 1.73 KB | paolomainardi |
| #2 | tablefield_migrate-support-2317245-2.patch | 1.74 KB | paolomainardi |
| #1 | tablefield_migrate-support-2317245.patch | 1.75 KB | paolomainardi |
Comments
Comment #1
paolomainardi CreditAttribution: paolomainardi commentedComment #2
paolomainardi CreditAttribution: paolomainardi commentedSorry there was a typo, this is the correct one.
Comment #3
paolomainardi CreditAttribution: paolomainardi commentedSorry, a typo again :( i can't delete the previous ones.
Comment #4
kaareClean, decoupled code which works as promised. I've just migrated a cck-6.x-3.x multigroup field to this and had no trouble with it. It sure didn't work without this patch.
Comment #5
Kevin Hankens CreditAttribution: Kevin Hankens commentedSweet! Thanks for the effort. I just realized that email notifications got turned off, so I'm just trying to catch up. I'll see about getting this into a new version soon.
Comment #6
paolomainardi CreditAttribution: paolomainardi commentedThis patch fixes empty values.
Comment #7
brentrobbins CreditAttribution: brentrobbins commentedOMG, thank you paolomainardi. This is exactly what I needed and the tablefield_migrate-support-2317245-6.patch patch worked great (and by the way I am using ver 7.x-2.4). Thanks again!
Comment #8
paolomainardi CreditAttribution: paolomainardi commented@kevinhankens can be merged ?
Comment #9
vitalie CreditAttribution: vitalie commentedMany thanks @paolomainardi. I can commit this, but I wonder if either:
* this can be put into a separate sub-module, e.g. tablefield_migrate
or
* the two new inc files moved to a includes/migrate folder.
Even it's a few lines of code, I think I prefer first option, since this is needed only a very short time in the life of a website, so a separate sub-module could be disabled/uninstalled when its job done.
Comment #10
paolomainardi CreditAttribution: paolomainardi commented@vitalie i suggest to keep the structure as in the patch, if you see other modules it is accepted as a standard structure, create a separate module just for a class it is too much IMHO.
Comment #11
vitalie CreditAttribution: vitalie commentedok, but I am still reluctant to dedicate tablefield.inc name for a file that only hosts a migrate class, that is only used at the beginning of the lifetime of a setup (most probably).
Comment #12
paolomainardi CreditAttribution: paolomainardi commented@vitalie that is the way to be autoloaded by migrate module.
Comment #13
vitalie CreditAttribution: vitalie commented@paolomainardi it's definitely not the only way. I've written migrate classes and successfully located them anywhere I really liked, actually.
Comment #14
paolomainardi CreditAttribution: paolomainardi commented@vitalie yes there other ways too, but the one i propose is the mainly used and it is the standard way to do that :)
Comment #15
vaccinemedia CreditAttribution: vaccinemedia commented@paolomainardi I've applied the patch :) I'm using a yaml file as the source. Can you tell me how the value should look and give an example field mapping please?
Comment #16
lolandese CreditAttribution: lolandese at HCL Technologies Limited commentedComment #17
noel.delacruz CreditAttribution: noel.delacruz commentedI know this patch is for Drupal 7, is there a patch that supports the migration for the Drupal 8 version?