Unknown field in filter clause: status. [#1278780]

I've updated the search_api module to dev version, because I need the node_access check functionality. After that, when I try to search for something as anonymous user, I get the error message »Unknown field in filter clause: status.«. When I'm logged in with uid 1, everything works fine. As server type I use search_api_db and a view with FullTextSearch filter as an exposed filter in a block.

I attach an exported feature of the search server, index and view, so you can check my settings.

Comment	File	Size	Author
#14	1278780--node-access-published-14.patch	3.54 KB	dawehner
#13	1278780--node-access-published-13.patch	3.53 KB	drunken monkey
#10	1278780--node-access-published-9.patch	1.54 KB	drunken monkey
#8	1278780-search_api-field-access-force-status.patch	1.74 KB	dawehner
#6	1278780-search_api-field-access-force-status.patch	1.42 KB	dawehner
	search_feature.tar_.gz	2.52 KB	mhh

Comments

Comment #1

mhh commented 14 September 2011 at 11:21

Category:

bug

» feature

Ok, I found the reason for this error.
When you enable the Node Access alteration in the workflow tab in the Search Index settings, you also have to enable »Published« in the fields tab.

Maybe it is possible to implement some functionality, that enables the Published option automatically as soon as the Node Access alteration is enabled.

Comment #2

drunken monkey

he/him

German

Vienna, Austria

commented 14 September 2011 at 12:37

Component:	Database search	» Framework
Issue tags:		+D7 stable release blocker

Ah, of course! Sorry, was silly to overlook that. I don't have time to look into this right now, but will think of a way to alleviate this through some notes, or even fix it automatically as you say.

Comment #3

dawehner

German

commented 14 September 2011 at 12:39

One way to do it would be perhaps to set $index->options['fields']['status'] = 1 on configurationFormSubmit.
Does this make sense?

Comment #4

drunken monkey

he/him

German

Vienna, Austria

commented 14 September 2011 at 13:26

Yeah, it would probably be the best solution. The thing is hard-coded for nodes anyways, so some additional customizations don't matter, I guess. (The last key is 'indexed', not 'status', though.)
And we should also append this to the notes saying that you have to have the „Node access information“ field indexed for this to work, and likewise add it to the corresponding checks in the query alter hook.

(Oh, and fix the watchdog constant on line 1264 of search_api.module – oops!)

Comment #5

dawehner

German

commented 14 September 2011 at 17:21

Assigned:

Unassigned

» dawehner

Assign to myself, hopefully i will find time tonight.

Comment #6

dawehner

German

commented 14 September 2011 at 23:39

Assigned:	dawehner	» Unassigned
Status:	Active	» Needs review

Status	File	Size
new	1278780-search_api-field-access-force-status.patch	1.42 KB

Okay here is a short patch which automatically alters the index.

Did i already said that i like the clean-code of searchapi ?

Comment #7

drunken monkey

he/him

German

Vienna, Austria

commented 15 September 2011 at 13:19

Status:

Needs review

» Needs work

This goes in the right direction, but fails to check whether the Node access data alteration was enabled. Like it is, this will set the „Published“ field to „indexed“ every time the „Workflow“ form is submitted.
You'll additionally have to check whether the data alteration was previously disabled but now enabled in the form – only in this case do we automatically set the fields added by the data alteration to „indexed“ as well.