Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] indexing string resource values during import is incorrect #1709

Closed
tusmester opened this issue Jun 28, 2022 · 0 comments
Closed

[Bug] indexing string resource values during import is incorrect #1709

tusmester opened this issue Jun 28, 2022 · 0 comments
Assignees

Comments

@tusmester
Copy link
Member

tusmester commented Jun 28, 2022

When a content is created early in the import process (e.g. all CTDs), before string resources under /Root/Localization are imported, all string resource fields (mainly DisplayName) are indexed incorrectly: an empty value is indexed. This is true for all regular content items too that are imported before string resources (e.g. under /Root/Content in snaas).

In case of DisplayName this affects sorting on the UI, which is a major issue.

Current empty index document for IMPORTED CTD display names

{
  "Name": "DisplayName",
  "Type": "StringArray",
  "Value": [""]
}

Correct value (created on the UI)

{
  "Name": "DisplayName",
  "Type": "StringArray",
  "Value": ["mytesttypeenglish","mytesttypegerman"]
}

This happens in LowerStringIndexHandler.GetIndexFields: the method SenseNetResourceManager.Current.GetStrings returns an empty string array, because there are no string resources yet.

Solution

  • We may have to memorize and reindex all content items that have fields containing string resources.
  • Import string resources immediately after CTDs and settings? We still have to reindex ctds, but that is acceptable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants