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.
So, migration load plugins are almost a thing of the past! YAY!
However, while working on #2530030: Create the migrate builder plugin type, I neglected (read: forgot) to write a builder for the d6_profile_values migration, which uses a load plugin. Before load plugins can be removed, there needs to be a builder plugin which will take over those duties. I have attached one, with a test.
Comment | File | Size | Author |
---|---|---|---|
#13 | interdiff-2549003-11-13.txt | 670 bytes | phenaproxima |
#13 | 2549003-13.patch | 1.24 KB | phenaproxima |
#11 | interdiff.txt | 1.08 KB | mikeryan |
#11 | create_a_builder_for-2549003-11.patch | 1.13 KB | mikeryan |
#8 | 2549003-8.patch | 766 bytes | phenaproxima |
Comments
Comment #3
phenaproximaD'oh.
Comment #4
mikeryanComment #5
phenaproximaThis is blocking some important stuff.
Comment #6
webchickThis sounded a lot scarier than it actually was. :) Turns out the change is very simple and is really just a follow-up from the builder patch that was accidentally omitted.
I inquired about why we need this in the first place, since the wrapping code here is very trivial. Adam pointed out it's because this essentially acts as an "alter" hook to let us pretend that profile fields are real fields.
Works for me.
Committed and pushed to 8.0.x. Thanks!
Comment #8
phenaproximaWhoops! We (read: I, phenaproxima) screwed up a line that broke Migrate Upgrade. This is the fix.
Comment #9
webchickIs there any way to add test coverage for that?
Comment #10
Anonymous (not verified) CreditAttribution: Anonymous commentedThis patch fails if you do not have profile installed in D6...
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'd6.profile_fields' doesn't exist: SELECT pf.fid AS fid, pf.title AS title, pf.name AS name, pf.explanation AS explanation, pf.category AS category, pf.page AS page, pf.type AS type, pf.weight AS weight, pf.required AS required, pf.register AS register, pf.visibility AS visibility, pf.autocomplete AS autocomplete, pf.options AS options FROM {profile_fields} pf; Array ( )
Comment #11
mikeryanWe need to check the requirements (specifically source_provider=profile).
Comment #12
mikeryanMigrate critical, since it totally breaks migrate-upgrade.
Comment #13
phenaproximaAdded a comment mentioning the need to pass database connections to Migrate SQL sources, rather than letting them create connections out of thin air.
Comment #15
webchickOk, let's get this in. Tests are being deferred to #2552791: MigrateSqlSource should use dependency injection to unblock Migrate Upgrade. It's not straight-forward.
Committed and pushed to 8.0.x. Thanks!