Problem/Motivation
There is no migration path from Drupal 6 Views 6.x-2.x to the new Drupal 8. Views 6.x-3.x migration is supported.
While this is not critical to the release of Drupal 8, it is critical to the vast majority of Drupal 6 Views v2 users, who will not have an easy upgrade path.
The Drupal 8 FAQ proclaims that there will be a migration path from Drupal 6. The most popular Drupal 6 module is Views, and of those, the number of people using Views 6.x-2.x is six times more than those using Views 6.x-3.x (raw data | Totals).
Furthermore, the Views project page says there is a bug upgrading from Views 6.x-2.x to Views 6.x-3.x, making this route unreliable.
Proposed resolution
Provide a migration path, otherwise most Drupal 6 sites will not have a path to Drupal 8.
Remaining tasks
The migration of Views v2 schema, that are not already catered to in the migration of Views v3 schema.
Comments
Comment #1
iantresman commentedI think this is a D7 upgrade path issue too, and critical, as it appears similar to issues like this one. I am happy to be corrected.
This bug is mentioned on the Views project home page: ".. there is an upgrade bug in 6.x-2.x that causes upgraded views to break". It prevents people with Views 6.x-2.x from upgrading.
Comment #2
pfrenssenThere is a related discussion in the Views queue: #2324061: D6: Views 6.x-2.x upgrade path still broken?.
It seems like that notice about the broken upgrade path has been there for quite some time. We would need to know what exactly is broken. Also we only need a viable upgrade path to D7 to solve the critical part of this issue.
Comment #3
tim.plunkettMigration bugs are not critical yet, that other issue is not about migrations but update path.
Comment #4
dawehnerI'd strongly suggest to just support 6.x-3.x to 8.x and force people to move from there to 8.x
In general this issue is certainly a duplicate of another migrate issue which also wants to provide such a conversion.
I remember that is has been related with pagers and it was literaly not possible to distinct two different expected behaviour, so there was no way to update properly, but its not like it would block you entirely from moving over.
Comment #5
iantresman commented@dawehner. But there are six times more people using Views 6.x-2.x than Views 6.x-3.x. I wanted to upgrade to Drupal 7, but this was blocking me. I want to upgrade to Drupal 8 too, but won't be able to do so as easily if there is no upgrade/migration path from Views 6.x-2.x.
Comment #6
catch@iantresman what stops you upgrading from 6.x-2.x to 6.x-3.x then from 6.x-3.x to either 7 or 8 though?
From my memory of doing a 6.x-2.x to 6.x-3.x upgrade and Daniel's comment in #4, the upgrade path from 6.x-2.x to 6.x-3.x is mostly there. The project page unfortunately does not say what the issue is with the upgrade (i.e. neither a description on an issue nid).
Comment #7
iantresman commented@catch. Because I interpret the message on the Views home page, ".. there is an upgrade bug in 6.x-2.x that causes upgraded views to break", to mean that it might break my Views.
I believe that some people have updated without problems, but with 50 sites, I don't want to be one of those who has to fix broken Views.
Comment #8
catch@iantresman well you could test the upgrade path on some of those sites and find out if it's a real issue?
Comment #9
iantresman commented@catch. I'll have to figure out how to do it, without risking my live sites. I believe I can make copies and run them locally, but I've not done it before.
Comment #10
catch@iantresman you should be doing that before any core or contrib update anyway, many, many contrib modules have upgrade path issues without advertising the fact on their project pages.
Comment #11
dawehnerI'm happy to support anyone who tries to work on a 6.x-2.x update function to fix the pager problem.
We could then release a new version of 6.x-2.x, so the update path to 6.x-3.x is no longer broken.
Once this is done, this issue can disappear, but maintaining two update paths is not optimal.
Comment #12
iantresman commented@dawehner. Is it only a pager issue? Seems a little odd, as the setting is only Full/Mini/None, and that should be trivial to upgrade. I assumed that something "that causes upgraded views to break", was far more serious, eg. "WSOD when updating from 6.x-2.x to 6.x-3.0", but as you say, the pager issues is noted in "Mark the 6.x-3.x branch as recommended".
Comment #13
catchIt was a long time ago that I did a 6.x-2.x to 6.x-3.x upgrade, but I think the issue was the number of items per page not getting migrated over. When that isn't set, it defaults to unlimited, so on sites with lots of content you could end up with very large pages and WSOD until the views are updated.
Comment #14
iantresman commented@catch. That does seem consistent with this post which suggests that a WSOD "might be triggered by the changed pager settings in Views 3 that lead to timeouts".
Comment #15
xjmI think this issue should be a wontfix. It's always been required to update to the latest version of a project for a given release of Drupal before upgrading to the next release of Drupal.
Also, when the VDC team added Views to core, the committers told us that it was not core's responsibility to provide upgrades for contrib data, that this would need to be supplied by contrib. Honestly, I'd say that if your site is running 6.x-2.x, you're better off recreating the Views by hand unless you have hundreds of them or something. (Create the views in D8, export the config, and then add installing them to the end of your migration process.)
Comment #16
tim.plunkettCouldn't agree more.
Comment #17
iantresman commentedComment #18
tim.plunkett1) is a bug in views, not in core
2)
Comment #19
iantresman commented@tim. "It has always been required to update the latest version of Drupal", until now. One of the main attractions of Drupal 8, is that you don't have to update D6 to D7 first.
If we are going to ignore this issue, then we'll need to update the Drupal 8 documentation (here and here), which promised Drupal 6 using Views 6.x-2.x, a migration path.
Comment #20
mallezie@iantresman, i can't see where the documentation you've linked, mentions an upgrade path / migration of views 6.x-2.x
Comment #21
iantresman commentedDrupal 8 documentation says it will provide a migration path from Drupal 6, here. In Drupal 8, Views is in core. In Drupal 6, Views 6.x-2x is the recommended version of Views (here), and is used by 6 times as many people as Views 6.x-3.x.
In my opinion, that implies an obligation to provide a migration path from Drupal 6 (with Views 6.x-2.x), to Drupal 8. I am happy for others to disagree, but it means leaving the majority of people with Drupal 6 (and Views 6.x-2.x) out in the cold.
Comment #22
mallezie@iantresman, i see that your point linking to the documentation, is to have a migration from the 'recommended' views version in D6 to D8.
It's correct that the 'recommended version' of views for D6 is still 6.x-2.x. However that's because there is an upgrade bug from 2.x -> 3x.
'For new installs of Drupal 6, we recommend the 6.x-3.x branch. We have not changed the recommended version you see below, because there is an upgrade bug in 6.x-2.x that causes upgraded views to break. We don't want anyone getting a surprise breakage of their site.'
However there is an upgraded path from views 6.x-3.x to D8, so the documentation is correct. In your case your steps should be to upgrade from 6.x-2.x to 6.x-3.x and then to D8. Which makes this a 'duplicate' issue of the D6 views upgrade bug. But you could help with those by testing that upgrade, and even the views maintainers are willing to fix some of those upgrade bugs, you sould encounter (which isn't even sure, you'll encounter problems). If the upgrade seems correct, views 6.x-3.X could even become the recommended release.
To test the upgrade, it's indeed best to test those locally (and not on the live site). You could find documentation to do that on https://www.drupal.org/node/157602
Comment #23
iantresman commented@mallezie. Thank you for the explanations. Although I still feel we should be making it as easy as possible for people on Views 6.x-2.x, I understand the issues. Thank you also for the link to help set up the local server, it is exactly what I was looking for.
Comment #24
neffets commentedPlease show us a solution to first upgrade from 6.x-2.x to 6.x-3.x.
You mentioned a "bug concerning pages with not set item count".
Is it correct ? - QUESTION:
"If you set a item count in all Your 2.x views, then you can easily migrate to 3.x views?"