Problem
On startup, the CX3 app is loading the list of supported languages from CX Server. Sometimes it fails and it leaves the app in a mostly broken state.
However, the popular "New translation" button that leads to the search feature remain available but the search feature itself is broken and triggers invalid instrumentation events as documented in T400463 and seen here.
Solution
Provide the list of languages to the app from SpecialContentTranslation.php. Take the list from cxserver/config/languages.yaml
Derived Requirement
Ensure that the CX3 app can properly handle scenarios where fetching the list of supported languages from CX Server fails. When this failure occurs, the app should instead load the list of languages from a fallback source provided by SpecialContentTranslation.php, which retrieves the list from cxserver/config/languages.yaml.
This prevents the app from entering a broken state and ensures that the “New translation” button and the search feature remain fully functional, avoiding invalid instrumentation events.
Test Artifact(s):
Test Steps
Test Case 1: Verify successful loading of languages from CX Server
- Launch the CX3 app.
- Observe the app initialization process.
- ✅❓❌⬜ AC1: Confirm that the list of supported languages is loaded successfully from CX Server when the server response is valid.
- ✅❓❌⬜ AC2: Confirm that the “New translation” button and search feature function normally.
QA Results - TestWiki
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T405000#11325525 |
| 2 | ✅ | T405000#11325525 |
