i'm having two issues with the 6dev version of search config. first, even though search queries return results, with the module enabled it always says that my site's indexing status is 0% indexed.

the other issue is searches for words in titles of nodes do return any results. i'm not sure this is directly an issue with search config, but thought i would see if others had run into the same problem.

thoughts? or am i the only one experiencing this problem?

Comments

canen’s picture

canen commented

Search config should't affect the *display* of the % indexed. And it doesn't mess with the search queries either.

masande’s picture

masande commented

i did a little more checking and my index is in fact not being rebuilt when the search config module is enabled. what was confusing me is that drupal is holding onto an old index i made before installing search config. from the re-index dialog:

"Searching will continue to work but new content won't be indexed until all existing content has been re-indexed."

any thoughts why search config (or otherwise) would prohibit my website from indexing on cron? i only have ~200 nodes at this time and no other technical problems i am aware of.

canen’s picture

canen commented

masande,

Please make sure none of your content types are checked to be removed from the search index. The setting is under the Advance search section.

masande’s picture

masande commented

thanks canen. that allowed the index to be repopulated.

that said, the only reason i want to use this module is to exclude content types from the search index. i have several feed content types. these only provide content to blocks via views. i don't want the raw feed data searchable. also, i have a couple of content types that are not available to all users. i'd like to use search config to keep anonymous users from discovering this info.

am i missing something or is this ability a key component of the module? is there a way to get this to work?

i appreciate your help.

masande’s picture

masande commented

sorry to bump, but i have a site i'd like to go live with but am stymied by content types that i don't want indexed. from the module description...

"There is also the option of selecting which node types not to index. Once selected they are also automatically removed from the advance search form. This gives more control over the content that can be searched to those who need it."

i fixed the indexing problems i was having by unchecking all the node types in the 'Search Index' section of the advanced search configuration options. however doesn't this render a key component of this module useless?

is there another way to realize this functionality or is this a true bug?

canen’s picture

canen commented
Status: Active » Fixed

This has been fixed in the latest release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

doublejosh’s picture

doublejosh commented
Version: 6.x-1.x-dev » 6.x-1.6
Status: Closed (fixed) » Active

Removing node types from the index does not work.

In my setup, I have one imported content type just used for node reference purposes (with out 6000 nodes) that still get indexed after it's been excluded in the search config admin area.

This thread was closed, but the probably seems to reamain.

PS: "Node types that should not be index by the search module" has a type-o.

doublejosh’s picture

doublejosh commented

I suppose this is the same as: http://drupal.org/node/462482
But still not avoiding indexing.

jbomb’s picture

jbomb commented

The module will not immediately exclude the content types from the search index. One must re-index the site after the content types are excluded.

I did try to reproduce the issue that you described, but didn't have any success. Below is a description of how I tested the module:

In my test instance I set up two nodes using the default node types in Drupal. Both the page node and story node contained the word "test."

All content types:
First I ran cron to index the site, next I searched for the word "test." I received both nodes in the result set as expected.

Pages indexed; Stories not:
Next I returned to my search settings and in the advanced panel excluded the "stories" content type. I then went through the process of re-indexing the entire site and ran cron. Again, I searched for the word "test" and received the expected result (the page node, but not the search node).

Stories are indexed; Pages are not:
I then returned to the search settings to re-enable stories and excluded pages. Next I re-indexed the entire site and ran cron. I searched for the word "test" and again received the expected outcome.

Custom content types:
Finally, I created a custom content type, and repeated the tests outlined above, which produced the expected outcome.

doublejosh’s picture

doublejosh commented

I suppose the problem could just in my (any admin's) understanding of what's going on. Since it has to push through all the potential nodes in order to find what should be indexed, the feedback on the search settings (admin/settings/search) page becomes unclear. I was assuming it was indexing all 6000 excluded nodes because the percent only creeped down as I processed through them.

However, I'm concerned they are getting indexed... since this query select * from search_node_links limit 10; brings back results like...

+------+------+-----+-----------------------------+
| sid  | type | nid | caption                     |
+------+------+-----+-----------------------------+
| 5965 | node |  13 | content construct kit cck   | 
| 5965 | node |  18 | filefield                   | 
| 5965 | node |  20 | imagefield                  | 
| 5965 | node |  21 | date                        | 
| 5965 | node |  12 | view                        | 
| 5965 | node |  14 | token                       | 
| 5965 | node |  15 | pathauto                    | 
| 5965 | node |  59 | path redirect path redirect | 
| 5965 | node |  44 | page titl                   | 
| 5965 | node |  66 | better format               | 
+------+------+-----+-----------------------------+

...which in my setup are the nodes that should NOT be indexed. (There is one node for each contrib module on Drupal.)

jbomb’s picture

jbomb commented
Status: Active » Closed (works as designed)

I apologize for the delayed response. This module was based on an article: Hiding content from Drupal's search system. It appears that this approach continues to index all site content, but intentionally excludes search results when a user performs a search using the search module. This takes place in the "hook_db_rewrite_sql" implementation.

It seems that completely excluding a content type from the search index is a core issue that is being discussed here: #111744: Add configuration to exclude node types from search indexing