I have a node for iPaper, where I am uploading PDF's of my publication. These nodes, for some reason, stop the search index from running and stall cron out until it locks up and i have to go in and manually delete the cron_semaphore element to get it running again, and then it stalls back out.

I have installed Search_Config, and checked the iPaper node type for index exclusion, but it is still trying to index these node types. It seems this component is not working.

I am running Drupal 6.12, which I believe has updates to the DB layer? Is there an update for this module forthcoming, or is there a bigger problem here?

Comments

canen’s picture

canen commented

djudd,

Is the iPaper content type provided by CCK and if so what are the field types?

djudd’s picture

djudd commented

I don't believe it's CCK based. You can take a look at the module here:

http://drupal.org/project/ipaper

Essentially, it uploads a PDF (or other document types) to the Scribd service and then links to that document.

What I discovered is that it tries to place the full text of the document into the search database, which is just way too much information for a large file. I have turned off it's indexing of all text, and that solves my problem.

However, I was never able to use Search Config to exclude the node type.

ccshannon’s picture

ccshannon commented

Same here. Last week, a production site I work on, stopped indexing new content. Turns out there is a bug between Drupal core search module and this module.

Drupal indexes all nodes no matter what. Search config is supposed to tell the indexer not to index certain node types. This doesn't work.

The site in question uses an 'Editions' paradigm for homepage publishing, so there are at least 2 or 3 versions of the homepage every day. The unused editions get Unpublished and are not supposed to even be indexed.

Once I fixed the problem with real content not being indexed, by hacking the max number for the indexer up to 2000 from 500.

Now that the indexer is getting new content, it is also getting all the content that search config says it shouldn't.

This is critical. I'm going to have to hack core node to fix this site by hard-coding what nodes can and cannot be indexed.

What is the problem? Anyone?

ccshannon’s picture

ccshannon commented

I think this is the problem I am having with re-index:

#565232: little bug in validate function

jbomb’s picture

jbomb commented
Status: Active » Closed (fixed)

I agree that this issue was related to the re-indexing bug that has since been closed. Please re-open if the problem persists.

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented
Version: 6.x-1.x-dev » 6.x-1.6
Status: Closed (fixed) » Active

Hi,

It seems that this is still an open issue: I activated current version of this module for Drupal 6. I go to search administration, check the node types which should be excluded and click on "re-index". Then all setting for excluding nodes are deleted. Then I click again all node types and save. After running cron all settings are missing again, all checkboxes are empty and I can find every node type when I search.

Best,
Tobias

alan d.’s picture

alan d. commented
Status: Active » Postponed (maintainer needs more info)

The 6 branch is not longer officially maintained, but there were a lot of patches committed to the dev version. Do your problems persist when using this version? (Remembering to backup first, then update).

alan d.’s picture

alan d. commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

Closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.