Hi Joern,
Did you try the "New publication" usecase? When I make a new
publication [using the default pub as a template], the
indexing/searching works without having to make any manual config edits.
--Doug
Joern Nettingsmeier wrote:
hi felix!
your patience is much appreciated :)
Felix Röthenbacher wrote:
Jörn Nettingsmeier wrote:
Felix Röthenbacher wrote:
You have to configure the index in your publication. Please have
a look in the config directory of the default publication.
Additionally, you need a xxx2index.xsl for all your resourcetypes
xxx (see xhtml module).
hmm. i have a config directory beneath my publication, so that should
be used, right? or does this have to be in the default one?
No, it's your publication config directory.
ok. it's there, and i checked it.
index_manager_index.xconf looks ok to me.
This file contains the per publication configuration of the indexes.
You have to copy this file to your own publication (if not done
already) and modify it to suit your setup. You need to change the
index id both in the xconf xpath expression and in the
<index id="..." .../>. E.g. replace 'id="default-live"' with your
publication name plus area: 'id="yourpub-live"' (same for
'id="default-authoring"'). Additionally, you need to replace the
directory path of the index storage location. Here again, replace
the '../default/..' path name with you publication name.
it's also there:
<xconf remove="/cocoon/index_manager/indexes/index"
unless="/cocoon/index_manager/indexes/[EMAIL PROTECTED] = 'PolWiss-live' or @id
= 'PolWiss-authoring']" xpath=
<index analyzer="stopword_en"
directory="/home/POLNET/nettings/src/lenya-1.4.x/build/lenya/webapp/lenya/pubs/PolWiss/work/lucene/index/live/index"
id="PolWiss-live">
<structure>
<field id="url" type="keyword"/>
<field id="title" storetext="true" type="text"/>
<field id="description" storetext="true" type="text"/>
<field id="subject" storetext="true" type="keyword"/>
<field id="body" storetext="true" type="text"/>
</structure>
</index>
<index analyzer="stopword_en"
directory="/home/POLNET/nettings/src/lenya-1.4.x/build/lenya/webapp/lenya/pubs/PolWiss/work/lucene/index/authoring/index"
id="PolWiss-authoring">
<structure>
<field id="url" type="keyword"/>
<field id="title" storetext="true" type="text"/>
<field id="description" storetext="true" type="text"/>
<field id="subject" storetext="true" type="keyword"/>
<field id="body" storetext="true" type="text"/>
</structure>
</index>
</xconf>
but it still does not work.
message: index PolWiss-authoring doesn't exist
org.apache.cocoon.ProcessingException: Error calling flowscript function
executeUsecase at
file:/home/POLNET/nettings/src/lenya-1.4.x/build/lenya/webapp/lenya/usecases/usecases.js:282:-1
at <map:call> -
file:/home/POLNET/nettings/src/lenya-1.4.x/build/lenya/webapp/lenya/usecases/usecase.xmap:93:46
at <map:mount> -
file:/home/POLNET/nettings/src/lenya-1.4.x/build/lenya/webapp/lenya/usecase.xmap:56:128
at <map:mount> -
file:/home/POLNET/nettings/src/lenya-1.4.x/build/lenya/webapp/global-sitemap.xmap:303:105
at <map:mount> -
file:/home/POLNET/nettings/src/lenya-1.4.x/build/lenya/webapp/sitemap.xmap:531:110
cause: org.apache.cocoon.components.search.IndexException: message:
index PolWiss-authoring doesn't exist
this is really confusing, since i never know whether something is a file
path, a cocoon path or an xpath when i look at all those config files....
i checked for the pubs/PolWiss/work/lucene/ dir, it exists and contains
a subdir "index", but there is only one file in it:
[EMAIL PROTECTED]:~/src/lenya-1.4.x/build/lenya/webapp/lenya/pubs/PolWiss>
ls -l work/lucene/index/authoring/index/
total 4
-rw-r--r-- 1 nettings nettings 20 2005-12-01 15:06 segments
what i did not have was a local xhtml2index.xsl in the modules path of
my publication, but there is one in the server-wide default. just to be
sure, i copied it over, but it made no difference. is there any way to
create a lucene index on the command line? maybe this would help me
understand what's going wrong.
sorry for nagging you, but i really want to get this sorted out. it
looks very very stupid atm, because the error is triggered after every
edit, and i need have something going to pacify my supervisors by the
end of next week. :-D
best,
jörn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
