It would be nice if there were a way to have a per-domain setting to disable access control for a single subdomain, such that the subdomain will be able to see content from all other domains without restriction. I don't think there is a way to do this right now.

Why would I want to?

Well, here is our scenario, which I think is reasonable. We have several sites, business.treet,tv. entertainment.treet.tv, media.treet.tv, each of which uses full DA features and works quite well. However, we want to have a mobile site, m.treet.tv which allows content to be culled from the entire database. In other words, we don't want to create three mobile sites, but just one which shows the "greatest hits" from other sites and has custom treatment.

We just can't set "All Affiliates" on our content because we rely very heavily on having content "remain inside" each domain where it was created by users, and also each content group is truly distinct. But, for the mobile site, there is just too much content to try to cater to each site separately.

If you can think of a good way to do this, let me know.

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

I think this fits into the primary use-case of the module.

Why don't you simply select the mobile site as an additional publishing option for all nodes that you want placed there? That's what people would normally do, and it doesn't require any extra code.

You can also use the Domain Content module (included in the download), to batch select items to promote from each domain.

garywiz’s picture

garywiz commented

"Why don't you simply select the mobile site as an additional publishing option for all nodes that you want placed there? That's what people would normally do, and it doesn't require any extra code."

Well, the primary reason is because there are about 6000 nodes maintained by about 70 different people who have very limited content creation permissions, and new contributors coming up every day. None of them really know where things "should be", they all create nodes, and the domain settings are the default. So, if somebody is on our business site, they create nodes, they are assigned to business. If they are on the entertainment site, the defaults assign them to entertainment. Exposing the domain options to these people would be a bad idea.... they don't have the knowledge of drupal to decide what some of the options should be set to and when we have given them control of this, they have ultimately made mistakes frequently. In general, they aren't even aware of "other domains" and tend to work within the domain they know. It definitely shouldn't be the content creator's decision about whether things end up.

Ultimately, all of the options currently available "add work" to the daily creation of content. Either we need to train people to adjust settings they otherwise don't care about or understand, or have somebody spend several hours a day "repurposing" hundreds of new nodes and adjusting domain settings to be sure they go on the mobile site, or to use a batch updater to update them every day.

I made a simple patch which disables DA for the domain, and it works perfectly.

Maybe our situation is special, and I am happy with the patch I created. But, I think there is good cause to believe that others will need to have "aggregating domains" which pull content from other domains without having to have content creators tag those nodes to begin with. Mobile sites are one good example.

One answer might be to use Rules. I don't know whether Rules is supported by DA (if so, great). In that case, Rules could be set up to preset particular domain options when a node is saved, alleviating the need for unprivileged content creators to know how to set these options. It would also allow customization of the kind of situations and solve many domain assignment problems.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Rules should work. You can also try using an extension module and hook_domaingrants().

function custom_domaingrants(&$grants, $account, $op) {
  global $_domain;
  if ($_domain['domain_id'] != MOBILE_DOMAIN_ID || $op != 'view') { // set this value however you see fit.
    return;
  }
  $grants = array(); // NOTE: only do this is you are not using another node access module. Othwerwise, you have to unset the 'domain_id' and 'domain_site' array elements.
  $grants['domain_all'][] = TRUE;
}

This should modify the grants to use domain_all, which effectively turns off DA.

You have two other options, as well:

1) Let some editors use Domain Content module to re-assign content.
2) Use some combination of Rules / hook_form_alter() to silently assign content to the mobile domain.

I'd be happy to see a patch. I suppose what I'd be interested in is one that allows certain domains to be assigned to all nodes of a given type.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Postponed
agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Postponed » Closed (won't fix)
dhineshr’s picture

dhineshr commented

Is there any way to redirect admins of each domain to separate pages after login. for example the admin of one.example.com to dashboard page and two.example.com to content listing page. i've tried using rules, but not get the desired result as both the donmains redirect to dashboard page. plz help..thanks.