Hi David,

Am 14.01.13 14:40, schrieb David Richter:
But..
The titles of the search results from external publications are not
displayed correctly and instead 'No Title' is displayed. Also the link
does not work.

The search results that have been found within its own publicationare
displayed correctly and also the link works. I think there is a problem
with the access to the content of external publications(?), cause the
content folder is located within the various publications.

Do you have any idea about this case?

I never actually used a cross-publication search index, so I think what you are describing is a bug. Would you mind filing a ticket? TIA!

-- Andreas



Thanks, David


2013/1/14 Andreas Hartmann <andr...@apache.org <mailto:andr...@apache.org>>

    Hi David,

    Am 14.01.13 10:10, schrieb David Richter:

        I still have a problem with the search across all publications.
        After I changed the path in the lucene_index.xml files for various
        publications, the search delivers no more results. I restarted the
        Tomcat already.The folder for the new path is created
        automatically in

        the file system and a file named 'segments' was created. In the
        original
        location (within the publications) are a few more files with the
        file
        extensions 'cfs' and 'del' and a file named 'deletable'... I
        don'tknow
        how the files were created. I've noticed that the content of the
        folder
        determines which search results are displayed.

        Is there maybe a script that I have to start, so that all
        required files
        are generated? Or do I have to edit another configuration file?


    in the "File" menu, you should find an entry "Re-index site" (or
    similar). Can you try that? You'll probably have to do it for all
    publications.

    -- Andreas



        2013/1/9 Andreas Hartmann <andr...@apache.org
        <mailto:andr...@apache.org> <mailto:andr...@apache.org
        <mailto:andr...@apache.org>>>


             Hi David,

             Am 09.01.13 15:24, schrieb David Richter:

                 I am very new to Lenya and hope you can help me. I use
        Lenya in
                 version
                 2.0.4 on an Apache Tomcat 6.0.36 server and I have two
        questions
                 about
                 the search function of Lenya.

                 First
                 Is there a way to change the search function, so that
        the 'wildcard
                 search' also works without wildcards (without Java
        programming)?
                 As if
                 we were always search with using wildcardsat the end.

                 For example: The search for "devel" would then deliver
        words like
                 "developer" as a result. This currently only works with
        the use of
                 wildcards... like this --> "devel*"


             I doubt that this is possible without writing any code.
        Lenya uses
             Lucene for searching, with the standard Lucene query syntax.

        
http://wiki.apache.org/lucene-____java/LuceneFAQ#What___wildcard___search_support_is___available___from_Lucene.3F
        
<http://wiki.apache.org/lucene-__java/LuceneFAQ#What_wildcard___search_support_is_available___from_Lucene.3F>


        
<http://wiki.apache.org/__lucene-java/LuceneFAQ#What___wildcard_search_support_is___available_from_Lucene.3F
        
<http://wiki.apache.org/lucene-java/LuceneFAQ#What_wildcard_search_support_is_available_from_Lucene.3F>>

             A simple workaround might be to use JavaScript to wrap each
        search
             term in wildcards before submitting the search form.


                 Second
                 For me, the search currently only works within a
        publication. Is
                 there a
                 way to search across all publications (also without Java
                 programming)?


             This should be possible by configuring a shared search index
             directory in all publications:
        <pub>/config/search/lucene-____index.xml.

             More info:
        
http://lenya.apache.org/____docu20/tutorials/____newPublication14.html#N100C5
        
<http://lenya.apache.org/__docu20/tutorials/__newPublication14.html#N100C5>


        
<http://lenya.apache.org/__docu20/tutorials/__newPublication14.html#N100C5
        <http://lenya.apache.org/docu20/tutorials/newPublication14.html#N100C5>>

             Basically, instead of using the path

                lenya/pubs/$MYPUB/work/lucene/____index


             you could use something like

                /var/lenya/lucene/index

             I would recommend to store all data (content, access
        control data,
             search index) outside the web application directory anyways.

             HTH,
             -- Andreas

             --
             Andreas Hartmann, CTO
             BeCompany GmbH
        http://www.becompany.ch
             Tel.: +41 (0) 43 818 57 01
        <tel:%2B41%20%280%29%2043%20818%2057%2001>
        <tel:%2B41%20%280%29%2043%__20818%2057%2001>



        
------------------------------____----------------------------__--__---------
             To unsubscribe, e-mail: user-unsubscribe@lenya.apache.____org
             <mailto:user-unsubscribe@__lenya.apache.org
        <mailto:user-unsubscr...@lenya.apache.org>>

             For additional commands, e-mail: user-h...@lenya.apache.org
        <mailto:user-h...@lenya.apache.org>
             <mailto:user-help@lenya.__apache.org
        <mailto:user-h...@lenya.apache.org>>




    ------------------------------__------------------------------__---------
    To unsubscribe, e-mail: user-unsubscribe@lenya.apache.__org
    <mailto:user-unsubscr...@lenya.apache.org>
    For additional commands, e-mail: user-h...@lenya.apache.org
    <mailto:user-h...@lenya.apache.org>





---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org
For additional commands, e-mail: user-h...@lenya.apache.org

Reply via email to