In our use case, we're having trouble with how nodes are being added.
By design, the module assigns all new nodes to the domain from which they were entered. If the user has 'set domain access' privileges, then this behavior is replaced by a form.
Some of our editors create content from the 'wrong' domain -- we probably need to enforce that they can only create content for 'their' domain.
Question: What is the best solution here? Some options:
1) Create a new permission: 'assign domain content' (or similar) which would:
-- Check which domains the user is assigned to.
-- If count == 1, assign all new nodes to that domain.
-- If count > 1, give a series of checkboxes (radios?) for the user to select.
-- If count == 0, assign to the active domain (the current behavior).
2) As above, but with configuration options for handling case where count > 1.
3) Do not add a permission. Act based on configuration options for users who have the 'edit domain nodes' option.
4) Force all users to enter content from their 'registered' domain by using domain_goto().
Option #4 would mean that, on registration, users might need to select their domain -- currently they are assigned to the active domain that they register from.