Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-4963

Share does not honor locale on file content upload

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Resolution: Duplicate
    • Affects Version/s: 3.4
    • Fix Version/s: 3.4.4
    • Component/s: Installer, JLAN, L10N
    • Labels:
      None
    • Environment:
      Linux Squeeze, Linux Ubuntu 10.04 (32 bits), Ubuntu 10.10 (64 bits), Tomcat 6
    • Bug Priority:
      Category 1
    • Testcase ID:
      Hide

      Start tomcat with language spanish (LANG=es_ES).

      Go to Share in spanish and upload a file, go to node browser and check the node content's locale it is spanish, so far so good.

      Go to Share in french and upload a file, go to node browser and check the node content's locale, it is spanish, but french is expected.

      Show
      Start tomcat with language spanish (LANG=es_ES). Go to Share in spanish and upload a file, go to node browser and check the node content's locale it is spanish, so far so good. Go to Share in french and upload a file, go to node browser and check the node content's locale, it is spanish, but french is expected.

      Description

      There seems to me that there are several issues related to lucene indexes and localisation, especially in share (most of them due to the probably correct, but unexpected, mechanism of "localised search"). But I'll try to go step by step in each of the issues that are leading to the various problems.

      Whatever language you're using Alfresco Share in the uploaded content always gets the locale that the repository's JVM is running in. Share as a remote client for the repository does not honour the locale when uploading the file, so does FTP and presummably IMAP, CIFS and NFS (not tested). Probably in those clients there is no way of specifying the locale, don't know, but obviously, as Share offers and internationalized interface it should manage to ask the repository to maintain its locale.

      I think this is critical because this is the beginning of many indexing and searching problems. For share users all content gets indexed in just one language, which may or may not be the correct one depends on tomcat configuration. So when searching, clients in other languages don't find anything. I think there is something more than the share issue in this problem, but obviously this is part of the problem.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedissues Closed Issues
                  Reporter:
                  iblanco Igor Blanco
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel