Using taxonomy terms for categories has made generating "features" with this module a nightmare. Additionally it doesn't really make sense to use taxonomy terms in the first place. It would be much more logical and simple to just use a serialized array variable. That would make it exportable to features using strongarm and greatly simplify the user interface.

Once userpoints are made into entities in 2.0 the categories can be "bundles" or the user can create their own select or taxonomy field or whatever they wish.

Comments

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Closed (won't fix)

7.x-2.x will change how all these things work as you said, see e.g. the discussion in #1870674: Categorization with default taxonomy term reference field and views.

However, changing the taxonomy module integration in 7.x-1.x is not an option, there is no way that would be backwards compatible.