Experience Fragments - unused 'text' property causing issues during translation
|
Request for Feature Enhancement (RFE) Summary: |
|
| Use-case: |
AEM is sending duplicate content to the third party applications like smartling when the page is submitted for the translation which has Experience fragment referred in it. Example: Let's assume, we have a page where experience fragment component is used. The moment experience fragment is added on the page, 'text' property gets created at node level and all the experience fragment content will be stored at page level as well which is not required.
|
| Current/Experienced Behavior: | 'text' property gets created at node level and all the experience fragment content will be stored at page level as well which is not required. |
| Improved/Expected Behavior: | 'text' property should be removed |
| Environment Details (AEM version/service pack, any other specifics if applicable): | AEM 6.5.12 |
| Customer-name/Organization name: | |
| Screenshot (if applicable): | 
Steps to reproduce: 1. Create Experience fragment add test component. 2. Create Page and add 'Experience Fragment' component. 3. Edit component & Refer experience component path and Save dialog. 4. Verify the experience fragment node property at content level where you can see unused 'text' property. |
| Code package (if applicable): |
