- 🇺🇸United States bluegeek9
Drupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade → .
Here are my sites/language combinations:
example.com/en (master)
example.us/en-US
example.ca/en-CA
example.ca/fr
example.mx/en-MX
example.mx/es
We use various workbench moderation states (Content Authoring, Editor Review, Approved to Publish, Publish).
Basically, all of our content editing, etc. is done on the example.com site.
So, a user creates a new node on .com site. "Send to all affiliates" = OFF, only check .com under "Publish to:". All good so far. Still only showing on .com - Good.
Eventually, it hits an Approved to Publish state, which means it's been approved to be posted to all sites, and then the users of each of the country sites can either publish the node, translate it themselves (but needs to go through another approval process), or send it to translation services.
The problem I hit is once it gets into the Approved to Publish state, it also needs to push the node to all domains.
I've tried checking the "Send to all affiliates" box and only select .com as the "owner". And I've tried keeping "Send to all affiliates" box unchecked, and select all the checkboxes under "Publish to:". I've tried using the domain_source module, but i don't really understand what it's for, but the results weren't any better when using it.
Examples of my problems once the .com node hits Approved to Publish state:
1. Node/500 on .com (Send to all affiliate OFF, Publish to: .com).
Node/500 is accessible for view and edit on all domains.
node/500 path alias of products/test is only available for view and edit on .com. Good.
2. Node/500 on .com (Send to all affiliates ON, Publish to: .com).
Node/500 is available for view and edit on all other domains. Good.
The path alias for node/500, which is products/test works on .com, but not on any of those other domains.
CA user should now be able to go to example.ca/en-CA, review the node, and publish the en-CA version to their site if they want, resulting in node/501. If they want the content on their site, they also need to create a translation on example.ca/fr from node/500, resulting in a node/502 for FR.
But, when a translation is added, a domain access setting needs to be set. Should it be set to "Send to all", "Publish to only .ca)? Or would domain_source come into play here?
3. Node/500 on .com (Send to all affiliate ON, Publish to: .com, .us). Same as #1.
4. Node/500 on .com (Send to all affiliate ON, Publish to: .com, .ca). Same as #1.
I don't understand why the node is available on sites that aren't checked?
I also don't understand the difference between what core node_access does and what domain node_access does? How should permissions be set differently?
I don't understand the difference between "Send to all affiliates" and checking each box under "Publish to:".
I don't understand the use for domain_source.
Closed: outdated
3.11
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Drupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade → .