Just upgraded from Views 3 RC2 to RC3 and am getting the following error on many node page that have views based on node references.

The full error is:

Debug:
'Exception: SQLSTATE[42S22]: Column not found: 1054 Unknown column \'field_data_field_related.nid\' in \'on clause\''
in views_plugin_query_default->execute() (line 1386 of /usr/www/users/dproot/sites/all/modules/views/plugins/views_plugin_query_default.inc).

Any thoughts? When running update.php there was a small error and something about an index key. Tried to reload the main page and everything was fine until I hit one of these view pages. Now this DEBUG error shows up consistently to all users (incl. anonymous). Any idea how to fix?

Comments

dawehner’s picture

Status: Active » Fixed

Update references module to dev or search the issue queue first.

frishaynes’s picture

Same problem here. Tried dev version of references but eventually went back to Views RC1 and the problem has gone away and my Views are working again.

Problem was with an Eva View.

13rac1’s picture

Updating to references dev fixed this for me.

drupalninja99’s picture

Works for me

RIA212’s picture

I just update to references dev but still having the same message when I'm adding a relationship.
Any idea? I have views dev and references dev versions.
@frishaynes How may I get views rc1 that solved your problem?
thanks in advance

fran70’s picture

I update views rc3, and i have the same problem. I tried references dev with views rc3, and problem follow.
Finally i change to views rc1 and works fine.

bobaloo’s picture

Latest References dev fixed the problem for me as well, same as #3 and #4

Status: Fixed » Closed (fixed)

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

mrharolda’s picture

Any chance this gets released any time soon? I don't like to use -dev modules on production sites...

13rac1’s picture

@MrHaroldA This issue is in the Views issue queue, not the References issue queue. The request for a new release would never be seen.

Additionally, this problem is long fixed in the current References release. The initial comment by dereine saying to use the dev of References was written 11/28/11. The most recent release of References was created on 12/22/12, therefore the problem has been corrected in the released version.

I've neverc completely understood why people don't want to use dev versions. Could you explain?

mrharolda’s picture

I've neverc completely understood why people don't want to use dev versions. Could you explain?

1) Drush doesn't know which -dev version you are using
2) -dev versions aren't screened for security holes
3) -dev implies that it's not stable to use
4) Our clients dislike things like -beta, -alpha, -unstable and also -dev
5) ...