[MGNLCTS-147] I18n fields coming from prototype dialog not added to translations Created: 28/Oct/21  Updated: 18/Oct/22  Resolved: 10/Jan/22

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.3.1, 2.5.4
Fix Version/s: 2.5.5

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Thuy To
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 10.25d
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: AuthorX Support
Sprint: Global Maintenance 4, AuthorX 1
Story Points: 5
Team: AuthorX

 Description   

Steps to reproduce

  1.  Configure a template prototype which sets a dialog with i18n fields (You can use DEMO author prototype.yaml from the demo)
  2.  Create a page/component which uses such dialog (must come from the prototype, DEMO author categoryOverview page page template works on the demo, as long as you remove the dialog line on the yaml file)
  3. Fill the i18n fields (from page properties is enough)
  4. Export that page translations

Expected results

I18n fields appear on the exported file

Actual results

Any i18n field coming from a dialog defined on a template prototype won't appear on the exported file.

Workaround

Development notes



 Comments   
Comment by Roberto Gaona [ 29/Oct/21 ]

Reproducible on latest version and on core translations module.

Moving to Content Translation Support.

Generated at Mon Feb 12 00:33:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.