[MGNLCTS-10] Introduce support for tag's dialogs Created: 07/Oct/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0.x

Type: Improvement Priority: Neutral
Reporter: Zdenek Skodik Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
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)
Date of First Response:

 Description   

At the moment only dialogs of template/paragraph definitions are taken into account. But if one uses cms tags in her scripts (i.e. <cms:editButton>), such content is not exported for translations so that your only chance is to provide a custom /modules/content-translation-support/config/nodeDataToTranslateFinder.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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