Closed (fixed)
Project:
Protected Node
Version:
6.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
5 Dec 2008 at 02:30 UTC
Updated:
1 May 2011 at 03:02 UTC
Jump to comment: Most recent file
When a site search (search.module) is performed and a Protected Node is returned as part of the search, rather than displaying the list of nodes, protected_node fires off a redirect to the Password Protection---this prevents *any* search results from being returned.
One should be able to perform a search and have results returned without triggering the password.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | protected_node_search_result.patch | 794 bytes | ramlev |
Comments
Comment #1
Frank Steiner commentedI guess this shouldn't happen because no content is returned for the page when it is fetched from a cron run (although this doesn't work well), so that no content should ever be indexed. Hmm.
Comment #2
cyberwolf commentedSame issue here. Subscribing.
Comment #3
ramlev commentedI have made a patch, which fix the issue when trying to see search results when some of the nodes is password protected.
Comment #4
jadwigo commentedThe patch in #3 works.. a password protected node will still show the title but no text.
If you want to exclude the nodes from search results restricted search will offer a all or nothing solution
Comment #5
AlexisWilke commentedInteresting problem. 8-)
The search is fed empty data when the password is set on a node. However, if you create a node, the search indexes it, and then you add a password to that node, it obviously is going to be in the search index, no matter what.
Thinking about it, it seems that the db_rewrite_sql() is the solution for this one (and many others...)
See: #830016: db_rewrite_sql() misses protected nodes...
Thank you.
Alexis
Comment #6
AlexisWilke commentedOkay, the hook_init() was the solution on this one. The other things did not directly help.
It is fixed in 6.x-1.x for now. I'll wait a little before publishing 1.6.
Thank you.
Alexis Wilke
Comment #7
AlexisWilke commentedMeant to mark as fixed. 8-)