IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
This tutorial demonstrates how to add a hierarchical taxon selector in a widget's designer view. You can select taxa from a hierarchical taxonomy like Categories or a custom classification of your choice. For more information about categories in Sitefinity CMS, see For developers: Hierarchical taxonomies. For more information on custom classifications in Sitefinity CMS, see Create custom classifications.
DesignerView.YourView.json
JSON
DesignerView.<YourView>.json
scripts
NOTE: For more information on the scripts that you must load, see Feather: List of selectors scripts reference.
designerview-<yourview>.js
.js
DesignerView.<YourView>.cshtml
To access the selected value, you use the sf-selected-item and sf-selected-item-id attributes. If multiple selection of items is enabled, you must use the sf-selected-items and sf-selected-ids attributes. For more information on multiple selection of items, see Feather: Use multiple content items selectors.
sf-selected-item
sf-selected-item-id
sf-selected-items
sf-selected-ids
By default, the selector shows only categories but you can modify it to work with a hierarchical taxonomy of your choice. You do this by specifying a sf-taxonomy-id attribute that accepts a scope property holding the GUID of the taxonomy. You can specify the dialog header using the sf-dialog-header attribute. By default, the dialog header is Select but if you set sf-dialog-header="Department", then the header is Select Department.
sf-taxonomy-id
sf-dialog-header
sf-dialog-header="Department"
To create the scope property, add the following code in the widget designer's controller:
You can access the scope property using scope.properties.TaxonomyId.PropertyValue. In the code above, the GUID the Departments taxonomy.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important