cancel
Showing results for 
Search instead for 
Did you mean: 

Search result dependant on Explorer's interface language?

olange
Champ in-the-making
Champ in-the-making
Hello all,

While evaluating Alfresco 3, we noticed that the full text search results within Alfresco Explorer Web Client depend on the language its interface is set to: it displays only documents whose locale matches the one of the interface.

Is this a configuration problem, a known bug or a feature?

We expected Alfresco to return all documents, independently of the language Alfresco Explorer's interface is set to when searching.

Within the user profile settings, the Content language filter being set to All languages. We observed the same behaviour with Firefox 3 and Internet Explorer 7.

Some details

What I call the «interface language» is determined by the Accept-Language header sent by the browser. If we change the browser options to accept en, fr (en first), we get the Alfresco Explorer interface is english. If we set the header to fr, en, we get the Explorer's interface in french.

And what I name the «document language» can be observed on the content property of our document nodes, within the Node Browser. For instance, contentUrl=store://2009/4/24/18/1/5dd40ccd-02b7-4a4e-9726-b6c50246a1e0.bin|mimetype=text/plain|size=294|encoding=UTF-8|locale=fr_CH_ shows the document's locale is fr_CH.

I came to the conclusion that if these locale do not match, documents are omitted in the results.

Steps to reproduce the above mentioned case

  1. set the browser Accept-Language option to fr,en

  2. reload Alfresco Explorer within the browser; the language of its interface switches to french

  3. upload a new document with the Alfresco Explorer, for instance a Word document or a text document

  4. search for some terms know to be present in these documents, they should be listed in the results

  5. set the browser Accept-Language option to en,fr

  6. reload Alfresco Explorer within the browser; the language of its interface switches to english

  7. do the same search as above, for some terms know to be present in these documents

  8. they do not show up in the search results anymore
We first noticed this problem while uploading documents thru a CIFS network attached drive, the documents' locale being automatically set to en_US in our case. Doing a full text search from the Alfresco Explorer interface set in french didn't return these documents; when set to english, all results were displayed.

Sorry for the long explanation. I hope I'm not too confuse.

Regards,
Olivier
3 REPLIES 3

olange
Champ in-the-making
Champ in-the-making
Hi all,

Rebuilding the indexes solved this issue: we added index.recovery.mode=FULL to custom-repository.properties and stopped/restarted Alfresco. Now all documents appear in the search results and these are not filtered anymore by Alfresco Explorer's interface language.

Regards,
Olivier

olange
Champ in-the-making
Champ in-the-making
A quick update, there is more to this point. I forgot to mention that we are testing with Alfresco Enterprise 3.0.1. At first glance, I observed that fully rebuilding the indexes solved the above described issue, but it was a mistake with my testcase, because it did'nt: our results where still dependant upon the language of our browser. To solve it, we also had to change the analyser class that Lucene uses to index content in french.

This involved the following change within the properties file WEB-INF/classes/alfresco/mode/dataTypeAnalyzers_fr.properties:


d_dictionary.datatype.d_text.analyzer=org.alfresco.repo.search.impl.lucene.analysis.AlfrescoStandardAnalyser
d_dictionary.datatype.d_content.analyzer=org.alfresco.repo.search.impl.lucene.analysis.AlfrescoStandardAnalyser

instead of:


# d_dictionary.datatype.d_text.analyzer=org.alfresco.repo.search.impl.lucene.analysis.FrenchAnalyser
# d_dictionary.datatype.d_content.analyzer=org.alfresco.repo.search.impl.lucene.analysis.FrenchAnalyser

and then rebuild the indexes (setting index.recovery.mode=FULL within our custom-repository.properties and stopping/restarting Alfresco).

Many thanks to Sylvain Perrot/SmartWave, our Alfresco Partner, as well as Philippe Dubois/Alfresco, that helped us to solve that issue.

Olivier

zoao
Champ in-the-making
Champ in-the-making
Very thanks Olivier, for putting here the solution to your problem, which helped to solve mine.
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.