I wrote a Scald Atom source for a migration I recently worked on.
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | scald-atom-migrate-source-2772129-16.patch | 2.16 KB | seanr |
| #14 | scald-atom-migrate-source-2772129-14.patch | 2.18 KB | seanr |
| #10 | scald-atom-migrate-source-2772129-10.patch | 2.16 KB | seanr |
| #4 | scald-atom-migrate-source-2772129-2.patch | 2.3 KB | andrewmacpherson |
Comments
Comment #2
andrewmacpherson commentedThis patch provides a Scald Atom entity source. It works much like the D7 node source, pulling in Field API values during
prepareRow().It has an
atom_typeconfiguration key, to specify the scald atom bundle in the D7 source data.I didn't write a migrate source for scald types; these were configured manually in our D8 project.
Comment #3
andrewmacpherson commentedWhere did the patch go? I think I forgot to press the upload button.
Comment #4
andrewmacpherson commentedComment #5
slashrsm commentedComment #6
dan_metille commentedIs this patch still working? And if it is the case is it please possible to have some instruction about how to migrate scald to media entity? Thanks a lot, because I was expecting a much smoother migration process to D8.
Comment #7
heddnLinking in #2906878: [Meta] Support for D7 -> D9 contrib migrate
Comment #8
seanrDocumentation on this would be much appreciated - an example migration to go along with this patch would be a huge help. Also +1 to Sahaj's question on whether this has been affected by any changes elsewhere.
Comment #9
heddnFor creating a fixture for any testing, see https://www.drupal.org/docs/8/api/migrate-api/generating-database-fixtur...
This need a source_module too per https://www.drupal.org/node/2911881
Rather than list all the fields, can we simplify things and just grab all of them?
This feels like a good case for a deriver. I could be wrong.
Why is this needed? Transforms like this usually happen in a process section of the migration.
Comment #10
seanrMoving this along a little, I hope...
Comment #12
seanrUgh, I'll try to re-roll that from scratch later today.
Comment #13
andrewmacpherson commentedGood to see someone picked this up. The patch I put in place was a work-in-progress as of D8.1. Things like
source_modulehave come along since then.Re: #9.4
I honestly don't remember. I expect I was still learning my way around wiring up process pipelines in D8. As it happens, the requirement to migrate Scald atoms was dropped from the client project I was working on at the time. It had a mixture of imagefields and scald atoms, and the particular source field that used scald was dropped as a non-essential field. That's the way things go.
Comment #14
seanrRe-rolled
Comment #16
seanrThanks to @jhodgdon updated patch here. Hopefully this'll work. ;)
Comment #17
vitchy commentedThanks to updated patch. I'm beginning a drupal 8 migration with scald media. Also i applied patch but no media was imported. Anyone could list steps necessary to follow for migrate scald from D7 to D8 ?
Thanks
Comment #18
scsmith commentedI'm a bit lost as well. I've tried, unsuccessfully to install the patch on a clean drupal 8.5.3. Without being able to migrate my scald atoms, I'm not able to upgrade to 8 from 7! I'd really like to see an easy way to upgrade!
Comment #19
dan_metille commentedAs @vitchy and @scsmith, I'm still lost on this.
Patch #16 do not seams to work on upgrade (I have tried from D7 to D8.6 dev), right?
As @vitchy requested 1 month ago, it would be very welcome to get a step by step tutorial on how to migrate Scald from D7 to D8. At least to know if this is really possible to perform at this moment (I mean, somebody succeeded at it ?) and to get some insights about what is required (are any contributed Migrate modules required?) to complete the task.
It is now 1 year that I'm trying to upgrade some sites using Scald to D8, first waiting for 8.4 and media in core to be released, hoping that it will solved the problem, then waiting for 8.5 for a better upgrade integration. And still I'm facing a wall. This is very frustrating.
Comment #20
seanrPretty sure the patch is really only going to work in a custom migration - you'll have to set the mappings and everything. There's no pure upgrade path for this since Scald was a dead end. This patch just makes the source available to migrations.
Comment #21
jcisio commentedThe patch works as expected. Here is an example with this patch, to migrate D7 Scald atom image to D8 media image:
I don't think it's reasonable to expect an out of the box Scald to Drupal 8 Media migration, given the priority and number of Scald sites and Scald providers, and in most cases, the fields will change.
I'm wondering whether this patch lives on Media Entity 2.x (there is nothing related to Media entity...) or in Scald 8 (module does not exist yet).
Comment #22
jcisio commentedIn case that #21 is not enough, here is the code snippet to migrate atom reference fields:
Comment #23
dan_metille commented@jcisio you said:
I'm also wondering that too! Also would like to know how to update that .php file for Media in core.
I'm really wiling to share a proper step by step guide to migrate Scald from D7 to Media in D8, but I need to be able to perform it at least once with basic configuration case.
Comment #24
j4 commentedHi @sahaj, any updates on this? Were you able to carry out a migration? Thanks!
Comment #25
sylvainm commentedI made a contrib module to handle that: https://www.drupal.org/project/migrate_source_scald
Feel free to contribute :-)