Bug #10173

Treeview quicksearch does not support i18n culture fallback

Added by Dan Gillean almost 4 years ago. Updated almost 3 years ago.

Status:VerifiedStart date:08/03/2016
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:I18N
Target version:Release 2.4.0
Google Code Legacy ID: Tested version:2.1.2, 2.2, 2.2.1, 2.3
Sponsored:No Requires documentation:

Description

First reported in the user forum - see for example: https://groups.google.com/d/msg/ica-atom-users/iLTunA11wVs/BL2LaillBwAJ

To reproduce:

In a site with a default culture of English:

  • Create a new description with children - e.g. Foo 1, Foo 2, Foo 3
  • Flip the interface to French (or another culture), and add translations to some of the children - esp. to title, e.g. Bar 1, Bar 2. Leave at least one without a translation
  • Flip back to English and perform a quicksearch via the Treeview search tab for "Bar" - Foo 1, Foo 2, Foo 3 are returned (okay)
  • Flip to French and perform a search for "Foo"

Resulting error

  • Foo 3 (e.g. the one with no french translation) is returned in the french quick search results interface as "null"
  • No culture fallback is in place when a title is not available in the requested culture

Expected result

  • Foo 3 is returned as "Foo 3" when no french title is available and the French interface is used for the search.
  • Culture fallback is in place in the quicksearch results.

I haven't tested yet in 2.3 but AFAIK we haven't done any work in this area; I expect the same results.


Related issues

Related to Access to Memory (AtoM) - Bug #3274: 'Add new' text not i18n in dialog.js & multiRow.js New

History

#1 Updated by Jesús García Crespo almost 4 years ago

  • Related to Bug #3274: 'Add new' text not i18n in dialog.js & multiRow.js added

#2 Updated by Dan Gillean almost 4 years ago

  • Tested version 2.3 added

Now tested and reproduced in 2.3 as well.

#5 Updated by Nick Wilkinson over 3 years ago

  • Assignee set to José Raddaoui Marín
  • Target version set to Release 2.4.0

Hi Radda, can you please look into this?

#6 Updated by José Raddaoui Marín over 3 years ago

  • Status changed from New to Deploy
  • Assignee changed from José Raddaoui Marín to Nick Wilkinson

This is already fixed in qa/2.4.x and in deploy for #10975

#7 Updated by Nick Wilkinson over 3 years ago

  • Status changed from Deploy to QA/Review
  • Assignee changed from Nick Wilkinson to Dan Gillean

Hi Dan, assigning to you for either QA or Verify.

#8 Updated by Dan Gillean about 3 years ago

  • Assignee deleted (Dan Gillean)

#9 Updated by Kelly Stewart almost 3 years ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF