You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing the same issue with not using the Categories Attribute on the IList<>. The only way we can get the dialog to work is by using StandardContentBase as the allowed type, which is not optimal.
I've checked the browser console, and I'm not seeing any console errors. I am seeing that the request (see below) to the store is not returning any objects when using a type that extends from CategoryData.
So following this part of the documentation:
If you prefer to use the native content reference list editor for your categories you can skip the CategoriesAttribute:
If I implement the above, then it never shows any categories, it just displays the root node:
If I implement the single category property, it displays fine:
[UIHint(CategoryUIHint.Category)]
[AllowedTypes(typeof(TopicCategory))]
public virtual ContentReference TopicCategory{ get; set; }
The text was updated successfully, but these errors were encountered: