D6: Views 6.x-2.x upgrade path still broken? [#2324061]

I never upgraded any of my sites to Drupal 7 because the Views project notes that the "Views 6.x-2.x upgrade path still broken".

Now that Drupal 8 is coming soon, I want to make sure that I understand the situation, and whether there is a solution.

If I will be able to upgrade from Views 6.x-2.x to Drupal 8, then there is no issue. Otherwise:
Does the Views 6.x-2.x upgrade catastrophically corrupt an installation?
Does the Views 6.x-2.x upgrade merely not support "pagers", in which case, can I upgrade, and reset the pager configuration?
Is there another workaround which will ensure I can upgrade in some way to Drupal 8?

Comments

Comment #1

iantresman commented 21 April 2015 at 15:53

According to the statistics, of those people using Drupal 6.x, there are as of 12 April 2015:

99,321 people using Views 6.x-2.x (equivalent to 6:1)
16,121 people using Views 6.x-3.x

I suspect these people haven't upgraded because of the known bug. Is there a workaround? Can I manually Export a View from Views 6.x-2.x, and Import the resulting text file directly into Views 6.x-3.x?

It would be very nice to easily migrate from Views 6.x-2.x to Drupal 8 core, but a manual Export/import would be OK.

Comment #2

iantresman commented 14 May 2015 at 12:22

In Views3 help, in particular the file updating.html says:

There are no known issues converting views from Views 2 to Views 3 at this time.

So is there a bug, or are there no known issues?

Comment #3

iantresman commented 22 July 2015 at 13:16

Still uncertain whether this is still an issue, here are some other posts which may help identify the problem:

Comment #4

almaudoh commented 22 July 2015 at 15:08

Some years back I upgraded the views installation in one of my sites from 6.x-2.x to 6.x-3.x and I didn't have any issues afterwards.
I was initially scared by that warning, but still decided to take the plunge.

Comment #5

othermachines commented 21 November 2015 at 00:28

In anticipation of 6.x-8.x Drupal migration I just updated a site with a couple dozen views from 2.x to 3.x branch with only minor problems, all but one of which required I manually reset the pager. The other one was related to better_exposed_filters module, which you'll also need to update if you're using it. So I wouldn't worry too much about it as long as you can do it in a dev environment first (and you should always do this, anyway). Cheers -

Comment #6

iantresman commented 22 November 2015 at 09:03

I don't think resetting the pager is a big deal. Would be nice if the process could warn people, but at least there is no blue screen of death, or data loss.

Comment #7

othermachines commented 23 November 2015 at 17:19

@iantresman

One other thing: If your sites use Image Assist (which uses Views 2 API), you'll need to refer to this issue: https://www.drupal.org/node/712836. It's a simple fix but it took me awhile to find it.