[MGNLCTS-128] richTextField is not exported Created: 19/Jan/21  Updated: 22/Sep/21  Resolved: 02/Feb/21

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.5
Fix Version/s: 2.5.1

Type: Bug Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Federico Grilli
Resolution: Fixed Votes: 4
Labels: cs-bk, maintenance
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Issue Links:
Relates
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
Release notes required:
Yes
Date of First Response:
Sprint: Maintenance 42
Story Points: 2

 Description   

Field which si configured:

description:
      $type: richTextField
      tables: false
      height: 200
      label: "Description"
      i18n: true

is not included in the export

Testing on m6.2.5 (cloud 1)

thanks.

DEV NOTES
------
If dam is installed, DamRichTextField will replace RichTextField. This is the expected behaviour and CTS should adjust its supported fields config accordingly.



 Comments   
Comment by Teresa Miyar [ 19/Jan/21 ]

Problem seems to be in ByteBuddyI18nizer before decorate we have 10 fields in the form, after decorate we get 7, the richtextfield is out for some reason it does not match the criteria on 6.2.4 seems to work

There is a workaround adding to supported fields (thank you rdrangovski)
‘damRichTextField’: ‘info.magnolia.dam.app.field.DamRichTextFieldDefinition’

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