The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I suppose we should do a meeting today. :slightly_smiling_face:
0️⃣ Who is here today?
| alison | Hi! And congratulations @Nick Dickinson Wilde! |
| Nick Dickinson Wilde | Nick, he/him, T'So-uke lands/Victoria BC :flag-ca: |
| Nick Dickinson Wilde | Thanks Alison! |
| dinarcon | Mauricio here and congrats Nick :slightly_smiling_face: |
| heddn | Lucas here. About to release new releases of various contrib modules with greater D9 support |
| benjifisher | Benji here. Sorry I am late to the party!:balloon: :tada: to Nick! |
| wimleers (he/him) | :wave: Wim but late |
1️⃣ What do we need to talk about?
| dinarcon | It would be good to talk about what is needed to create a Layout Builder destination plugin. #3087210: Layout Builder Destination Plugin for Migrate API |
| benjifisher | @heddn marked it as postponed, but #2746541: Migrate D6 and D7 node revision translations to D8?page=1 is a high priority. |
| wimleers (he/him) | We already showed @heddn, @mikelutz and @quietone but now it’s public: https://twitter.com/wimleers/status/1255872225535819777 |
| wimleers (he/him) | FYI: @huzooka is contributing a lot to @juampynr’s https://www.drupal.org/project/media_migration — some good progress there! |
2️⃣ MigrateUpgradeImportBatch does not use source_private_file_path & source_base_path correctly, making it impossible to have public & private files in separate locations
3️⃣ Migrations fail due to missing dependency when dependency is clearly not missing.
| mikelutz | #2797505: Migrations fail due to missing dependency when dependency has skipped rows by the source plugin |
| wimleers (he/him) | Interesting one! Following now. |
4️⃣ Rollback of complete node migration fails
| mikelutz | #3123095: Rollback of complete node migration fails |
5️⃣ Call to a member function getSetting() on null in Drupal\migrate_drupal\Plugin\migrate\EntityReferenceTranslationDeriver->getDerivativeDefinitions()
| mikelutz | #2984460: Call to a member function getSetting() on null in Drupal\migrate_drupal\Plugin\migrate\EntityReferenceTranslationDeriver->getDerivativeDefinitions() |
6️⃣ SQL error if migration has too many id fields
| mikelutz | #3098282: [backport] SQL error if migration has too many ID fields |
| heddn | @quietone this is an interesting problem. If I recall correctly, the index was added for performance reasons. It isn't strictly necessary. An option could be to warn and build the table w/o the indexes |
7️⃣ Migration failed with source plugin exception: upgrade_d6_language_content_taxonomy_vocabulary_settings
| mikelutz | #3101045: LanguageContentSettingsTaxonomyVocabulary source plugin should only add language column if it exists |
8️⃣ errors in migration process configuration don’t give a clear message
| mikelutz | #2969231: errors in migration process configuration don't give a clear message |
| Nick Dickinson Wilde | well that would certainly have saved time in the past for me - I've often used xdebug for just that which is a bit of overkill |
9️⃣ Allow logging for non-strings values
| mikelutz | #3047328: Allow logging for non-strings values |
| benjifisher | I contributed the debug process plugin to the migrate_devel module. It works a lot like t he log plugin, but uses drush_log() or similar so that messages go directly to the terminal instead of being logged as migrate messages. It already works with arrays and such. |
🔟 Layout Buider destination plugin
| mikelutz | #3087210: Layout Builder Destination Plugin for Migrate API |
| dinarcon | There was some discussion about this last week https://drupal.slack.com/archives/C226VLXBP/p1587676641454000 |
| benjifisher | IIRC, it is not clear that a destination plugin is what we actually want. Have you made anny progress since that discussion? |
| dinarcon | In summary, Layout Builder configuration can be exported as part of the view mode. Or if the it is possible to override the default layout per node, then they are assigned to a ‘layout_builder__layout’ field. Does this require separate migrations for configuration and content? Also, there are two elements to migrate: Sections and SectionComponents. |
| dinarcon | @benjifisher no, I have not had further discussions with anyone after last week's conversations. |
| heddn | @dinarcon based on that description, so far it doesn't sound like a new destination is needed, yet. |
| benjifisher | I only have bandwidth for one or two Migrate issues per week. This week, I am looking at the issue I mentioned in 1️⃣ . So if you have ideas, I can talk about them but I am not likely to come up with anything new. |
| dinarcon | @heddn no new destination is needed like in it should be possible with existing migration plugins for content and configuration? |
| benjifisher | I think we need to add to the existing plugins. I am not sure whether we need to add a new process plugin or add to an existing destination plugin or ... |
| benjifisher | I suggest that you start with the config (per bundle, not per entity LB). Figure out where the data might come from (probably Panelizer), what the data look like, where it has to end up. |
| dinarcon | Inside Layout Builder it is possible to have so many things. When migrating, you might have to create block_content entities for example for content that was previously in a field. Creating entities on the fly similar to entity_generate should not be the only option. But then, you need would need multiple migrations with dependencies among them. I am not sure if a process plugin would be the best option for this. |
| heddn | @dinarcon throw up a patch with something. then we can start poking at it. |
| heddn | @dinarcon from what I can tell from my work with LB last saturday and default_content we will have all kinds of things that will have to be "auto generated" on the fly during the migration. and there's no way to know what those things will be until you run into them |
Participants:
alison, Nick Dickinson Wilde, dinarcon, heddn, benjifisher, wimleers (he/him), mikelutz
Comments
Comment #2
mikelutzHello all, it’s time for the weekly migration initiative meeting. The meeting will take place in slack in various threads
This meeting:
➤ Is for core migrate maintainers and developers and anybody else in the community with an interest in migrations
➤ Usually happens every Thursday and alternates between 1400 and 2100 UTC.
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ Has a public agenda anyone can add to here: https://www.drupal.org/project/drupal/issues/3132498
➤*Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.
Comment #8
benjifisherComment #9
benjifisher