I have a site that uses style settings applied to views fields extensively, generally by assigning classes to particular fields. Upon upgrading from alpha1 to beta3, I've found that I've lost all style information. Every field in every view appears to have the default options selected (e.g. 'Create a label', 'Add default classes' etc.), even where I had explicitly changed those values in my old 3.0-alpha1 installation.

Is this an expected behavior? Is there anything I can do to restore these values, or can I re-do the upgrade process differently? This time around, I upgraded views first, then ctools (from alpha2 to alpha4), then cleared the cache multiple times.

CommentFileSizeAuthor
#5 7.x_3.0_alpha1_export.txt - PRE UPGRADE12.23 KByskel
#5 7.x_3.0_dev_export.txt - POST UPGRADE - PROBLEMS12.88 KByskel

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

Please take sure that you first try the current dev version of views.

Once you have tryed this out, please try to give us a view which we can use to reproduce the problem

yskel’s picture

yskel commented

From where I am now, a site with broken views, should I try to upgrade to dev, or should I restore to pre-upgrade, and then directly upgrade to dev?

Thanks for the amazingly quick response.

dawehner’s picture

dawehner
Primary language German
commented

Before you upgrade any module make a backup always!

I would say that pre-upgrade doesn't change something because we don't run update functions.

yskel’s picture

yskel commented

Definitely good advice! This is a dev install that I'm playing with, and I've got a clean backup, so no real data is in danger either way.

I'll upgrade Views to the latest dev now.

yskel’s picture

yskel commented
StatusFileSize
new 7.x_3.0_dev_export.txt - POST UPGRADE - PROBLEMS12.88 KB
new 7.x_3.0_alpha1_export.txt - PRE UPGRADE12.23 KB

Alright, I've upgraded to the latest dev. I'm still having problems, although it looks like a slightly different set of problems. My custom classes have generally been carried over now, but issues like labels being assigned to every field still exist. I've attached two exports here, one pre-upgrade, and one post. Please let me know what else I can provide.

merlinofchaos’s picture

merlinofchaos commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Okay, the problem is that Field API fields have changed somewhat dramatically since the early alpha.

Back in the days of alpha1, we were just letting Field API handle the generation of the label. For various reasons, this is really bad for Views (like, for tables). In those days, the handler was actually suppressing the Views' label.

There is no way for the current, correct system to tell how the older system was set up. Meaning, unfortunately, there is no choice but for you to go through your views and fix this.

If it helps, you could use the CTools' bulk export module and your views to code and modify the code (finding the labels isn't hard). That might be significantly less tedious than unsetting the labels one by one if you have a lot of views and/or a lot of fields.

yskel’s picture

yskel commented

Got it. Thanks for the suggested solution - I'll try it out.

Maybe there should be a line in the release notes about this issue? Not sure how many actually used alpha1, but this would be a pretty big problem if you applied the update to a live site.

merlinofchaos’s picture

merlinofchaos commented

Probably a little late for the release notes now, but we should note this somewhere, at least.