Timeline for SxaTags not rendering in Rendering Variants
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2019 at 7:01 | comment | added | Dawid Rutkowski | You are complicating your life. Just change the approach, start using tags on pages (like everyone...) and problem solve. | |
| Oct 8, 2019 at 14:31 | comment | added | Sumit Upadhyay | With the custom template, SxaTags show up in front end :) But when I'm trying to edit the Tags through Experience Editor, it does not have any effect. I believe that the Tags in the Experience Editor are pointing to the ones in the page instead of the custom template. Is there a workaround to make it editable from the Experience Editor. | |
| Oct 8, 2019 at 10:47 | comment | added | Dawid Rutkowski | You can do it, but you would need to extend Promo data source template with SxaTags filed (there is a base template for that). | |
| Oct 7, 2019 at 18:01 | comment | added | Sumit Upadhyay | Yup I got it. But just wondering if there's anyway to make this work for Promo with a data source | |
| Oct 7, 2019 at 12:24 | comment | added | Dawid Rutkowski | @SumitUpadhyay No... I'm just saying that Page Content is using the current page as the data source by default (when the data source field is empty). We have tags on the pages. When you are using Promo, the rendering variant for promo won't look for tags on the page, it will looks for tags on the Promo data source item (as promo is using it) but the tags are not there. | |
| Oct 7, 2019 at 11:59 | comment | added | Sumit Upadhyay | So you mean SxaTags would not work for Promos? And will work only for components which don't use data sources? Is my understanding correct? | |
| Oct 7, 2019 at 11:53 | history | answered | Dawid Rutkowski | CC BY-SA 4.0 |