Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.3.3
-
Fix Version/s: Unscheduled
-
Component/s: WordPress Integration
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:User and Admin Doc
-
Funding Source:Needs Funding
Description
When 'multisite' option of wordpress is enabled, the wordpress permissions scheme only works for the top/main site in the multisite hierarchy. All subsites (e.g. subsite.mainsite.org):
a. show only empty checkboxes on the wordpress permissions page, irrespective of what has been actually selected,
b. throw an error when the permissions page on the subsite is edited
c. effectively lock all non.admin users out of civicrm pages on subsites, including registration pages etc, due to 'insufficient permission0
Attachments
Activity
An update on this feature.
If CiviCRM is configured to be used across sites as a multi-domain civi, instructions here: https://wiki.civicrm.org/confluence/display/CRMDOC/Multi+Site+Installation. Permissions work on the the other sites as configured. This would be the same if it is on a WordPress multisite accessing CiviCRM from multitple sites or multiple single site installs of WP.
ACLs in CiviCRM are basically managed by groups and then components. This page outlines how each works in more detail: https://wiki.civicrm.org/confluence/pages/viewpage.action?pageId=86213708 noting if there is separation across sites. Working on each of those items in CiviCRM will provide for ways to share a single CiviCRM instance across a network of sites.
From my understanding this page is the most current that outlines proposed changes: https://wiki.civicrm.org/confluence/display/CRMDOC/Proposed+changes+to+multisite it would be good to update this and get a sense of ways this work could be funded.
Dana Skallman Can you confirm if this can be replicated on 4.7?
From what I have seen to date network admins and Admins of any sub-site have access to all CiviCRM no matter if the multisite settings define access only to that site. The permissions are then applied on a site by site basis when CiviCRM is activated on a site by site basis, when not network activated. Screenshots below show the main site and it's roles that are different that the second site on the same network that roles vary. And this assumes accessing the same CiviCRM DB on both sites, which does not display the installer screen as noted below.
For that to work we had to make the following change the following in `civicrm.config.php`
'settingsFile' => '/var/www/yoursite/wp-content/uploads/civicrm/civicrm.settings.php',
from
'settingsFile' => NULL,`
When CiviCRM is network activated the installer screen appears on sub-sites, which seems like it could technically override the main database if run from a sub-site. I would need to test and look into this more, but maybe Christian Wach knows more about that. Might be it's own ticket, including screenshot from a sub-site with CiviCRM network activated and configure already installed and configured on the main site:
Let me know if I am understanding what is being reported in this issue correctly.
It is my understanding that by default CiviCRM is set for one domain. So it would only work on the main site permissions, not any of the sub-sites. By using it on a WP multisite you'd have to add each site or each domain to Civi by following the instructions here http://wiki.civicrm.org/confluence/display/CRMDOC/Multi+Site+Installation. Each subsite would be it's own domain and have it's own ID or Default Org contact.