[LIVECOPY-158] Master Local must contain country suffix Created: 09/Sep/19 Updated: 01/Sep/20 Resolved: 01/Sep/20 |
|
| Status: | Closed |
| Project: | Live Copy |
| Component/s: | None |
| Affects Version/s: | 3.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jürgen Ulrich | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnolia 6.1 |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Epic Link: | Ext DAMs maintenance & partnership support |
| Description |
|
Hi Magnolia Team, just to let you know - we have an issue with Live Copy 3.1 and the masterLocale. For our client we have defined "en" as default masterLocale. Updating the fallback to en_INT (for international) or en_GB will cause a lot of redactional work. Our solution would be to implement a custom authoring support class to handle also language codes without the country suffix: Locale masterLocale = LocaleUtils.toLocale(masterLocaleString); Maybe this is also a valid scenario for other clients which want to use Live Copy. Thanks and best |
| Comments |
| Comment by Laura Delnevo [ 01/Sep/20 ] |
|
The issue is fixed on the released 6.2 version. As 6.1 is in its grace period, we won't fix this issue on this version as its reaching end-of-life (only critical and security issues are tackled at the moment for 6.1) |