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.
I don't know if this will be useful to anyone. At the company I worked for they had a large distrubution running over 100 website. They were running draggableviews 1.x-dev. I created an upgrade path so the data wasn't lost when we upgraded to 2.x.
For the UI, I had to recreate the views manually then export it as a feature.
In #1 is the patch that worked for us. I do not know if it will work for you.
Comment | File | Size | Author |
---|---|---|---|
#6 | data-update-path-1.x-2.x-1730474-6.patch | 5.41 KB | iStryker |
#4 | data-update-path-1.x-2.x-1730474-4.patch | 5.23 KB | drasgardian |
#3 | data-update-path-1.x-2.x-1730474-3.patch | 6.62 KB | iStryker |
#1 | data-update-path-1.x-2.x-1730474-1.patch | 6.46 KB | iStryker |
Comments
Comment #1
iStryker CreditAttribution: iStryker commentedAttach is the patch. If you apply this patch to 7.x-2.x-dev, everything will work. If you apply this patch to 7.x-2.0, things will probably break because of #1662830: Wrong hook_update_N()
If I find time, I plan on adding a check for schema version and will re-roll this patch.
Again:
To test or to upgrade:
Comment #2
iStryker CreditAttribution: iStryker commentedComment #3
iStryker CreditAttribution: iStryker commentedAttached is the patch that will not break if you do a 7.x-2.0 -> 7.x-2.x-dev (or 7.x-2.0 -> 7.x-2.x).
Comment #4
drasgardian CreditAttribution: drasgardian commentedAttached is a patch to also support upgrading data that has a hierarchy, i.e. uses parent field.
btw, this patch also removes the temp table used in the previous patches, because it didn't seem to be doing anything.
Comment #5
iStryker CreditAttribution: iStryker commented@dragardian Temp table is removed in 7102. If 7101 fails, there is always a temp table to go back to. If 7101 works, then 7102 gets fire, which removes the temp table.
However this is not standard Drupal practice. Standard Drupal practice is to backup database before hand, if it fails, then you restore your backup. So, your solution is better
The patch looks good to me. Maybe later this week I will get a chance to test it more.
Comment #6
iStryker CreditAttribution: iStryker commentedJust testing upgrade of 1 to 2 with Taxonomy Hierarchy. Everything went smooth.
Steps
Upgrade script will not run if you have version 7.x-2.0, as it does a check
Now should this patch get committed? The only thing that is holding me back is the need to fix all of your draggableviews views after running the upgrade script. IMO, It is too complicated to create a script that will fix your views automatically.
I added an updated message in the attached patch:
from
to
This will get display when before you apply the pending update(s).
Comment #7
iStryker CreditAttribution: iStryker commentedSpoke with @ygerasimov. His only worry was this script might get hung on a table with thousands of rows. If anyone experience this and has trouble, please comment on issue.
Again my solution for large production is:
Only one difference. I push changes to private git repository, then pull them down to live. Depending on your environment, there are other [better] ways of doing this.
Committed #6 to dev. (& removed extra white-space)