Hi, i've used Lucene API since RC version. There's problem since RC7 version in my site, LuceneAPI can not index nodes which have been indexed before, even if the index files deleted.

After I created a node and run cron to index the node, LuceneAPI shows no result, although the node is indexed.

Now, I'm using RC6 because it is the working one for me.

Comments

cpliakas’s picture

Hi gantenx.

I am afraid that I cannot replicate the issue. A couple of major difference between RC6 and 1.0 is that the sable version correctly honors node access, and it does not index nodes that are unpublished. Also, versions RC7 and later use a different analyzer and require an uprade of ZF components and an index rebuild. I just re-tested indexing on a 1.0 installation with and without node access rules, and it worked exactly as expected. I need some more information before I can help you out.

  1. Can you confirm that you upgraded the ZF components>
  2. Can you confirm that you set your site to be reindexed in admin/settings/search before wiping the index files?
  3. Does the core search behave like you expect it to?
  4. Have you tried uninstalling RC6 and doing a clean install of 1.0?
  5. Can you confirm that the nodes you are trying to search have the correct access settings and are published?
  6. Have you tried searching the content as user 1? an annonymous user? users of other roles?
  7. Do you have Drush installed so you can confirm the actual number of documents in the index? You can also find this out by printing the output of luceneapi_index_size('luceneapi_node') somewhere in a custom function.
  8. Are there any log message indicating that an error is occurring in luceneapi or luceneapi_node?
cpliakas’s picture

Status: Active » Closed (fixed)

Closed manually after over 2 weeks of inactivity.

Dr Jay’s picture

Status: Closed (fixed) » Active

I'm reopening this issue as I believe it may be related to a permissions problem. lucene works flawlessly until I run cron, after which it seems to somehow affect the permissions in the lucenapi_node folder/files (in the files directory). Running chmod on this directory once again allows the index to be accessed, though this is impractical as it requires to much human intervention.

cpliakas’s picture

Category: bug » support
Priority: Critical » Normal

Hi Jay.

If you are having permissions problems, check the settings in the Search Lucene API settings page. Towards the bottom, you will see options that allow you to set the UNIX permissions for the index. Try messing around with these to see if you get the desired results.

Thanks,
Chris

Dr Jay’s picture

Status: Active » Closed (fixed)

How embarassing! Thanks for that ...

cpliakas’s picture

Haha. No problem! There are a lot of settings scattered over a lot of pages for this one module, so it is understandable that a couple can fall through the cracks. If anything else, you helped a bunch of people know this setting actually exists.

Thanks for posting,
Chris