It would be very helpful to see details about views that have broken fields in them on the list of views provided by listing the views at /admin/build/views. I've written code to show in red, to the right of the list of Displays, the fields/relationships/arguments/etc that are broken. I'm posting this here to see if there is interest in this functionality. If I posted a patch file, is there a possibility it would be incorporated into the code?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

DarrellDuane’s picture

Here is a patch that provides this functionality. I'm hopeful that someone can use it to provide the same functionality in 7.x-3.x, as I imagine it will need to be put there first and then backported.

One slight issue with this patch is that there is a bit of a gap of space that appears in the listing of the display types that the view uses. It doesn't break functionality, just makes it a little less pretty. I haven't been able to figure out how to remove this space, perhaps someone with more experience with CSS/theming can figure out what is missing to clean this up.

The list of broken views appears to the right of the list of display types in an area on the screen that wasn't being used, so the addition of this functionality won't take up any more space on the screen once this issue I mention above is fixed.

MustangGB’s picture

Issue summary: View changes
Status: Needs review » Closed (won't fix)
DarrellDuane’s picture

Hi MustangGB,
Could you say more about why you would not accept this bug fix?

MustangGB’s picture

Only that the maintainers said 6.x isn't having any new features.

From the steadily declining install base (https://www.drupal.org/project/usage/views) it this doesn't seem like there is much point to keep this open.

DarrellDuane’s picture

oh, right, I didn't realize I had made this for 6.x. If I adapted it for 7.x would you consider adding it?

MustangGB’s picture

I have no say on what features will or won't be accepted, but it does seem like a sensible feature request to me.

By all means feel free to port your code to 7.x/8.x and re-open if you wish, this issue was just a victim of a bigger 6.x issue queue clean-up.