I got the following error on the update.php follow-up page and some of my views are broken
Notice: Undefined index: entity type in views_handler_field_entity->init() (line 38 of /home/billboar/public_html/bcf2/sites/all/modules/views/handlers/views_handler_field_entity.inc)
In addition I am seeing the following message attached to my broken views
Debug:
'Exception: SQLSTATE[42S22]: Column not found: 1054 Unknown column \'field_data_field_event_venue.nid\' in \'on clause\''
in views_plugin_query_default->execute() (line 1386 of /home/billboar/public_html/bcf2/sites/all/modules/views/plugins/views_plugin_query_default.inc).
Comment | File | Size | Author |
---|---|---|---|
#18 | cz_featured_slider.zip | 3.07 KB | Anonymous (not verified) |
Comments
Comment #1
dawehnerDo you use node reference?
Comment #2
MrPaulDriver CreditAttribution: MrPaulDriver commentedIndeed, I do
Comment #3
dawehnerUpdate nodereference.
Comment #4
dawehnerThere are so many issues here, with the same problem.
Comment #5
Abilnet CreditAttribution: Abilnet commentedI had the same error after upgrading to RC3 and running update.php:
Notice: Undefined index: entity type in views_handler_field_entity->init() (line 38 of /home/xxxxxx/domains/xxxxxxxx.com/public_html/sites/all/modules/views/handlers/views_handler_field_entity.inc).
Edit: Not using node reference.
Comment #6
MrPaulDriver CreditAttribution: MrPaulDriver commentedI take it you mean the complete References module.
7.x-2.0-beta3 to 7.x-2.0-dev
Comment #7
MrPaulDriver CreditAttribution: MrPaulDriver commentedFixed for me. Updating the References module to 7.x-2.x-dev did the trick.
As well as running update.php, I also had to clear the cache before the errors cleared
Thank you dereine
Comment #8
dawehnerUpdate status.
Comment #9
epsilon1983 CreditAttribution: epsilon1983 commentedWait, wait, but what about for those of us not using Reference/nodereference? Do I need to install Reference in order to fix this error?
Comment #10
ldedecker CreditAttribution: ldedecker commentedI agree with espilon1983 i do not have reference installed.
Also, for my updates i'm usually using drush and after using it, drush automatically restore initial project.
When updating on my own, i have same kind of problems as described earlier.
May be i should update some other modules, but i assume drush is updating everything that is required.
Also, from comments it is said we need to update reference from beta to dev version, which surprises me as i thought dev is supposed to be less tested than dev ?
Through drush i've tried to see why it is restoring backup but i don't see any usefull information in log
Thanks.
Comment #11
dawehnerMaybe there is another module which implements the views api wrong. What kind of relationship do you have on the buggy views?
Comment #12
bojanz CreditAttribution: bojanz commentedAlso, if you're using Commerce together with Views 7.x-3.0-RC3, it's probably best to use 7.x-1.x-dev (until Commerce 1.1 gets tagged, which should be any day now).
Comment #13
macman91 CreditAttribution: macman91 commentedNotice: Undefined index: entity type in views_handler_field_entity->init() (line 38 of /home/w4835/public_html/billy/sites/all/modules/views/handlers/views_handler_field_entity.inc).
Notice: Undefined index: entity type in views_handler_field_entity->init()
Error after updating from 7.x-3.0-rc1 to rc3
Note not using reference either!
Anyone know whats causing it?
Comment #14
ldedecker CreditAttribution: ldedecker commentedAfter restoring prev version and database, clearing cachen reinstalling manually and clearing cache again, finally no more error with rc3, seems ok for me even if i'm not completely sure
I don't know why drush was refusing the update.
I'm using commerce, may be is there something with it.
Comment #15
bojanz CreditAttribution: bojanz commentedWithout providing a views export, there's no way for us to tell you what might be causing it. Keep that in mind.
Comment #16
Anonymous (not verified) CreditAttribution: Anonymous commentedSame error, not using Node Reference (I do have the latest dev version installed, but disabled), didn't appear to break anything.
Comment #17
dawehnerYou know it would be DEFINITIVE helpful if you could provide an export of the view. Additional you would do me a favor if it's a view you can import on any site.
Comment #18
Anonymous (not verified) CreditAttribution: Anonymous commentedHere's an export of my view.
Comment #19
ñull CreditAttribution: ñull commentedMeaning....? views rc3 will crash commerce? And commerce dev will fix it? Is that based on experience?
Comment #20
dawehnerWell if bojanz says this you should follow him :)
Comment #21
rhiss CreditAttribution: rhiss commentedReverting to 7.x-3.0-rc1 solved it, but i also didnt update the references module...
Comment #22
bojanz CreditAttribution: bojanz commentedCommerce 1.0 was made to work with Views RC1.
Commerce 1.1 (current 7.x-1.x-dev) is being made to work with Views RC3.
Right now Commerce works best with Views RC1, cause there's a query access bug that breaks some views when not viewed as an admin user with Views RC3.
So, for production Commerce sites, updating Views is not recommended. I would like to fix this bug today if possible, just need to catch a few people online ;)
There's are Views patches that can fix the problem at #1222324: Fix query access control on relationships (comments), but the current consensus seems to be to try and fix this at the Commerce side.
So, right now you can you use Commerce 7.x-1.x-dev with any Views version. However, soon we'll be committing patches that require Views RC3, leading to Commerce 1.1 that requires Views RC3.
Comment #23
BrightBoldI got this error on two different sites after running update.php even with the latest dev of References (10-10). As far as I can tell it's not causing any problems — my views using references seem fine.
Comment #24
dusov CreditAttribution: dusov commentederror on the update.php
and problem with Views content panes (ctools): Theme key "panels_onecol" not found.
Comment #25
alexiscott CreditAttribution: alexiscott commentedThis error message cold be related, as it's also a missing column with the .nid suffix.
Running 7.9 I'm getting this error in one of my views displays after the views upgrade: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_data_field_exhibition.nid' in 'on clause'
I tried upgrading references (node references), as well as ctools, and views slideshow, but it did not seem to make any difference - same error.
Comment #26
dawehner@arcX
Are you sure you updated references to the dev version and cleared the cache?
Comment #27
guillaumev CreditAttribution: guillaumev commentedSame issue as arcX here, besides that I had 2 debug messages (the same ones) appearing. I updated references and now one of them is gone, but the other one remains.
What's strange though is that I have, in the same view, a Block display and a Page display, displaying exactly the same data in the same way. After updating References, in the Page display, everything is fine, while in the Block display, the error is still there...
Comment #28
guillaumev CreditAttribution: guillaumev commentedNever mind, the issue was coming from a custom module of mine implementing hook_field_views_data that I needed to update.
For arcX: find the module responsible for your field_data_field_exhibition and, in this module, look for the function implementing hook_field_views_data. Then, do as in this commit http://drupalcode.org/project/references.git/blobdiff/80e59efe2a0a56ed8b... to fix the error...
Comment #29
alexiscott CreditAttribution: alexiscott commentedI'm good too: as dereine points out, and maybe I missed in the thread, it needs to be the dev version, and not the beta3 version that I was using.
Thanks for the help, and thanks too to guillaumev for his explanation, of what is going on under the hood.
Comment #30
bojanz CreditAttribution: bojanz commentedOkay, looks like we're good then.
Comment #32
BrightBoldHmm. I just got this error again on a site that didn't have References installed. So it does sound like there's another module that may be causing the same problem.
I went through all the views trying to see if any were broken and the only error I can find is a missing style plugin and a broken/missing handler error (that appears to be on the "delete" link) on a view called admin_user_user. Unfortunately, I don't know where this view came from (maybe someone here does? It seems to duplicate the People List view but with a Drupal-6-style path; I don't seem to have it on any of my other Drupal 7 sites) nor can I confirm whether it was broken before the upgrade. But here's an export:
If you think it's related and there's anything I can do to help track down its source, let me know.
Comment #33
bojanz CreditAttribution: bojanz commentedThat view comes from the admin_views module that is bundled with Admin menu.
You have an old version, which explains the problem with the missing style plugin (it's looking for pre-May 29th VBO).
Comment #34
BrightBoldAah thanks, that explains it. I will update.