3 to 4 upgrade path for audio_file and video media type changes

Created on 15 October 2020, over 4 years ago
Updated 8 May 2023, over 1 year ago

Problem/Motivation

When updating acquia/lightning from 4.1.6 to 4.1.7, lightning_media is also updated from 3.16 to 4.2. In this transition the original "audio_file" media type becomes "audio" and the original "video" media type becomes "remote_video". We now have 2 extra media types that are created by lightning_media. This is undesirable. We are using blt and pipelines which rebuilds the site during the workflow.

In lightning_media_audio_update_8001() there is reference to the change from audio_file to audio but I have not seen an upgrade path.

Steps to reproduce

Proposed resolution

I propose that a upgrade path be included to move the audio_file and video media types to the new audio and remote_video media types.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Postponed

Version

4.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States oheller

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States loopy1492

    I believe this cropped up becase, at some point, someone on our team ran the update without exporting the configuration. I'm trying to fix it now, but it looks like the version we are running (5.x) no longer has update 8001 in it so I can't run that update with either php-eval "module_load_install('lightning_media_audio'); lightning_media_audio_update_8001;" on d9.5.x or php-eval "\Drupal::moduleHandler()->loadInclude('lightning_media_audio', 'install'); lightning_media_audio_update_8001;" on d10.0.x.

    Too bad.

    I WAS able to uninstall and reinstall the module to get the correct fields and delete the config for the old ones. But we are lucky that we do not have any media.audio_file content on the site because I suspect if I did this, that content would explode or at the very least the content for the old "audio_file" field would have disappeared and a blank "audio" field would have taken its place.

Production build 0.71.5 2024