Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
I'm getting this notice error often, also shows up after an update.php process has completed:
Notice: Undefined index: entity type in views_handler_field_entity->init() (line 44 of /home/account/public_html/drupal/sites/all/modules/views/handlers/views_handler_field_entity.inc).
Comment | File | Size | Author |
---|---|---|---|
#7 | views problem.png | 25.85 KB | deanflory |
Comments
Comment #1
damiankloip CreditAttribution: damiankloip commentedDo you have an export of your view you can attach?
Comment #2
deanflory CreditAttribution: deanflory commentedWell, it's happening on the landing of a successful update.php process completing, which doesn't have any of my views on it. The only thing I can think of is there is a countdown module (Maintenance Countdown 7.x-1.x-dev) that appears to have modified the look of maintenance/site offline page(s) as well as the update.php pages. Or it may be AdaptiveTheme.
Comment #3
esmerel CreditAttribution: esmerel commentedCan you try using a core theme or disabling one at a time to narrow that down, maybe?
Comment #4
esmerel CreditAttribution: esmerel commentedComment #5
deanflory CreditAttribution: deanflory commentedI'm still getting these, going to try recreating all my views one at a time to see if it goes away.
Notice: Undefined index: entity type in views_handler_field_entity->init() (line 44 of /.../drupal/sites/all/modules/views/handlers/views_handler_field_entity.inc).
• Notice: Undefined index: entity type in views_handler_field_entity->init() (line 44 of /.../drupal/sites/all/modules/views/handlers/views_handler_field_entity.inc).
• Notice: Undefined index: users in views_handler_field_field->access() (line 127 of /.../drupal/sites/all/modules/views/modules/field/views_handler_field_field.inc).
• Notice: Undefined index: users in views_handler_field_field->access() (line 127 of /.../drupal/sites/all/modules/views/modules/field/views_handler_field_field.inc).
• Notice: Undefined index: users in views_handler_field_field->access() (line 127 of /.../drupal/sites/all/modules/views/modules/field/views_handler_field_field.inc).
Comment #6
ycshen CreditAttribution: ycshen commentedI think this bug is duplicate the #1950762: Breaks when adding "sign-up" link to view
It's a real bug.
Comment #7
deanflory CreditAttribution: deanflory commentedWhen doing module updates it shows up after update.php runs and reports the results, and I'm using the Seven admin theme and there are no signups in any way on the udpate.php results page:
SEE IMAGE
Comment #8
deanflory CreditAttribution: deanflory commentedStill having this issue but still have not tried recreating my views.
Comment #9
VValdo CreditAttribution: VValdo commentedFWIW, enabling the Entity API module, then removing and readding the signup to the view seems to have quieted this error down. Looks like the signup module should be checking for entity API module as a dependency or something.
Comment #10
saltednutWe're seeing these (or similar) during the normal install process of install profiles. Using latest dev of views. It just shows up during the batch and nothing seems broken from my observations.
Comment #11
BassPlaya CreditAttribution: BassPlaya commentedHey guys, I just found this thread (issue) here because I had the same. I don't think it is related to the signup module but probably related to 'exposed filters'. I had this view with 3 exposed filters and I got 3 error messages on that page view.
I thought that was strange and deleted the filters. Saved the view. Cleared the cache. Nothing happened. So I added them back in and then the errors disappeared. So I guess you might wanna look into exposed filters.
FYI: the 3 exposed filters were: 2 fields based on a select list, and a filter based on the user role.
Hope that helps.
Comment #12
BassPlaya CreditAttribution: BassPlaya commentedEr ... it seems that I do get those errors back when I've just edited my view (a VBO) but after refreshing the page, they're gone. (for now)
Comment #13
siramsay CreditAttribution: siramsay commentedI am getting the same on one of my development install, not happening on production.
views 7.x-3.8
I get it when flushing cache on and on running update.php
Comment #14
saltednutAlthough I agree this is hard to reproduce, it's still really happening at times. I often see it on Features pages and it happens literally every time I install Views.
Comment #15
rcodina CreditAttribution: rcodina commentedI also reproduce the problem with this configuration:
Drupal 7.34
Ctools 7.x-1.6
Views 7.x-3.10
Entity 7.x-1.6
Entity tokens 7.x-1.6
Entity Reference 7.x-1.1
Multiple Entity Form 7.x-1.2
Comment #16
hoosk CreditAttribution: hoosk commentedMe and @rcodina have found out that this problem is caused by Simplenews module (7.x-1.1) which makes following variable to be empty:
$table_data['table']['entity type']
To know which module causes this problem we have added an if with a dsm instruction. Also, to workaround the problem, we have added an if with !empty function.
Comment #17
rcodina CreditAttribution: rcodina commentedI think views module should be patched to add the if with the "empty" function to avoid problems like this one. This time is simplenews module, next time can be another module. So this should be handled in views module. It's just and if sentence.
Comment #18
DarrellDuane CreditAttribution: DarrellDuane commentedhttps://www.drupal.org/node/2331209 will likely fix the issue listed in #5.
Comment #19
CmKeen CreditAttribution: CmKeen commentedThe issue is indeed in Simplenews that don't set the right element but it seems that the bug has not been resolved in Simplenews yet.
Did anyone found a patch in Simplenews?
Comment #20
UksusoFF CreditAttribution: UksusoFF commentedI just updated to 7.x-3.15 and got same error when database update. Should I re run update after this error? Or any manual work in SQL?
Comment #21
delacosta456 CreditAttribution: delacosta456 commentedhi @CmKeen
Effectively it looks like it concern simplenews .. and on my own side below is what has help (hope it is definitely):
- On your content type , delete the field_simplenews_term
-On content type at /admin/structure/types/manage/(your-content-type) in the Publishing options tab, UNCHECK Use as simplenews newsletter and save
(active tab)
- drush cc all (clear all cache) (twice)
- Go back to /admin/structure/types/manage/(your-content-type) in the Publishing options tab, AND RE-CHECK Use as simplenews newsletter and save..
- drush cc all (clear all cache) (twice) to verify error has gone
thanks
Comment #22
GemQueen CreditAttribution: GemQueen as a volunteer commentedI just started getting this problem on two websites after updating Views to the latest. Neither one have SimpleNews installed.
Comment #23
jukka792 CreditAttribution: jukka792 as a volunteer commentedI just started getting this problem on one site in a multisite installation after running update.php. Updated these modules using Drush:
imce 7.x-1.10
jquery_update 7.x-3.0-alpha5
l10n_update 7.x-2.1
s3fs 7.x-2.10
views_bulk_operations 7.x-3.4
(Views module version is 7.x-3.15 (didn't update it yet to the latest version which is now 7.x-3.16)
Also I do not have SimpleNews installed.
Comment #24
taylormadeapps CreditAttribution: taylormadeapps commentedI rolled back views_bulk_operations 7.x-3.4 to 7.x-3.3 as this was the only upgraded module on my sites that matched with @jukka792 the warning is no longer presented to me after the rollback.
I hope this is of some help
Comment #25
Agileware CreditAttribution: Agileware commented> I rolled back views_bulk_operations 7.x-3.4 to 7.x-3.3 as this was the only upgraded module on my sites that matched with @jukka792 the warning is no longer presented to me after the rollback.
@taylormadeapps you're a legend mate! That worked for me.
Comment #26
dat deaf drupaler CreditAttribution: dat deaf drupaler as a volunteer commentedConfirmed rolling back from views_bulk_operations 7.x-3.4 to 7.x-3.3 had stopped this error -- D7 running on 7.0 PHP
Comment #27
INAScon CreditAttribution: INAScon commentedI haven't upgraded to views_bulk_operations 7.x-3.4 yet and have this same issue in 7.x-3.3.
Comment #28
joelpittetCan you try the dev release?
Comment #29
joelpittetIt's a full release now in 3.5.
Please provide a clear set of steps to reproduce the problem
Comment #30
dat deaf drupaler CreditAttribution: dat deaf drupaler as a volunteer commentedThe error and warning haven't appeared since then... can close this issue if another person could confirm?
Comment #31
joelpittetThank you for letting me know.
Comment #32
dat deaf drupaler CreditAttribution: dat deaf drupaler as a volunteer commentedThis issue had came back and been linger around for couple months before I found this patch which solved this issue.
https://www.drupal.org/project/views/issues/1364064#comment-12589172