- Issue created by @vlooi vlerke
- π«π·France lazzyvn paris
why are you creating a Kanban view with taxonomy base?
Create node content type (or user, user profile but not taxonomy)
create field status with taxonomy add status in taxonomy terms list
add view kanban for node content type
add field status taxonomy
select the field in the Kanban parameter.
I have 20 Kanban views for my project with taxonomy. If there is a mistake, I need to know about it.
I want next version support color for each status with color field in taxomy if it define but drupal 10 remove color field. - πΏπ¦South Africa vlooi vlerke
I have no issues with taxonomy term reference fields used on "node" content types. They work.
I did the following tests, I recreated the demo but used different entity types.
node (task content type demo) - no errors
user (user entity with user task fields) - no errors
storage (storage entity type with storage task fields) - no errorsTaxonomy (vocabulary with term task fields) - dragg error
Profile (profile entity with profile task fields) - dragg errorYou right it does not make sense to use terms as tasks, same goes for profile entities.
Storage entity works great as it does not clutter the "node" content with loads of tasks and all tasks can be managed thru storage content admin.
Thanks, this is a great module
- Status changed to Closed: won't fix
7 months ago 2:41pm 10 April 2024