Message migration reverts "template" value

Created on 26 June 2024, 11 months ago

I'm running into a problem with a migration. I started with the original d7_message.yml and modified it as follows:

langcode: en
status: true
dependencies: {  }
id: upgrade_d7_activitylog
field_plugin_method: null
cck_plugin_method: null
migration_tags:
  - 'Drupal 7'
  - Content
migration_group: mysite
label: 'Activity log'
source:
  plugin: d7_message_source
process:
  mid: mid
  template:
    -
      source: type
      plugin: static_map
      bypass: false
      map:
        admin_create_forum_comment: forum_new_comment_admin
        admin_create_forum_post: forum_new_post_admin
        create_comment: forum_new_comment
        create_forum_post: forum_new_post
        create_node: content_new_node
        user_login: user_login
        user_logout: user_logout
        user_register: user_register
        user_update: user_updated
        view_node: false
    -
      plugin: skip_on_empty
      method: row
      message: 'Unsupported message type.'
  created: timestamp
  uid: uid
  arguments: 
    plugin: d7_message_arguments
    source: 
      - arguments
  langcode: 
    plugin: default_value
    source: language
    default_value: "und"
destination:
  plugin: entity:message
migration_dependencies:
  required:
    - upgrade_d7_user
  optional: {}

As you can see, the "user_update" message type was renamed to "user_updated".

When the migration runs it fails with the error saying "No valid template found". I debugged through it and found that it's trying to use "user_update" as the message type, not "user_updated".

πŸ’¬ Support request
Status

Closed: cannot reproduce

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States damienmckenna NH, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @damienmckenna
  • πŸ‡ΊπŸ‡ΈUnited States damienmckenna NH, USA
  • Issue was unassigned.
  • Status changed to Closed: cannot reproduce 11 months ago
  • πŸ‡ΊπŸ‡ΈUnited States damienmckenna NH, USA

    I renamed the "user_updated" message to "user_update", reran the migration and everything worked. Not sure why this one migration didn't save correctly, but it's an odd one.

    Going to close this and chalk it up to gremlins.

Production build 0.71.5 2024