|Anonymous | Login | Signup for a new account||2015-08-31 15:11 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000004||Active Directory Integration||Multisite||public||2011-02-18 14:16||2011-05-04 21:10|
|Target Version||1.2||Fixed in Version|
|Summary||0000004: Better MultiSite Support|
|Description||There are three possibilities for settings in multisite environments:|
1. global settings for all sites
2. individual settings for every single site
3. A combination of both: Choose which site uses individual settings an which has to use the global settings.
Dr. Iver Jackewitz [firstname.lastname@example.org] has made some changes to the plugin.
And here is discussion on this topic:
|Tags||No tags attached.|
|Attached Files||adi_multisite_patch.zip [^] (28,523 bytes) 2011-02-18 14:16|
If that title doesn't scare you off!....
Our setup is a WP multi site with a wildcard domain. AD-integration is working well - except in this specific case.
New user logs in at a page such as:
Password and authorisation succeeds and they see the normal admin dashboard. Except, that their newly created user account is associated with ourwordpress.org, and everything they see is in that context.
Looking at the code ad-integration.php line 994:
// Here we go!
$return = wp_create_user($username, $password, $email);
This seems to be the call that creates the user. Is there some way to specify which blog the user will be associated with, depending on which domain login page they enter from?
Apart from this problem I have found the ad-integration plugin to be very useful and the test function is especially good.
At http://wordpress.org/support/topic/plugin-active-directory-integration-single-config-for-multisite, [^] the recommended solution is to create a module and put it in the mu-plugins directory. That causes two problems:
1. After adding this mu-plugins module, you have to redo all your Active Directory Integration settings. The ADI module moves from Settings > Active Directory Integration to Super Admin > Active Directory Integration
2. When under Super Admin, the tabs don't appear correctly. Instead, the tabs show just as vertically-stacked links at top left of the module settings.
Just want to clarify my prior statement.
Right now, if I network enable this plugin on a WordPress Network (multisite), I have to go to the root blog's dashboard (/wp-admin/) and use Tools > Active Directory Integration.
I think proper design is that this plugin's settings page would only appear in network admin (/wp-admin/network/) and nowhere else.
|Bug 31 (http://bt.ecw.de/view.php?id=31 [^]) may be caused by the workaround required described in the above-linked WP forum post.|
|2011-02-18 14:16||cst||New Issue|
|2011-02-18 14:16||cst||Status||new => assigned|
|2011-02-18 14:16||cst||Assigned To||=> cst|
|2011-02-18 14:16||cst||File Added: adi_multisite_patch.zip|
|2011-02-18 14:33||cst||Description Updated||View Revisions|
|2011-02-21 16:34||cst||Note Added: 0000007|
|2011-02-23 21:09||arencambre||Note Added: 0000012|
|2011-03-24 11:14||cst||Target Version||1.1 => 1.2|
|2011-03-24 11:15||cst||Status||assigned => confirmed|
|2011-05-02 19:53||arencambre||Note Added: 0000043|
|2011-05-04 21:10||arencambre||Note Added: 0000048|
|Copyright © 2000 - 2010 MantisBT Group|