Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.related issues
#1080616: A strategy for nested mini-sites using taxonomy, fields api and domains
Good day
I have a project with a huge relation strucrure between domains
and thinking about changing backend table "domain" with taxonomy _storage_
1 We can then create multiple domain groups and relations using taxonomy hierarhy and taxonomy reference fields
2 We can provide more complicated support for views (taxonomy based)
3 It will be possible to integrate domains with a huge taxonomy related modules database
Comments
Comment #1
agentrickardThis sounds to me like the rejected "Convert domains to entities" request, and would also be rejected.
There is not enough detail here to even make an assessment of how much work is involved.
You might consider attaching optional fielded (entity) data to a domain based on machine_name.
Comment #2
podarokThis issue only for consolidating thoughts about
Working on 500+ domain structured site network we have a lot task with views and smart exposed filters dependent on domain access
And with taxonomy - it`s much easier despite domain - cause widgets, contrib support much more against domain itself
But "domain" table mostly looks like "taxonomy_data" and do the same work but not so nice
Comment #3
agentrickardTaxonomy is not so nice when you get FieldAPI involved. Note that taxonomy_index only stores data for published nodes.
What you want is a hierarchy system, I get that, but what you suggest is tremendously more difficult than you seem to admit. There was some domain hierarchy work done in Drupal 6, finding that would be a good start.
And moving domains over to use entities is a non-starter for a variety of reasons.
Comment #4
agentrickard