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 have a D-5.11 site with one view. The view was lost on upgrade.
I don't necessarily need support of this; I can easily re-create the view. This is more of an FYI.
In case it matters, the view depends on CCK, which I have not yet installed on my 6.x copy. (Yes, I realize that not having CCK means I will be missing all CCK-provided functionality such as its fields.)
Comment | File | Size | Author |
---|---|---|---|
#15 | updating.html_.patch | 1.07 KB | esmerel |
#1 | views_drupal5.png | 87.75 KB | Aren Cambre |
#1 | views_drupal6.png | 91.44 KB | Aren Cambre |
Comments
Comment #1
Aren Cambre CreditAttribution: Aren Cambre commentedBTW, by "lost" I mean it's not there at all.
I've attached screen shots of the drupal 5 and 6 views lists.
Comment #2
merlinofchaos CreditAttribution: merlinofchaos commentedvisit admin >> build >> views >> tools >> convert
Comment #3
Aren Cambre CreditAttribution: Aren Cambre commentedRequesting that UI point out when un-upgraded views are present.
Comment #4
paulnem CreditAttribution: paulnem commentedI'm really just subscribing to this so I don't forget about the views upgrade, however it would be great if views were automatically converted on upgrade.
Comment #5
xabooth CreditAttribution: xabooth commentedI thought it was broken on my end. It would be helpful to have a little note that said where to convert existing views. tools -> convert is pretty hidden.
Comment #6
esmerel CreditAttribution: esmerel commentedComment #7
esmerel CreditAttribution: esmerel commentedComment #8
Aren Cambre CreditAttribution: Aren Cambre commentedComment #9
dawehnerWhere is the point of moving the issue?
Comment #10
Aren Cambre CreditAttribution: Aren Cambre commentedDon't all features get implemented in the newest branch? Also, this is a UI issue, not a documentation issue. The request is that the UI make it obvious that views are not upgraded. Right now the UI gives no hint of this problem.
@esmerel--did you mean to assign this issue to yourself?
Comment #11
dawehnerNo new issues get's developed until 6.x-3.x
Additional assigned esmerel this issue against the component documentation.
Comment #12
Aren Cambre CreditAttribution: Aren Cambre commentedBut the problem is not documentation. It's that the UI doesn't give any indication that the views need to be upgraded. If you haven't run update.php since updating Drupal or modules, Drupal itself does inform you of the need for upgrades. Why not views?
Comment #13
esmerel CreditAttribution: esmerel commentedThis isn't getting changed in the UI, and yes, I assigned it to myself to make sure this was in the documentation, because that's where it belongs.
Comment #14
merlinofchaos CreditAttribution: merlinofchaos commentedBecause an extra query to see what's in that table would be a performance burden on the 99% of sites that don't need that information. Seriously, we've gone 2 years and it hasn't been a problem, and nobody cares about D5 upgrades at this point. The vast majority of the sites that are going to go through an upgrade process already have.
The Views upgrade process is different from core because it can't be done automatically, so comparisons to core don't work here. Core just upgrades you and you pray it worked.
At best this is, as esmerel said, a documentation issue, because the documentation should point you to the right place to do it. Mostly people have figured this out.
This is not a place where I think it is worthwhile to put any non-documentation effort.
Comment #15
esmerel CreditAttribution: esmerel commentedAdded detail to the advanced help page for updating from views 1 to views 2.
Comment #16
dawehnerLooks fine
Comment #17
esmerel CreditAttribution: esmerel commentedCommited to 6.x-3.x