I'm building a community website with MB-AIO, Bricks Builder and WPGridBuilder.
Initially my intention was to create, about 27-30 custom fields for storing various user meta - stored in custom db table.
But, then I read this article Custom Fields vs Custom Taxonomy and it actually seems to be a better idea to use taxonomies instead of some custom fields (e.g. for gender) for front-end filtering users and for scalability reasons.
However, I cant find any straightforward way for assigning custom taxonomies to users.
Also, a LH User Taxonomies plugin suggested somewhere in this forums isn't updated for two years now.
So, is using taxonomies instead of some fields really a better solution for filtering performance and scalability?
How can it be done with MB (attaching custom taxonomies to users)?
Or, should I just put everything into a field group with 30 custom fields and into a custom db table, without overcomplicating things ?
Using the custom taxonomy for user is not a good solution, WordPress itself does not support taxonomy for user officially. It also cannot be done with Meta Box.
You can create custom fields for user (user meta) to store extra data for each user.
Or I think you can create a custom post type called Users, for example, then you can use the custom taxonomy or custom fields as you want.
You're right. Forcing non native solutions would most probably cause additional problems down the road.
Now, I don't know how many users - with a lot of extra data, wp can handle, but I know it handles posts very well. So, creating a cpt and binding it's posts to users seems to be a better solution after all.