Timeline for Component link in RTF not resolving in DXA1.5
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2016 at 18:53 | vote | accept | Atila Sos | ||
| Nov 17, 2016 at 18:52 | comment | added | Atila Sos | Understood, thank you. I was told by a collage that the switch was made because of some issues with SI4T, I will be sure and forward this information. | |
| Nov 17, 2016 at 18:33 | comment | added | Rick Pannekoek | BTW: SI4T works perfectly well with JSON format. You will get a weird intermediate result (JSON with an XML comment preamble), but the SI4T indexer (deployer extension) strips of this XML comment, so the stored content is regular JSON. We do extensively test (and support) that combination. | |
| Nov 17, 2016 at 18:29 | comment | added | Rick Pannekoek | In general, DXA is not intended to work with legacy DD4T XML (at least we don't test it nor guarantuee that it works). If you really want to stick with XML format, I would recommend to create a custom TBB instead of modifying the DXA one. | |
| Nov 17, 2016 at 11:02 | comment | added | Atila Sos | Thanks Rick, the mentioned TBB is present but unfortunately the namespace is still not stripped. Your answer did point me to the right direction however: In our implementation the 'Serialization format' is set to XML (it was needed to support SI4T). By changing it back to JSON, the namespaces were stripped, so I believe I have stumbled upon a bug. Resolve Rich Text does not strip the namespaces from XML format. Any ideas on how to address this issue? Is customizing the Resolve Rich Text the correct choice keeping in mind future releases? | |
| Nov 16, 2016 at 20:27 | history | edited | Rick Pannekoek | CC BY-SA 3.0 |
added 434 characters in body
|
| Nov 16, 2016 at 18:27 | history | answered | Rick Pannekoek | CC BY-SA 3.0 |