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.)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Aren Cambre’s picture

FileSize
91.44 KB
87.75 KB

BTW, by "lost" I mean it's not there at all.

I've attached screen shots of the drupal 5 and 6 views lists.

merlinofchaos’s picture

Status: Active » Closed (won't fix)

visit admin >> build >> views >> tools >> convert

Aren Cambre’s picture

Title: View lost upon upgrade » Make view upgrade obvious in UI
Category: bug » feature
Status: Closed (won't fix) » Active

Requesting that UI point out when un-upgraded views are present.

paulnem’s picture

I'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.

xabooth’s picture

I 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.

esmerel’s picture

Component: Code » Documentation
esmerel’s picture

Assigned: Unassigned » esmerel
Aren Cambre’s picture

Version: 6.x-2.0 » 7.x-3.x-dev
Component: Documentation » User interface
dawehner’s picture

Where is the point of moving the issue?

Aren Cambre’s picture

Don'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?

dawehner’s picture

Version: 7.x-3.x-dev » 6.x-3.x-dev
Component: User interface » Documentation

No new issues get's developed until 6.x-3.x

Additional assigned esmerel this issue against the component documentation.

Aren Cambre’s picture

But 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?

esmerel’s picture

This 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.

merlinofchaos’s picture

Because 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.

esmerel’s picture

Status: Active » Needs review
FileSize
1.07 KB

Added detail to the advanced help page for updating from views 1 to views 2.

dawehner’s picture

Status: Needs review » Reviewed & tested by the community

Looks fine

esmerel’s picture

Status: Reviewed & tested by the community » Fixed

Commited to 6.x-3.x

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.