Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jun 2014 at 19:17 UTC
Updated:
28 Jan 2018 at 15:35 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jhedstromThis resolves the issue in my testing.
Comment #2
lendudeThis also occurs if you have a display with overridden fields and a not overridden combined fields filter where some of the fields that are used by the filter have been removed by the override.
Easy to reproduce with just Views 3.8 and D7 Core and the following View (no field access modules needed):
On the URL test-combined-field-filter/bugged you will get the error
Patch applied cleanly and solved the bug.
Maybe update the comment in the patch to reflect that multiple scenario's can cause the field to not be available?
Len
Comment #3
pratip.ghosh commentedWorked for me too.
Comment #4
inteja commentedDitto. Worked for me also. Thanks!
Comment #5
mlzrWhen I clicked on a node (so just viewing as user1/admin) then I had error:
Fatal error: Call to a member function ensure_my_table() on a non-object in /home/techniek/public_html/sites/all/modules/views/handlers/views_handler_filter_combine.inc on line 60
So my case was somewhat different from the ones in this issue. Bud I applied the patch and the error is gone!
Thanks!
Comment #6
kscheirerI had the same error as marchellodepello, patch in #1 solved it for me as well.
Comment #7
joelpittet+1 to this patch, it's working well for me.
Comment #8
agileadamPatch #1 worked for me as well. Thank you!
Comment #9
anouTout pareil : Patch #1 worked for me as well. Merci ! :-)
Comment #10
hargobindConfirming that this patch fixes the scenario in #2.
Comment #11
jhedstromCurious if anybody knows what the process for ensuring fixes like this make it to Drupal 8 is?
Comment #12
joelpittet@jhedstrom best approach that I know:
To get it in faster... write a test that proves the bug, preferably UnitTest but WebTest can do the trick. Post the tests only and have testbot fail and then the combo(tests+fix) showing it fixes the issue.
All assuming this bug still exists in D8.
Comment #13
lendudeOpened a D8 issue for this with a port of patch in #1 with added testing.
Comment #14
lendudeOk the referencing is smart enough, so didn't have to add it here
Comment #15
geresy commentedPatch #1 worked for me. I encountered it with dev, the recommended release doesn't throw errors.
Comment #16
dawehnerThat totally makes sense. Committed to 7.x-3.x and pushed
Comment #17
jibranThis is the commit to D7 http://cgit.drupalcode.org/views/commit/?id=d7837bc
Form
\Drupal\views\Plugin\views\filter\Combinein D8So it seems it's already fixed.
Comment #18
lendudeYeah this was fixed for D8 in #2370251: Removed fields in Views Combined Filter setting lead to Fatal error.
Comment #20
arebacollins commentedHaving a strange recurrence of the same on views 7.x-3.11 and specifically on views field view , both dev and 7.x-1.1 versions. I tried applying the patch to views but nothing changes.
Strangely, I get this error on about 8 node items of a 46 nodes custom content type, started arbitrarily, and randomly around the time I was playing with openlayers. Since then has not resolved.
Comment #21
capfive commentedthis was a rare case for me, I am using Views Field View which allows you to embed another view within a view...
Long story short, I deleted the view that was being embed and didn't remove it from master view... just in case someone rolls into this problem!
Comment #22
RAWDESK commentedokay, patch worked for me also
Comment #23
robgreeniowaThis error showed on a logged-in Drupal user's view page (it was a table of nodes, using a combined filter as a 'searchbox of sorts'). Only her computer - I couldn't reproduce. Simply deselecting all the fields in the combined filter caused her error to go away. I was able to re-select those fields, and the error message didn't come back. Hopefully this quick fix saves some of you some time.
Comment #24
kscheirerThis issue is closed. If that's an error and there still is the original issue, please re-open this issue. If there is a different problem, please open a new issue. It's unlikely anyone will see comments on a closed issue.
Comment #25
drupal_8_tterm commentedSorry a stupid question, but how exactly do you apply this patch? Do you make a new file? If so what is the name of that file and if not where do I include the code of the patch in my views_handler_area_text.inc - file? Or do I include it even into a different file?
Thank you very much in advance!
Comment #26
lendude@Drupal_8_TTerm you don't need to apply this patch, this was fixed in Drupal 7 Views and Drupal 8 core. So if you still run into this on an up-to-date install, please open a new issue for this.