Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Omnigator full-text uses hard-wired path to indexes #161

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments
Closed

Omnigator full-text uses hard-wired path to indexes #161

GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Set up a topic map source in tm-sources.xml with 
maintainFulltextIndexes=true and the directory in some other place than 
where Omnigator expects it to be. Omnigator will think the topic map has 
not been indexed, and offer to reindex it. The solution is to make 
Omnigator respect the directory setting on the topic map's source.

Original issue reported on code.google.com by lar...@gmail.com on 26 Nov 2009 at 12:44

@GoogleCodeExporter
Copy link
Author

Fixed by revision 693.

Original comment by lar...@gmail.com on 26 Nov 2009 at 2:04

  • Changed state: Verified

@qsiebers
Copy link
Member

#522 has brought up some more hardcoded index paths within omnigator

@qsiebers qsiebers added the Release5.4.0 Issues resolved in release 5.4.0 label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants