Thorsten Scherler wrote:
El mar, 21-03-2006 a las 11:04 +0100, Jörn Nettingsmeier escribió:
Doug Chestnut wrote:
Actually Publication templating is broken atm. If one uses the "new
pub" usecase to create their pub, the index_manager_index.xconf doesn't
get created. This breaks the exit usecases for editing, uploading, etc
and gives an error.
We should remove the index usecase as exit usecases and come up with a
better approach (I think Thorsten mentioned triggers or some such
thing). Better to have a broken search index, then to not be able to
edit your new pub.
WDYT?
thumbs up for a clean long-term solution, but currently users can work
around the problem by creating an index.xconf manually, and they will
get an up-to-date index.
Is this working as well for templates pub? As I understood Andreas it is
not, so all that are using templating are not able to fix this.
Working fine in templates pub, at least for one of mine (as long as you
have index_manager_index.xconf setup.
The problem is the it isn't working without undocumented changes.
...or did I missunderstood you, Andreas?
if you remove the exit usecase, we won't be
able to use the index until somebody gets around to implement those
triggers...
Well, that is not true. You can still request the indexing usecase, it
only will not invoked after a document got edited/... (as exit usecase).
As workaround one can schedule the indexing every x minutes/hours/...
via the scheduler.
Or as I hope to do in my pub, just override the usecases in your own pub:
http://lenya.apache.org/1_4/reference/usecase-framework/index.html#Overriding+Core+Usecases+in+Publications
wdyt?
salu2
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
