Posted by electricmonk on October 22, 2008 at 2:40pm
Jump to:
| Project: | Restricted Search |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
Hi,
I've just installed this module, which I really need for a current project, and it seems like you've missed a way to perform those updates without relying on hook_cron... see here:
Before I make changes to the module, I would like to know whether you were aware of this method and chose not to employ it for some reason...
Cheers
Comments
#1
I think what you're suggesting is that the submit hook be used to ensure that the node isn't added to the index. The problem is that the actual indexing is done by cron, not when a node is submitted. So even if I used that hook, the node would be indexed on the next cron run.
Perhaps the submit hook could manually index the node then (would probably use a nodeapi hook instead), so it wouldn't be indexed by cron because it would all ready be in the table? Though I think the cron code would still be required to deal with changing indexing status from the content types page.
--Andrew
#2
I'm referring to the comment for hook_cron:
There actually IS a way to implement a callback from hook_form_alter, as is described in the link I've posted in my previous message; it would be possible to move all business logic related to marking a node as restricted / removing search indexes for a node to such a callback, methinks.
#3