[FOLIO-1431] FOLIO snapshot-stable homepage and app bar has odd messages Created: 21/Aug/18 Updated: 12/Nov/18 Resolved: 21/Aug/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P2 |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Zak Burke |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Description |
|
Overview: folio-snapshot-stable homepage does not look normal Steps to Reproduce:
Expected Results: usually there's a "Welcome to FOLIO" message in the middle of the screen, plus the icons for the various apps at the top Actual Results: There's a "stripes-core.front.welcome" message instead, and component names for the various apps and buttons at the top. This also carries over into the various individual apps, e.g. vendor app. Additional Information: See attached screenshots |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 21/Aug/18 ] |
|
Per Zak: The labels are fixed. Settings > Organization > Language and Localization > Locale was set to German, but we don’t have many German translations in place, so all labels defaulted to the keys we use in the translation files. I set it back to English - United States. |
| Comment by Zak Burke [ 21/Aug/18 ] |
|
Settings > Organization > Language and Localization > Locale was set to German, but we don’t have many German translations in place, so all labels defaulted to the keys we use in the translation files. It would be prudent to investigate whether we can cause a particular locale, say, en-us (English - United States), when a value does not exist for a key in the active locale. |
| Comment by Ann-Marie Breaux (Inactive) [ 21/Aug/18 ] |
|
That makes sense to me, Zak Burke. Cate Boerema see this bug and the comments. Should we consider adding a default locale's text for the various components, if there's no translated value available from the chosen locale? |
| Comment by Zak Burke [ 21/Aug/18 ] |
|
Briefly looking into the option to "provide a value from a default-locale when no value is listed in the selected locale", it doesn't appear to be available without moving the default values back into the codebase. I didn't spend much time investigating, so I may have missed or misunderstood the options, but it doesn't appear to be a simple tweak. |
| Comment by Julian Ladisch [ 21/Aug/18 ] |
|
We have
|