Can domain views write links to published domain rather than active domain?

The correct way is to use Domain Source to assign those nodes to a source domain. All links to the node will then be sent to the 'source' domain, regardless of the domain on which those links are written.

Domain Source links are only rewritten if the current domain is not the source domain.

When using Domain Source, all existing nodes would need to be assigned to a 'source' domain if you want to force links to go to a specific domain. You can use Domain Content to perform batch operations to add a source to existing content. The source works when nodes are published to multiple domains because it is merely a flag for where to send the link.

It is not related to #300454. That is a special case involving table prefixing.

From reading the bullet list of requests, it sounds like you don't need Domain Source at all. Just enable the default SEO Optimization. What that will do is detect whether or not linking to the current site will allow a node to be viewed. If not, it will write a link to the proper site.

In number form, these are easy to address.

1. From the national site I want links to affiliate sites' nodes to take the visitor to the originating site. Links to national nodes should keep the visitor on the national site.

This is what Domain Source is for. If the originating site is an affiliate, set a Domain Source value. If it is a national node, set the source to the national site.

2. On the affiliate sites I want the links to national nodes to keep the visitor on the current affiliate site.

Set the 'Default source domain' option to 'Do not change domain'.

3. On any one affiliate links to nodes of another affiliate should keep the visitor on the current affiliate site.

That makes no sense to me. It would only work if all content is viewable across all affiliates. And it would, as you say, contradict request #1.

The problem is that you have business rules that contradict the module design.

Your other option is to use your own copy of custom_url_rewrite_outbound. Instead of using the version provided, copy that function to a new file or to the bottom of settings.php -- be sure to remove the current include to my version of the file. THen edit custom_url_rewrite_outbound() to match your logic.

I see. You only need to rewrite paths on the primary domain.

You would need to implement your own version of custom_url_rewrite_outbound() that only rewrites the URL if $_domain['domain_id'] == 0.

That should work. Try using Domain Source, but inserting the following at line 31 of settings_custom_url.inc:

      $skip = TRUE;
    }
   // We use Domain Source, but only from the primary domain.
    if ($_domain['domain_id'] > 0) {
      $skip = TRUE;
    }
    // This routine only needs to be run from certain urls or if we want to

If you do not use Domain Source, this will still work, but you will have the links rewritten to the first match (based on domain creation order) and lose some control.

You should make you own copy of the settings_custom_url.inc file and put it in a different directory so it does not get overwritten on module updates.

In theory, we could provide a setting that allows this sort if control, but we have lots of settings already.

With a setting, the code looks like:

      $skip = TRUE;
    }
   // We use Domain Source, but only from the primary domain.
    if (variable_get('domain_rewrite_primary_only', 1) && $_domain['domain_id'] > 0) {
      $skip = TRUE;
    }
    // This routine only needs to be run from certain urls or if we want to

Here I have set the default value to 1, since there is no interface for changing the value.

This seems like an edge case to me. To handle it 'properly' you would need settings for Domain Source (probably) that indicate whether links should be rewritten on each domain.

We could also put in a hook to set the $skip value. That would let you write a custom module extending the behavior. I like that idea.

Send the nodes to 'all affiliates' or assign them to each domain where they should be visible.

You also have the option, for page views, of telling Domain Access to ignore its access controls on certain paths.

Enter the path in the 'Special Page Requests' settings box at Admin > Build > Domains.

Doing so will make DA ignore it's own access rules. This would work well if you had a different view page for the main site -- which you can do using Domain Conf.

Close the issue when you get it working.

With the Views 2 API, we can create a Views filter for Domain Source.