Posted by peterx on October 14, 2008 at 3:59am
Jump to:
| Project: | Domain Access |
| Version: | 6.x-2.0-rc4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (works as designed) |
Issue Summary
6.1 converted to 6-2 RC4. Edit content. One site selected. I deselected the site and ticked Send to all affiliates
. The page would not let me preview or save until I selected a site. The page kept saying Publish to field is required
. I tried creating a new page and had the same error.
Domain module behaviors:
New content settings: *
( ) Show on all affiliate sites
(*) Only show on selected sites
Comments
#1
This is by design. The instructions are misleading.
Even if a node is assigned to all affiliates, it must still be assigned to a domain. We use this for editor controls and link rewrites.
Section 6.1 of the README used to say:
If you select 'Send to all affiliates,' the node will be viewable on all domainsfor your site. If you do not select this option, you must select at least one
domain for the node.
It should say:
If you select 'Send to all affiliates,' the node will be viewable on all domainsfor your site. Even if you select this option, you must select at least one
domain for the node.
The setting you refer to is actually about whether or not the 'send to all affiliates' option is selected by default. Changing it will not affect your problem. See 4.2.1 of the README, which is accurate.
#2
How does the domain selection mix with the user access options? We need content going to many sites with some content creators logging into many sites. Will they be able to edit their own content or will they have to go to a domain to edit their content?
I am about to test everything at examplea.net and am trying to sort out user permissions. The user table is shared so a small number of content editors can log in anywhere. The node table is shared so sites can share some content. The menu tables are different by site so that each site can have their own menues. The non technical content editors will add a new site, visit the site, read the shared pages within the context of the specific site then edit the shared pages to not conflict with the new site or create a local copy with local changes. For local pages, they will change the page's user name to the user id of the person who owns the new site. The site owner will then be able to modify the local pages.
#3
'Sharing' the user table and node tables should be done by default. That is, you do not use DA like normal Drupal multisite. If you are using table prefixing on the node or users tables, then the node access system may work in unpredictable (and unsupported) ways.
Under node access rules, users can always edit their own content. Under certain configurations, DA may force those edits to be done from a certain domain.
There is no concept of 'copying' to a local site. If a node is visible on multiple domains, it can be edited by anyone with the proper permissions. Those edits apply to all views of the node, becuase there is only one copy.
It sound to me like you are mixing traditional multisite concepts with DA, which is causing confusion. Perhaps you need to re-think your site architecture.