restricting retroactively
WorldFallz - October 16, 2007 - 21:03
| Project: | Restricted Search |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | rconstantine |
| Status: | closed |
Description
is the module supposed to be form-altering the advanced search form? I still see content types listed there that I have blocked. I installed & enabled the module, set block/enable for all my content types, then reindexed the whole site. Is there something else I need to do (there wasn't a readme.txt)? Do I need to customize the form myself?
Great MODULE-- i was trying to figure out how to do this myself when I found it-- gonna save me a lot of time. Thanks.
#1
It currently doesn't alter the advanced search form - but that's a good idea to implement. If you block a content type, you could still search for it, but no results would be found.
--Andrew
#2
This patch may need to have its file references adjusted. Or just do it by hand since it is small. This includes the other patch I submitted as well.
This patch removes the options from the advanced menu for content types which have been blocked.
#3
+1
#4
Thanks!
I've tested this out and looks good. I had to add a line for the advanced search form to handle dealing with cases where the form element doesn't all ready exist. I've committed this to CVS.
--Andrew
#5
#6
Yep. I caught that on mine too. I think I just wrapped the whole thing in an 'if' testing the first element of the subsequent 'foreach'.
#7
Changed to active. Not sure issue is fixed.
Just installed today. Specifically using restrict mod with Job Search mod including both jobs and resumes types. Installed, restrict mod, enabled and edited content type resumes to restrict search, re-indexed and ran cron. Performed search on a resume node and it still comes up in basic results.
Note: Resume node was already indexed prior to installing your mod but not restricting retroactively. Any idea how to work with re-indexing?
Drupalgirl
#8
I ran the re-index and the cron twice and it seems to work. Running once does not do the trick.
#9
IIRC reindexing happens in chunks so the server doesn't time out. There may be a setting somewhere. So it could take more than two runs of cron, depending on the number of nodes. But I could totally be wrong on that.
#10
Settings for reindexing are at admin/settings/search
#11
Yes, the module can do things in chunks if the script times out. You can look in the database table to see which nodes still have the 'dirty' flag set.
Closing this issue. Next time if you have a problem that is not likely related, please open a new issue instead of changing the subject of an existing issue.
--Andrew