+13Hi all,
Does anyone know how I can fix the translations after creating a different context and reordering the nodes?
After I reorder the nodes, IFS no longer translates the terms correctly, even after refresh the cache.
The translations under Text Translations are correct, but they don’t seem to be applied when using a context with reordered nodes.
Has anyone experienced this issue or knows how to fix it?
Thanks!
Global context without any change in navegatior design.
Hi. I found the following information -
In IFS Cloud, when you create a custom Navigation Context and reorder or restructure navigator nodes, the framework creates context-specific configuration overrides (CONFIG layer entries) for those nodes.
Even though the translations exist under Text Translations for the core layer, the reordered nodes in your custom context reference context-layer keys. Until the context layer is scanned and the language/navigator caches are fully refreshed, IFS defaults to the base English (Prog Text).
Prog Text (Base Text)Open your Navigation Context in the Navigator Designer.
Ensure the base label / Prog Text of the reordered nodes exactly matches the original core text (case-sensitive). If the base string was modified during reordering, the translation lookup key changes.
Because new context structures introduce context-level text entries, you must scan the configuration layer:
Navigate to Solution Manager > Setup > Translation > Scan Translatable Text (or Scan Configuration Texts).
Select Configuration / Custom Context as the target layer.
Run the scan job to register the newly reordered context nodes into the translation database.
Go to Solution Manager > Setup > Translation > Text Translations.
Search for the term(s) and filter by:
Main Type: NAVIGATOR (or CONFIG)
Module: FNDBAS (or relevant component)
Ensure the translated strings are populated for both the Core and CONFIG / Context layers for your target language(s).
Refreshing only the standard browser cache is often insufficient because navigator structures and translations are cached separately on the IFS Application Server:
Go to Solution Manager > Setup > Translation > Refresh Language Cache.
Run Refresh Language Cache for the affected language(s).
Go to Solution Manager > Setup > System Administration > Refresh Server Caches.
Select and execute Navigator / Context Cache and Dictionary / Language Cache.
Log out of IFS Cloud completely.
Clear your browser cache / local storage or open a fresh private/incognito session.
Log back in under the custom Navigation Context and switch to the target language.
I hope this information helps! Jane
+13Hi. I found the following information -
In IFS Cloud, when you create a custom Navigation Context and reorder or restructure navigator nodes, the framework creates context-specific configuration overrides (CONFIG layer entries) for those nodes.
Even though the translations exist under Text Translations for the core layer, the reordered nodes in your custom context reference context-layer keys. Until the context layer is scanned and the language/navigator caches are fully refreshed, IFS defaults to the base English (Prog Text).
Prog Text (Base Text)Open your Navigation Context in the Navigator Designer.
Ensure the base label / Prog Text of the reordered nodes exactly matches the original core text (case-sensitive). If the base string was modified during reordering, the translation lookup key changes.
Because new context structures introduce context-level text entries, you must scan the configuration layer:
Navigate to Solution Manager > Setup > Translation > Scan Translatable Text (or Scan Configuration Texts).
Select Configuration / Custom Context as the target layer.
Run the scan job to register the newly reordered context nodes into the translation database.
Go to Solution Manager > Setup > Translation > Text Translations.
Search for the term(s) and filter by:
Main Type: NAVIGATOR (or CONFIG)
Module: FNDBAS (or relevant component)
Ensure the translated strings are populated for both the Core and CONFIG / Context layers for your target language(s).
Refreshing only the standard browser cache is often insufficient because navigator structures and translations are cached separately on the IFS Application Server:
Go to Solution Manager > Setup > Translation > Refresh Language Cache.
Run Refresh Language Cache for the affected language(s).
Go to Solution Manager > Setup > System Administration > Refresh Server Caches.
Select and execute Navigator / Context Cache and Dictionary / Language Cache.
Log out of IFS Cloud completely.
Clear your browser cache / local storage or open a fresh private/incognito session.
Log back in under the custom Navigation Context and switch to the target language.
I hope this information helps! Jane
Hi
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.