-
I believe the confusion comes from mixing up Admin Categorization via Labels (which do support parent-child structure in the Forms app) with user-generated Channels via hashtags, which remain flat by design in UNA’s core implementation.
If you're looking to organize hashtags or topics into parent-child groups, one possible workaround is through the Spaces module. You can structure Spaces in a parent-child hierarchy, and then subscribe those Spaces to specific hashtags (Channels). While the Channels themselves remain flat, this would effectively give you a way to group and moderate them within a structured Space-based environment.
In short:
- Labels → Admin-defined hierarchy
- Channels → User-driven, flat hashtags
- Spaces → Can be organized parent-child, and optionally associated with hashtags
Not a perfect native integration but a practical workaround depending on your community structure. https://unacms.com/wiki/hashtags-labels-channels#tags-vs-hashtagschannels-vs-labels-in-una
-
I’m currently studying the problem and will get back to you with a detailed response once I have a complete understanding of it.
-
Interesting: https://ci.una.io/docs/service.html#bx_channels-entity_parent But I still don't understand what the two html blocks are for. entity_parent and entity_childs
-
We've been very satisfied with using Spaces to create a hierarchy for communities. We started off using Channels but the hashtags left too much room for content violations. Spaces has been a great way to create communities and sub-communities. The lone hiccup is the Roles association where we can create roles within Spaces which are independent of User Levels. We're still working through that redundancy.