Closed (works as designed)
Project:
Domain
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Dec 2011 at 19:35 UTC
Updated:
21 Oct 2017 at 16:34 UTC
Jump to comment: Most recent
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