[EXCONTRANS-359] propertiesToTranslateFinder should be AdaptivePropertiesToTranslateFinder for Blossom compatibility Created: 17/Dec/21 Updated: 12/Jan/22 Resolved: 11/Jan/22 |
|
| Status: | Resolved |
| Project: | Content Translation Extended (CTX) |
| Component/s: | None |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | 3.4.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Carlos Cantalapiedra | Assignee: | Teresa Miyar |
| Resolution: | Fixed | Votes: | 0 |
| 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)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Description |
| Comments |
| Comment by Teresa Miyar [ 11/Jan/22 ] |
|
Note: The submitTranslation command must be set to sync to work with Blossom |
| Comment by Jörg Wirsig [ 12/Jan/22 ] |
|
Hi Teresa, it might be useful to add a hint that there is a modification of supportedFields required as well, as blossom uses old compatibility field types.
|
| Comment by Teresa Miyar [ 12/Jan/22 ] |
|
Thank you, will add the info in the documentation pages |