Closed (fixed)
Project:
Search API
Version:
7.x-1.7
Component:
Views integration
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Jan 2012 at 17:06 UTC
Updated:
1 Aug 2013 at 08:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
urlaub commentedI can confirm this bug with:
Views 7.3.1
Serach API & Search views 7.1.0
Comment #2
harrrrrrr commentedconfirmed
Views 7.3.1
Serach API & Search views 7.1.0
Comment #3
garethhallnz commentedI too can confirm this problem.
I have attached a patch but it might be a bit of a hack.
Comment #4
tecjam commentedYeah, I have that too in my view.
Search API 7.x-1.x-dev
Views 7.x-3.1
Comment #5
egarias commentedThe patch #3 worked for me
Comment #6
hrodrig commentedI had the same error too... patch #3 worked
Comment #7
a1russell commentedCleaned up patch from #3 a bit.
Comment #8
a1russell commentedComment #10
davidseth commented#7 works Great! Thanks.
Comment #11
xlyz commentedit failed a test. shouldn't we investigate a bit?
Comment #12
robhardwick commentedI was still getting undefined index notices with patch #7 so I've modified the patch a little bit to fix the error. Updated patch attached.
Comment #14
FredericoT commentedI reworked the patch a little because the current patch assumes the 'type' is the first item in the array. I check all items to see which one is the 'type' and then use that value so it will still work even if it were the last item for instance.
See attached.
Comment #15
FredericoT commentedForgot to change the status it seems.
Comment #17
FredericoT commentedSorry, I used the wrong patch file. Just went for another cup of coffee, should be fine now.
Comment #19
hrodrig commented#17: search_api-1411712-17.patch queued for re-testing.
Comment #21
jmaties commentedsubscribing
Comment #22
netsensei commentedHm. This patch works for me! What else does the testbot want to be happy?
Comment #23
matrixlord commentedIt works fine for me too! Maybe something like coding standards...
Comment #24
Oleksandr.Masovets commentedThe #17 patch is not good. Reasons:
- please, respect Drupal code standards.
- if the $group['conditions'] exists, it is an array but there no "type" value in it the $filter value equals nothing. And it causes the "Call to a member function condition() on a non-object" errors in next piece of the code.
Comment #25
Oleksandr.Masovets commentedTry this one.
Comment #27
jsacksick commentedSometimes this error occurs for me, and this seems to be because of the features module. Can you try to enter the filter settings of your view. And simply click apply (With no changes), and save.
When I do this, the 'group' of my filter is updated and it works again.
Comment #28
dynamicdan commentedI don't have features installed and I still get this message. I do however have a slightly complicated view (2 filters as 'AND').
I suspect that the view rendering the page is not sending an arg/param through. Perhaps the arg is optional in the view GUI?
Pasting view and hoping it's useful:
Comment #29
drunken monkeyPlease, everyone, verify whether re-saving the view (as Jonathan suggests in #27) works.
Comment #30
FredericoT commentedIn my specific case it could not be related to features since I do not have the module installed. Re-saving the view does not seem to make a difference either.
Comment #31
drunken monkeyAnd you're using the latest versions of both modules (Views and Search API)?
Comment #32
FredericoT commentedI am currently using the latest versions of both modules.
My earlier patch no longer works in the latest versions, though the problem does seem to remain the same. The variable $group['type'] doesn't always exist in my case.
Comment #33
dynamicdan commentedBug is still there.
I did however notice a corrupted search index. I cleared the index and then re-indexed all content. This process was somewhat buggy. I had to do it twice.
Haven't seen error since but I suspect it will re-appear.
Comment #34
tinkalink commentedSame for me, no features module installed
Comment #35
modstore commentedI get this warning as well, with the latest versions of views/search_api.
Tried saving the views again, but no luck.
Comment #36
tinkalink commentedMaybe this might help someone:
I had a filter on field Indexed Node: Status to just have published nodes displayed. I removed the filter and saved the view. Problem resolved, and found it's still working after adding the filter on published nodes again!
Comment #37
Adysone commented#36 worked for me
Comment #38
brad.bulger commentedalso getting this error in 7.x-1.7. the "type" value it wanted looks like it should be "AND" or "OR". just opening up the "And/Or, Rearrange" form on the filters and hitting Save fixed it.
Comment #39
drunken monkeyOK, if this still appears, let's just apply the workaround/check. Patch attached, please see if it gets rid of the notice.
Still think there's some Views bug involved, too, but with the Views documentation being what it is, it's of course impossible to tell.
Comment #40
brad.bulger commentedi can confirm that this patch stopped the error that i was getting, in a view with a similar problem to #38. thanks!
Comment #41
drunken monkeyExcellent, good to hear. Thanks for testing!
Committed.