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.Hi. I stumbled upon this change after someone updated media_gallery on prod: http://drupalcode.org/project/media_gallery.git/commitdiff/660d8772b728e...
Is there going to be an upgrade path for this any time soon or should I just do it myself? Yes, I realize this is how the dev branch works :-P
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | media_gallery-rename_field-1940036-3.patch | 2.75 KB | jsagotsky |
| #1 | media_gallery-rename_field-1940036-1.patch | 2.48 KB | jsagotsky |
Comments
Comment #1
jsagotsky CreditAttribution: jsagotsky commentedHere's an update hook. Should be straightforward. It works against the prod data I've checked so far, but I'd appreciate if anyone could throw me some comments before we run it for real.
Comment #2
Bernsch CreditAttribution: Bernsch commentedComment #3
jsagotsky CreditAttribution: jsagotsky commentedSlight change to the patch. We ran into some cases where the new field's table already existed, probably due to a feature revert. When that happens, the table is dropped if it's empty and the update proceeds as normal. If it has content, the update skips.
Ideally this should probably merge both tables together instead.
Comment #4
markpavlitski CreditAttribution: markpavlitski commentedHi, Just saw this issue after posting a patch for this in #1883270: errors after upgrade to media_gallery 2.x - Undefined property: stdClass::$media_gallery_file in media_gallery_node_load() .
It takes a slightly different approach in that it creates the media_gallery_file table first (which doesn't quite match the existing media_gallery_media table) and then migrates the data over.
Comment #5
Moloc CreditAttribution: Moloc commentedThis issue seems to be fixed in the issue referenced in #4