[MGNLCTS-148] Include translation of properties which directly belongs to areas Created: 25/Nov/21 Updated: 26/Aug/22 |
|
| Status: | Open |
| Project: | Content Translation Support |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Carlos Cantalapiedra | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| 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)
|
||||
| Epic Link: | AuthorX Support | ||||
| Team: | |||||
| Description |
|
By now, translation module searches for the mgnl:template attribute to check the dialog associated for digging in and search for the properties which should be translated. Anyhow and tho is not aa good practice, its posible to associate a dialog to an area and create i18n attributes to it. Under this scenario, when the translation modules checks for the template attribute of the area and determines it doesn't have, it jumps to the next dialog so the properties are not translated. Attached a light-module with an example and some screenshots. |