Menu
▾
▴
wpmu-ldap-users
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(49) |
Aug
(13) |
Sep
(1) |
Oct
(19) |
Nov
(6) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(9) |
Feb
(40) |
Mar
(30) |
Apr
(11) |
May
(23) |
Jun
(38) |
Jul
(39) |
Aug
(8) |
Sep
(10) |
Oct
(7) |
Nov
(3) |
Dec
(5) |
| 2010 |
Jan
(7) |
Feb
(6) |
Mar
(14) |
Apr
(13) |
May
(8) |
Jun
(4) |
Jul
(8) |
Aug
(1) |
Sep
(3) |
Oct
(5) |
Nov
(1) |
Dec
|
| 2011 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(6) |
Oct
(4) |
Nov
|
Dec
|
| 2012 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Grigsby, L. <Lan...@ba...> - 2010-07-27 17:36:01
|
Just upgraded my test server to 3.0. We've been using Aaron Axelson's great LDAP plugin, and we're excited to see that it's going to support the addition of group settings in the user interface--only problem is we can't get them to work, even when we point to a full DN. Anybody have the same problem? Generally, the plugin is authenticating fine; it's just when we specify group settings (we only allow certain members of our community to login and have blogs), authentication fails. Would LOVE to get this to work because heretofore, we've had to hack the plugin to get it to authenticate against certain groups in AD. Specifically, the error we get is: "Access denied - user not found in security access group(s)." Could this be a problem with our Attribute Mapping settings? |
|
From: SourceForge.net <no...@so...> - 2010-07-27 11:32:46
|
Bugs item #3033652, was opened at 2010-07-23 11:19 Message generated for change (Settings changed) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033652&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Collision with other WordPress plugins Initial Comment: Under WP 3.0, when also using the FeedWordPress plugin ( http://wordpress.org/extend/plugins/feedwordpress/ ), LDAP users cannot log in. I was able to fix this by changing line 94 of lib/wpmu_ldap.functions.php to require_once( ABSPATH . WPINC . '/registration.php' ); from require ( ABSPATH . WPINC . '/registration.php' ); Thanks for the great plugin. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-07-27 06:32 Message: 3033604 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033652&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-07-27 11:32:22
|
Bugs item #3033652, was opened at 2010-07-23 11:19 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033652&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Duplicate Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Collision with other WordPress plugins Initial Comment: Under WP 3.0, when also using the FeedWordPress plugin ( http://wordpress.org/extend/plugins/feedwordpress/ ), LDAP users cannot log in. I was able to fix this by changing line 94 of lib/wpmu_ldap.functions.php to require_once( ABSPATH . WPINC . '/registration.php' ); from require ( ABSPATH . WPINC . '/registration.php' ); Thanks for the great plugin. ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-07-27 06:32 Message: 3033604 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033652&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-07-27 11:31:54
|
Bugs item #3033604, was opened at 2010-07-23 09:27 Message generated for change (Settings changed) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033604&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: plugin causing 'Cannot redeclare username_exists()' error Initial Comment: in file /ldap/lib/wpmu_ldap.functions.php on line 94: require ( ABSPATH . WPINC . '/registration.php' ); should be: require_once ( ABSPATH . WPINC . '/registration.php' ); ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-07-27 06:31 Message: fixed in trunk ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033604&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-07-27 11:31:44
|
Bugs item #3033604, was opened at 2010-07-23 09:27 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033604&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: plugin causing 'Cannot redeclare username_exists()' error Initial Comment: in file /ldap/lib/wpmu_ldap.functions.php on line 94: require ( ABSPATH . WPINC . '/registration.php' ); should be: require_once ( ABSPATH . WPINC . '/registration.php' ); ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-07-27 06:31 Message: fixed in trunk ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033604&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-07-23 16:19:56
|
Bugs item #3033652, was opened at 2010-07-23 16:19 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033652&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Collision with other WordPress plugins Initial Comment: Under WP 3.0, when also using the FeedWordPress plugin ( http://wordpress.org/extend/plugins/feedwordpress/ ), LDAP users cannot log in. I was able to fix this by changing line 94 of lib/wpmu_ldap.functions.php to require_once( ABSPATH . WPINC . '/registration.php' ); from require ( ABSPATH . WPINC . '/registration.php' ); Thanks for the great plugin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033652&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-07-23 14:27:19
|
Bugs item #3033604, was opened at 2010-07-23 14:27 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033604&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: plugin causing 'Cannot redeclare username_exists()' error Initial Comment: in file /ldap/lib/wpmu_ldap.functions.php on line 94: require ( ABSPATH . WPINC . '/registration.php' ); should be: require_once ( ABSPATH . WPINC . '/registration.php' ); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3033604&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-06-20 05:26:52
|
Bugs item #3017995, was opened at 2010-06-18 06:35 Message generated for change (Settings changed) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3017995&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Aaron Axelsen (axelseaa) Assigned to: Nobody/Anonymous (nobody) Summary: Switching LDAP account to Local does not work as expected Initial Comment: When switching an existing account from LDAP to use local authentication, the LDAP username/password will still work. Plugin needs to force only local checking and bypass the ldap lookup ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-06-20 00:26 Message: fixed in trunk ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3017995&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-06-18 13:50:09
|
Bugs item #2962812, was opened at 2010-03-03 19:11 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Aaron Axelsen (axelseaa) Summary: Bulk Add Fails to Create DB tables for New Users Initial Comment: I’m experiencing issues when blog admins bulk add a large group of users (say 30 or so users) that don’t already have blogs, so a personal blog is created for the user in addition to adding them to the admin’s blog (as per my settings to do so in LDAP Options). It appears that a number of tables are not being properly created for their personal blog. ie. wp_716_options and so forth for each blog ID. When you try to go to their blog, you just get “The blog you have requested is not installed properly. Please contact the system administrator.” and “WordPress database error: [Table 'wordpress.wp_716_options' doesn't exist]” in my WP error log. It seems that the very first user in the bulk add list has their blog created properly. Every other user in the list, it appears to succeed to the person adding, but actually fails somewhere on the backend. I am running WPMU LDAP v2.9 and WPMU 2.9.1.1. I have disabled bulk add for now as this does not happen with single user adds. Thanks ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-06-18 13:50 Message: Are you talking about LDAP group memberships? If so, yes, that would indeed be helpful, but for us, more from the backend 'Add User' function, not upon login. We already use the auto-create blog and user for any user in our entire LDAP directory who chooses to login to the service, which always works fine. Hmmm.. wondering.. maybe I just need more clarity on what exactly your thoughts are there. Are you suggesting: - I've created a blog for someone, who wants to add say 30-40 LDAP users as Authors to their new blog. - They would "bulk add" these users, but if any have never logged into the system before, they would be "held" in a group. (If they have an existing WP account, they would get added as Author immediately.) - Once any user in that group logs into the system, their user and personal blog will be auto created as per normal, but the system would also add them to the other blog as Author, since they were in that group. Am I totally off track? :-) I'm thinking it would be easier if the WP code was written in such a way that allowed your Bulk Add function to create more than 1 blog at a time. Hehe. Thanks. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-06-18 11:33 Message: I don't know of any way to make that work. I've tried a similiar approach before for a different project, and it didn't work. Would it work to add a group setting so that any users who is a member of a specific group would automatically have a blog created during login? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-05-19 20:51 Message: Ok, thanks. Was wondering as a possible solution (since this feature would be very useful to us)... Can the list of bulk adds run each username in the list through the single user add function somehow, thereby allowing the create blog function to work? It might take longer, but is a lot better than entering each username individually. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 16:39 Message: The logic has been changed in the svn trunk to not create blogs when using bulk add. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-16 04:29 Message: Well, the feature still works - just not with the auto create blog for new user option. So i'll leave the future there, it will just need to be stated blogs will not be created - and it also needs to not attempt to create them. Thanks again for pointing this out! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-15 18:13 Message: So, unless core WP code changes, you will be removing this feature from future WPMU LDAP releases? ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-07 03:13 Message: I thought about this and looked at the code some - and then I remembered. This actually is not possible. Currently, wordpress only allows for a single new blog to be created per instance. For example, if you try to loop through a list, only the blog for the first user will be created successfully. The rest of the blogs will not be fully created and stuck in a weird state. When I get some more time, i'll investigate whether or not this changes in 3.0 - but in the 2.x trunk, I have not been able to successfully make this work. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:37 Message: I don't use the auto create option myself - so i'm sure i just missed that when going through the creation process for bulk add. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:22 Message: Wow. Actually, I was just taking a look at my DB. Seems that NO tables were created for the block of blog ID's where I've noticed the problem. So, this would include: wp_xxx_commentmeta wp_xxx_comments wp_xxx_links wp_xxx_options wp_xxx_postmeta wp_xxx_posts wp_xxx_terms wp_xxx_term_relationships wp_xxx_term_taxonomy ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:16 Message: Ok. I'll follow this (should have created an account!). Let me know if you need further information to help narrow it down. The bulk add is a very useful feature for us, so hopefully we can figure out what's going on. Thanks. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:15 Message: That's probably whats going on then. Will take a look time permitting and report back. Thanks for the report! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:14 Message: Yes. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:13 Message: Is your site configured to auto create a blog for new users? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-06-18 11:35:26
|
Bugs item #3017995, was opened at 2010-06-18 06:35 Message generated for change (Tracker Item Submitted) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3017995&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Aaron Axelsen (axelseaa) Assigned to: Nobody/Anonymous (nobody) Summary: Switching LDAP account to Local does not work as expected Initial Comment: When switching an existing account from LDAP to use local authentication, the LDAP username/password will still work. Plugin needs to force only local checking and bypass the ldap lookup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=3017995&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-06-18 11:33:38
|
Bugs item #2962812, was opened at 2010-03-03 13:11 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Aaron Axelsen (axelseaa) Summary: Bulk Add Fails to Create DB tables for New Users Initial Comment: I’m experiencing issues when blog admins bulk add a large group of users (say 30 or so users) that don’t already have blogs, so a personal blog is created for the user in addition to adding them to the admin’s blog (as per my settings to do so in LDAP Options). It appears that a number of tables are not being properly created for their personal blog. ie. wp_716_options and so forth for each blog ID. When you try to go to their blog, you just get “The blog you have requested is not installed properly. Please contact the system administrator.” and “WordPress database error: [Table 'wordpress.wp_716_options' doesn't exist]” in my WP error log. It seems that the very first user in the bulk add list has their blog created properly. Every other user in the list, it appears to succeed to the person adding, but actually fails somewhere on the backend. I am running WPMU LDAP v2.9 and WPMU 2.9.1.1. I have disabled bulk add for now as this does not happen with single user adds. Thanks ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-06-18 06:33 Message: I don't know of any way to make that work. I've tried a similiar approach before for a different project, and it didn't work. Would it work to add a group setting so that any users who is a member of a specific group would automatically have a blog created during login? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-05-19 15:51 Message: Ok, thanks. Was wondering as a possible solution (since this feature would be very useful to us)... Can the list of bulk adds run each username in the list through the single user add function somehow, thereby allowing the create blog function to work? It might take longer, but is a lot better than entering each username individually. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 11:39 Message: The logic has been changed in the svn trunk to not create blogs when using bulk add. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-15 23:29 Message: Well, the feature still works - just not with the auto create blog for new user option. So i'll leave the future there, it will just need to be stated blogs will not be created - and it also needs to not attempt to create them. Thanks again for pointing this out! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-15 13:13 Message: So, unless core WP code changes, you will be removing this feature from future WPMU LDAP releases? ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-06 22:13 Message: I thought about this and looked at the code some - and then I remembered. This actually is not possible. Currently, wordpress only allows for a single new blog to be created per instance. For example, if you try to loop through a list, only the blog for the first user will be created successfully. The rest of the blogs will not be fully created and stuck in a weird state. When I get some more time, i'll investigate whether or not this changes in 3.0 - but in the 2.x trunk, I have not been able to successfully make this work. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:37 Message: I don't use the auto create option myself - so i'm sure i just missed that when going through the creation process for bulk add. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:22 Message: Wow. Actually, I was just taking a look at my DB. Seems that NO tables were created for the block of blog ID's where I've noticed the problem. So, this would include: wp_xxx_commentmeta wp_xxx_comments wp_xxx_links wp_xxx_options wp_xxx_postmeta wp_xxx_posts wp_xxx_terms wp_xxx_term_relationships wp_xxx_term_taxonomy ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:16 Message: Ok. I'll follow this (should have created an account!). Let me know if you need further information to help narrow it down. The bulk add is a very useful feature for us, so hopefully we can figure out what's going on. Thanks. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:15 Message: That's probably whats going on then. Will take a look time permitting and report back. Thanks for the report! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:14 Message: Yes. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:13 Message: Is your site configured to auto create a blog for new users? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-25 02:28:40
|
Bugs item #2992502, was opened at 2010-04-26 19:12 Message generated for change (Settings changed) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2992502&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Settings Aren't Copied to Users Initial Comment: I'm able to successfully authenticate against our LDAP servers, however the admin's setting aren't copied over when new blogs are created (auto create users and blogs is set to no). For example, a non-default permalink structure fails unless the user has an administrator role. As another example, I have the WP-Latex plugin which works as along as each user goes into their blog with the admin role, enters the default configuration settings, and saves them. Then the plugin works regardless of what role they have. If they don't configure the plugin that the admin has already configured it fails. Why aren't the default settings copied over to new users? Thanks. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2010-05-25 02:28 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 05:20 Message: what default settings are you referring to? Can you explain this in more detail? It sounds like you are having a problem with new blogs, and if you have auto create users and blogs disabled, your problem is with the core wordpress code - and not this plugin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2992502&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-19 20:51:52
|
Bugs item #2962812, was opened at 2010-03-03 19:11 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Aaron Axelsen (axelseaa) Summary: Bulk Add Fails to Create DB tables for New Users Initial Comment: I’m experiencing issues when blog admins bulk add a large group of users (say 30 or so users) that don’t already have blogs, so a personal blog is created for the user in addition to adding them to the admin’s blog (as per my settings to do so in LDAP Options). It appears that a number of tables are not being properly created for their personal blog. ie. wp_716_options and so forth for each blog ID. When you try to go to their blog, you just get “The blog you have requested is not installed properly. Please contact the system administrator.” and “WordPress database error: [Table 'wordpress.wp_716_options' doesn't exist]” in my WP error log. It seems that the very first user in the bulk add list has their blog created properly. Every other user in the list, it appears to succeed to the person adding, but actually fails somewhere on the backend. I am running WPMU LDAP v2.9 and WPMU 2.9.1.1. I have disabled bulk add for now as this does not happen with single user adds. Thanks ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-05-19 20:51 Message: Ok, thanks. Was wondering as a possible solution (since this feature would be very useful to us)... Can the list of bulk adds run each username in the list through the single user add function somehow, thereby allowing the create blog function to work? It might take longer, but is a lot better than entering each username individually. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 16:39 Message: The logic has been changed in the svn trunk to not create blogs when using bulk add. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-16 04:29 Message: Well, the feature still works - just not with the auto create blog for new user option. So i'll leave the future there, it will just need to be stated blogs will not be created - and it also needs to not attempt to create them. Thanks again for pointing this out! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-15 18:13 Message: So, unless core WP code changes, you will be removing this feature from future WPMU LDAP releases? ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-07 03:13 Message: I thought about this and looked at the code some - and then I remembered. This actually is not possible. Currently, wordpress only allows for a single new blog to be created per instance. For example, if you try to loop through a list, only the blog for the first user will be created successfully. The rest of the blogs will not be fully created and stuck in a weird state. When I get some more time, i'll investigate whether or not this changes in 3.0 - but in the 2.x trunk, I have not been able to successfully make this work. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:37 Message: I don't use the auto create option myself - so i'm sure i just missed that when going through the creation process for bulk add. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:22 Message: Wow. Actually, I was just taking a look at my DB. Seems that NO tables were created for the block of blog ID's where I've noticed the problem. So, this would include: wp_xxx_commentmeta wp_xxx_comments wp_xxx_links wp_xxx_options wp_xxx_postmeta wp_xxx_posts wp_xxx_terms wp_xxx_term_relationships wp_xxx_term_taxonomy ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:16 Message: Ok. I'll follow this (should have created an account!). Let me know if you need further information to help narrow it down. The bulk add is a very useful feature for us, so hopefully we can figure out what's going on. Thanks. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:15 Message: That's probably whats going on then. Will take a look time permitting and report back. Thanks for the report! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:14 Message: Yes. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:13 Message: Is your site configured to auto create a blog for new users? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-10 16:39:56
|
Bugs item #2962812, was opened at 2010-03-03 13:11 Message generated for change (Settings changed) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Aaron Axelsen (axelseaa) Summary: Bulk Add Fails to Create DB tables for New Users Initial Comment: I’m experiencing issues when blog admins bulk add a large group of users (say 30 or so users) that don’t already have blogs, so a personal blog is created for the user in addition to adding them to the admin’s blog (as per my settings to do so in LDAP Options). It appears that a number of tables are not being properly created for their personal blog. ie. wp_716_options and so forth for each blog ID. When you try to go to their blog, you just get “The blog you have requested is not installed properly. Please contact the system administrator.” and “WordPress database error: [Table 'wordpress.wp_716_options' doesn't exist]” in my WP error log. It seems that the very first user in the bulk add list has their blog created properly. Every other user in the list, it appears to succeed to the person adding, but actually fails somewhere on the backend. I am running WPMU LDAP v2.9 and WPMU 2.9.1.1. I have disabled bulk add for now as this does not happen with single user adds. Thanks ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 11:39 Message: The logic has been changed in the svn trunk to not create blogs when using bulk add. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-15 23:29 Message: Well, the feature still works - just not with the auto create blog for new user option. So i'll leave the future there, it will just need to be stated blogs will not be created - and it also needs to not attempt to create them. Thanks again for pointing this out! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-15 13:13 Message: So, unless core WP code changes, you will be removing this feature from future WPMU LDAP releases? ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-06 22:13 Message: I thought about this and looked at the code some - and then I remembered. This actually is not possible. Currently, wordpress only allows for a single new blog to be created per instance. For example, if you try to loop through a list, only the blog for the first user will be created successfully. The rest of the blogs will not be fully created and stuck in a weird state. When I get some more time, i'll investigate whether or not this changes in 3.0 - but in the 2.x trunk, I have not been able to successfully make this work. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:37 Message: I don't use the auto create option myself - so i'm sure i just missed that when going through the creation process for bulk add. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:22 Message: Wow. Actually, I was just taking a look at my DB. Seems that NO tables were created for the block of blog ID's where I've noticed the problem. So, this would include: wp_xxx_commentmeta wp_xxx_comments wp_xxx_links wp_xxx_options wp_xxx_postmeta wp_xxx_posts wp_xxx_terms wp_xxx_term_relationships wp_xxx_term_taxonomy ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:16 Message: Ok. I'll follow this (should have created an account!). Let me know if you need further information to help narrow it down. The bulk add is a very useful feature for us, so hopefully we can figure out what's going on. Thanks. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:15 Message: That's probably whats going on then. Will take a look time permitting and report back. Thanks for the report! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:14 Message: Yes. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:13 Message: Is your site configured to auto create a blog for new users? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-10 05:24:01
|
Bugs item #2826793, was opened at 2009-07-24 16:25 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2826793&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: WPMU LDAP plugin 2.8.2 + WPMU 2.8.2 gets an error after inst Initial Comment: this is the error Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'wpmuRemoveAddNewMenu' was given in C:\xampp\htdocs\wp-includes\plugin.php on line 339 ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 00:24 Message: If this error still exists in the latest versions, please re-open. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2826793&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-10 05:23:13
|
Bugs item #2944838, was opened at 2010-02-02 14:11 Message generated for change (Settings changed) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2944838&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: will not authenticate when email address contains apostrophe Initial Comment: We are using LDAP plugin version 2.8.1 and it does not allow a user with an apostrophe in the email address to authenticate. I am not sure if it is a wordpress or ldap bug. ---------------------------------------------------------------------- Comment By: John Masson () Date: 2010-02-02 18:17 Message: If you use the email address as the username then yes you're right it won't work because Wordpress tries to strip the apostrophe as an invalid character - it is Wordpress not the plugin afaik. I've gotten around it by creating local user accounts/passwords which they can use - fortunately every user with an apostrophe in their email has alias addresses without so I can use one of those to ensure they get mail notifications etc... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2944838&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-10 05:22:14
|
Bugs item #2986487, was opened at 2010-04-13 08:43 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2986487&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Carl Franks (fireartist) Assigned to: Nobody/Anonymous (nobody) Summary: test connection fails in v2.9 Initial Comment: Checking the Test Connection "yes" radio button causes the following error message in v2.9 (latest zip file on sf.net) Call to undefined function wpmuSetupLdapOptions() in C:\\wamp\\www\\blogs\\wp-content\\mu-plugins\\ldap\\lib\\wpmu_ldap_admin.functions.php on line 787 ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 00:22 Message: I think this is fixed in the trunk for the 3.0 release. If not, please reopen this. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-14 21:53 Message: if your getting a blank page - usually that means some type of error is going on. Usually its people forgetting to enable the php extension - but it sounds like thats not the case for you. Have you tried setting the php error reporting to show all errors? Currently the ldap plugin has to be enabled before test connection works - if you do it on the same save action - it would throw that error. However, getting the blank page the second time again leads me to think something may not be configured correctly on your end. Can you try the above and report back? ---------------------------------------------------------------------- Comment By: Carl Franks (fireartist) Date: 2010-04-14 14:31 Message: Thanks for the response. It's set to "enabled" in same form that contains the Test Connection option - is that the only place that it needs set? When I went back and tried it again, I failed to get the same error message - so I started again with a new database and fresh extraction of the wpmu 2.9.2 zip file. This time, once I'd copied the ldap files into the "mu-plugins" directory, went to the Site Admin > LDAP options, selected "enabled", set all the other options appropriately, selected Test Connection, and pressed Submit. - Again I got the same error message listed in the OP. However, once I went back into Site Admin > LDAP, selected Test Connection, and pressed Submit - I got no error - just a blank page. If I try using the Add User form, when I do a user search, I get a blank page. And if I try logging in with a ldap account, I get a blank page. In all of these scenarios, there is no error in the apache error logfile, and the access-log lists each POST with a 200 (success) code. I've tested my LDAP settings with an ldap browser (apache directory studio), so they shouldn't be causing problems. I'm selecting linux server, not windows. The php ldap extension is enabled in my php.ini. display_errors and log_errors are both set to "1". If I can give any further details to help track down what's going wrong, please let me know. -cheers ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-13 23:29 Message: Is the ldap plugin set to enabled or disabled when your getting this error? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2986487&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-10 05:20:26
|
Bugs item #2992502, was opened at 2010-04-26 14:12 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2992502&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Settings Aren't Copied to Users Initial Comment: I'm able to successfully authenticate against our LDAP servers, however the admin's setting aren't copied over when new blogs are created (auto create users and blogs is set to no). For example, a non-default permalink structure fails unless the user has an administrator role. As another example, I have the WP-Latex plugin which works as along as each user goes into their blog with the admin role, enters the default configuration settings, and saves them. Then the plugin works regardless of what role they have. If they don't configure the plugin that the admin has already configured it fails. Why aren't the default settings copied over to new users? Thanks. ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-05-10 00:20 Message: what default settings are you referring to? Can you explain this in more detail? It sounds like you are having a problem with new blogs, and if you have auto create users and blogs disabled, your problem is with the core wordpress code - and not this plugin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2992502&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-05-05 03:35:21
|
Bugs item #2996900, was opened at 2010-05-05 03:35 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2996900&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong default ldaps port on LDAP options Initial Comment: The description under the Server Port field on the Connection Settings page says the default LDAPS: port for Linux is 686. The default Linux ldaps port is 636. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2996900&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-04-26 19:12:04
|
Bugs item #2992502, was opened at 2010-04-26 19:12 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2992502&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Settings Aren't Copied to Users Initial Comment: I'm able to successfully authenticate against our LDAP servers, however the admin's setting aren't copied over when new blogs are created (auto create users and blogs is set to no). For example, a non-default permalink structure fails unless the user has an administrator role. As another example, I have the WP-Latex plugin which works as along as each user goes into their blog with the admin role, enters the default configuration settings, and saves them. Then the plugin works regardless of what role they have. If they don't configure the plugin that the admin has already configured it fails. Why aren't the default settings copied over to new users? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2992502&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-04-19 12:01:20
|
Support Requests item #1811582, was opened at 2007-10-11 09:15 Message generated for change (Settings changed) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959075&aid=1811582&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Install Problem (example) Group: v1.0 (example) Status: Closed Priority: 5 Private: No Submitted By: Geek (geek99) Assigned to: Nobody/Anonymous (nobody) Summary: LDAP Plugin setup problem Initial Comment: Hi, I've just tried installing wordpress mu 1.2.1 and the version 1.0.0_2 of the ldap plugin on apache 2.2.4 and PHP 5.2.4 (Windows Server 2003 + Active Directory), and straight after installing the files I get the following when I try to go to any pages in wordpress: Dock()) { return LDAP_ERROR_CONNECTION; } // Set up the search stuff $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone"); if (get_site_option('ldapLinuxWindows')) { //Linux $this->SetSearchCriteria ("(uid=$in_username)", $attributes_to_get); } else { //Windows $this->SetSearchCriteria ("(samaccountname=$in_username)", $attributes_to_get); } $this->Search(); // Did we find the user? if ($this->info[0]["dn"] == "") { $this->Disconnect(); return LDAP_ERROR_USER_NOT_FOUND; } // We always get back one more record than there really is $no_of_entries = (count ($this->info) - 1); // Authenticate again but this time as the user $this->SetAccessDetails ($this->info[0]["dn"], $in_passwd); if($this->Bind()) { // Return the user's data $user_data[LDAP_INDEX_DN] = $this->info[0]["dn"]; $user_data[LDAP_INDEX_NAME] = $this->GetLDAPInfo (LDAP_INDEX_NAME); $user_data[LDAP_INDEX_EMAIL] = $this->GetLDAPInfo (LDAP_INDEX_EMAIL); $user_data[LDAP_INDEX_GIVEN_NAME] = $this->GetLDAPInfo (LDAP_INDEX_GIVEN_NAME); $user_data[LDAP_INDEX_SURNAME] = $this->GetLDAPInfo (LDAP_INDEX_SURNAME); $user_data[LDAP_INDEX_PHONE] = $this->GetLDAPInfo (LDAP_INDEX_PHONE); // Success! $return = LDAP_OK; } else { if ($this->GetErrorNumber() == 49) { $return = LDAP_ERROR_WRONG_PASSWORD; } else { $return = $this->GetErrorNumber(); } } // Close the connection $this->Disconnect(); return $return; } function GetUserInfo ($in_username, &$user_data) { // First, connect to the LDAP server $this->Dock(); $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone", "homeDirectory", "member", "zenwmMACAddress", "uniquemember", "dn"); $this->SetSearchCriteria ("(cn=$in_username)", $attributes_to_get); $this->Search(); // Did we find the user? if ($this->info[0]["dn"] == "") { $this->Disconnect(); return LDAP_ERROR_USER_NOT_FOUND; } $user_data[LDAP_INDEX_EMAIL] = $this->GetLDAPInfo (LDAP_INDEX_EMAIL); $user_data[LDAP_INDEX_NAME] = $this->GetLDAPInfo (LDAP_INDEX_NAME); $user_data[LDAP_INDEX_GIVEN_NAME] = $this->GetLDAPInfo (LDAP_INDEX_GIVEN_NAME); $user_data[LDAP_INDEX_SURNAME] = $this->GetLDAPInfo (LDAP_INDEX_SURNAME); $user_data[LDAP_INDEX_PHONE] = $this->GetLDAPInfo (LDAP_INDEX_PHONE); $user_data[LDAP_INDEX_HOMEDIR] = $this->GetLDAPInfo (LDAP_INDEX_HOMEDIR); $user_data[LDAP_INDEX_MEMBER] = $this->GetLDAPInfo (LDAP_INDEX_MEMBER); $user_data[LDAP_INDEX_MACADDRESS] = $this->GetLDAPInfo (LDAP_INDEX_MACADDRESS); $user_data[LDAP_INDEX_UNIQUE_MEMBER] = $this->GetLDAPInfo (LDAP_INDEX_UNIQUE_MEMBER); $user_data[LDAP_INDEX_DN] = $this->GetLDAPInfo (LDAP_INDEX_DN); $this->Disconnect(); return LDAP_OK; } function DoSearch ($in_search_criteria, $in_attrs, &$data) { $this->Dock(); $this->SetSearchCriteria ($in_search_criteria, $in_attrs); $this->Search(); $this->Disconnect(); $data = $this->info; return LDAP_OK; } function GetEmailList ($in_email_list_name, &$emails, &$dns) { if ($in_email_list_name == "") return LDAP_ERROR_EMPTY_PARAM; $this->GetUserInfo ($in_email_list_name, $data); $no_of_members = count ($data[LDAP_INDEX_UNIQUE_MEMBER]); $non_empty_count = 0; for ($c=0; $c < $no_of_members; $c++) { // Get the user ID from the DN (cn= part) $parts = $this->GetDNParts ($data[LDAP_INDEX_UNIQUE_MEMBER][$c]); $parts = split ("=", $parts[0]); if ($parts[1] != "") { $this->GetUserInfo ($parts[1], $user_data); $emails[$c] = $user_data[LDAP_INDEX_EMAIL]; $dns[$c] = $data[LDAP_INDEX_UNIQUE_MEMBER][$c]; $non_empty_count++; } } return $non_empty_count; } function GetDNParts ($in_dn) { return ldap_explode_dn ($in_dn, 0); } } ?> My LDAP configuration look like this : LDAP Server : im-dc.inspire.ma LDAP Server Port = 389 Search DN = cn=users,dc=inspire,dc=ma User DN = administrator Password = ***** Any ideas what is wrong? Thanks ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-17 23:19 Message: tVnkjz <a href="http://vgukubnlnchx.com/">vgukubnlnchx</a>, [url=http://dmnoaxjjeilm.com/]dmnoaxjjeilm[/url], [link=http://oyksctrmcion.com/]oyksctrmcion[/link], http://lixzgpwpzayn.com/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-06-13 06:02 Message: Logged In: NO I have been able to authenticate the user through LDAP plugin 1.3.0 with WordPress Mu 1.3.3. I was getting "white screen of death" .Becoz,I had not configured Ldap properly with PHP. Then later, it was redirecting me to the login screen saying wrong username or password. The problem was with the code !!!. (the Ldap Entry structure based on which the search is done) The problem that occurs are bcoz of these lines 1.inside LDAP_ro Authenticate function : $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone"); I dint have the Ldap entry with following attributes. I donno from where these attributes are defined. It was not available in OPENLDAP. I changed it according to my Ldap entry structure. 2. The search criteria!!!!!! $this->SetSearchCriteria ("(samaccountname=$in_username)", $attributes_to_get); I donno in which Ldap we will have this attribute !!! samaccountname!!!! I changed it to $this->SetSearchCriteria ("(cn=$in_username)", $attributes_to_get); I did not find any documentation for this plugin apart from the description of fields in the Ldap options admin screen.The Ldap is different for different people. there should be an option for setting search criteria(filter) & for getting the attributes. ---------------------------------------------------------------------- Comment By: Alex Coles (alexbcoles) Date: 2007-11-07 04:34 Message: Logged In: YES user_id=382403 Originator: NO I had the same issue. Try changing the first lines of ldap/ldap_ro.php and ldap/ldap_core.php from: <? to <?php Then try again. ---------------------------------------------------------------------- Comment By: Sean Wedig (doorknobslayer) Date: 2007-10-12 17:14 Message: Logged In: YES user_id=206759 Originator: NO After a bit of IM discussion with geek99, I found that the LDAP code inherited from the originating plugins used PHP short tags, which was a minor problem. Ultimately, though, geek99 updated to "the latest version" (from WPMUDev.org, I think), and it fixed the problem. Closing this out. ---------------------------------------------------------------------- Comment By: Geek (geek99) Date: 2007-10-11 11:08 Message: Logged In: YES user_id=1910901 Originator: YES the line 27 of the ldap_ro.php code look like : class LDAP_ro extends LDAP { function Authenticate ($in_username, $in_passwd, &$user_data) { // First, connect to the LDAP server ---Line 27 : if(!$this->Dock()) { return LDAP_ERROR_CONNECTION; } // Set up the search stuff $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone"); if (get_site_option('ldapLinuxWindows')) { //Linux $this->SetSearchCriteria ("(uid=$in_username)", $attributes_to_get); } else { //Windows $this->SetSearchCriteria ("(cn=$in_username)", $attributes_to_get); } $this->Search(); ---------------------------------------------------------------------- Comment By: Sean Wedig (doorknobslayer) Date: 2007-10-11 10:06 Message: Logged In: YES user_id=206759 Originator: NO Hmm... I'm sure you've guessed that it looks like it's displaying the code. A quick search shows that it seems to be breaking on line 27 of ldap_ro.php... Here's a shot-in-the-dark guess: Take a look at the code and see what line 27 looks like. It should be " if(!$this->Dock()) {" but it's possible that something's amiss with the line, which is causing it to close the PHP tags. So instead of executing the code, it's just displaying it (as if it were page text). It may be an encoding issue. What is the encoding of the file on your development box? -sean ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959075&aid=1811582&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-04-18 04:19:51
|
Support Requests item #1811582, was opened at 2007-10-11 14:15 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959075&aid=1811582&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Install Problem (example) Group: v1.0 (example) Status: Closed Priority: 5 Private: No Submitted By: Geek (geek99) Assigned to: Nobody/Anonymous (nobody) Summary: LDAP Plugin setup problem Initial Comment: Hi, I've just tried installing wordpress mu 1.2.1 and the version 1.0.0_2 of the ldap plugin on apache 2.2.4 and PHP 5.2.4 (Windows Server 2003 + Active Directory), and straight after installing the files I get the following when I try to go to any pages in wordpress: Dock()) { return LDAP_ERROR_CONNECTION; } // Set up the search stuff $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone"); if (get_site_option('ldapLinuxWindows')) { //Linux $this->SetSearchCriteria ("(uid=$in_username)", $attributes_to_get); } else { //Windows $this->SetSearchCriteria ("(samaccountname=$in_username)", $attributes_to_get); } $this->Search(); // Did we find the user? if ($this->info[0]["dn"] == "") { $this->Disconnect(); return LDAP_ERROR_USER_NOT_FOUND; } // We always get back one more record than there really is $no_of_entries = (count ($this->info) - 1); // Authenticate again but this time as the user $this->SetAccessDetails ($this->info[0]["dn"], $in_passwd); if($this->Bind()) { // Return the user's data $user_data[LDAP_INDEX_DN] = $this->info[0]["dn"]; $user_data[LDAP_INDEX_NAME] = $this->GetLDAPInfo (LDAP_INDEX_NAME); $user_data[LDAP_INDEX_EMAIL] = $this->GetLDAPInfo (LDAP_INDEX_EMAIL); $user_data[LDAP_INDEX_GIVEN_NAME] = $this->GetLDAPInfo (LDAP_INDEX_GIVEN_NAME); $user_data[LDAP_INDEX_SURNAME] = $this->GetLDAPInfo (LDAP_INDEX_SURNAME); $user_data[LDAP_INDEX_PHONE] = $this->GetLDAPInfo (LDAP_INDEX_PHONE); // Success! $return = LDAP_OK; } else { if ($this->GetErrorNumber() == 49) { $return = LDAP_ERROR_WRONG_PASSWORD; } else { $return = $this->GetErrorNumber(); } } // Close the connection $this->Disconnect(); return $return; } function GetUserInfo ($in_username, &$user_data) { // First, connect to the LDAP server $this->Dock(); $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone", "homeDirectory", "member", "zenwmMACAddress", "uniquemember", "dn"); $this->SetSearchCriteria ("(cn=$in_username)", $attributes_to_get); $this->Search(); // Did we find the user? if ($this->info[0]["dn"] == "") { $this->Disconnect(); return LDAP_ERROR_USER_NOT_FOUND; } $user_data[LDAP_INDEX_EMAIL] = $this->GetLDAPInfo (LDAP_INDEX_EMAIL); $user_data[LDAP_INDEX_NAME] = $this->GetLDAPInfo (LDAP_INDEX_NAME); $user_data[LDAP_INDEX_GIVEN_NAME] = $this->GetLDAPInfo (LDAP_INDEX_GIVEN_NAME); $user_data[LDAP_INDEX_SURNAME] = $this->GetLDAPInfo (LDAP_INDEX_SURNAME); $user_data[LDAP_INDEX_PHONE] = $this->GetLDAPInfo (LDAP_INDEX_PHONE); $user_data[LDAP_INDEX_HOMEDIR] = $this->GetLDAPInfo (LDAP_INDEX_HOMEDIR); $user_data[LDAP_INDEX_MEMBER] = $this->GetLDAPInfo (LDAP_INDEX_MEMBER); $user_data[LDAP_INDEX_MACADDRESS] = $this->GetLDAPInfo (LDAP_INDEX_MACADDRESS); $user_data[LDAP_INDEX_UNIQUE_MEMBER] = $this->GetLDAPInfo (LDAP_INDEX_UNIQUE_MEMBER); $user_data[LDAP_INDEX_DN] = $this->GetLDAPInfo (LDAP_INDEX_DN); $this->Disconnect(); return LDAP_OK; } function DoSearch ($in_search_criteria, $in_attrs, &$data) { $this->Dock(); $this->SetSearchCriteria ($in_search_criteria, $in_attrs); $this->Search(); $this->Disconnect(); $data = $this->info; return LDAP_OK; } function GetEmailList ($in_email_list_name, &$emails, &$dns) { if ($in_email_list_name == "") return LDAP_ERROR_EMPTY_PARAM; $this->GetUserInfo ($in_email_list_name, $data); $no_of_members = count ($data[LDAP_INDEX_UNIQUE_MEMBER]); $non_empty_count = 0; for ($c=0; $c < $no_of_members; $c++) { // Get the user ID from the DN (cn= part) $parts = $this->GetDNParts ($data[LDAP_INDEX_UNIQUE_MEMBER][$c]); $parts = split ("=", $parts[0]); if ($parts[1] != "") { $this->GetUserInfo ($parts[1], $user_data); $emails[$c] = $user_data[LDAP_INDEX_EMAIL]; $dns[$c] = $data[LDAP_INDEX_UNIQUE_MEMBER][$c]; $non_empty_count++; } } return $non_empty_count; } function GetDNParts ($in_dn) { return ldap_explode_dn ($in_dn, 0); } } ?> My LDAP configuration look like this : LDAP Server : im-dc.inspire.ma LDAP Server Port = 389 Search DN = cn=users,dc=inspire,dc=ma User DN = administrator Password = ***** Any ideas what is wrong? Thanks ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-18 04:19 Message: tVnkjz <a href="http://vgukubnlnchx.com/">vgukubnlnchx</a>, [url=http://dmnoaxjjeilm.com/]dmnoaxjjeilm[/url], [link=http://oyksctrmcion.com/]oyksctrmcion[/link], http://lixzgpwpzayn.com/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-06-13 11:02 Message: Logged In: NO I have been able to authenticate the user through LDAP plugin 1.3.0 with WordPress Mu 1.3.3. I was getting "white screen of death" .Becoz,I had not configured Ldap properly with PHP. Then later, it was redirecting me to the login screen saying wrong username or password. The problem was with the code !!!. (the Ldap Entry structure based on which the search is done) The problem that occurs are bcoz of these lines 1.inside LDAP_ro Authenticate function : $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone"); I dint have the Ldap entry with following attributes. I donno from where these attributes are defined. It was not available in OPENLDAP. I changed it according to my Ldap entry structure. 2. The search criteria!!!!!! $this->SetSearchCriteria ("(samaccountname=$in_username)", $attributes_to_get); I donno in which Ldap we will have this attribute !!! samaccountname!!!! I changed it to $this->SetSearchCriteria ("(cn=$in_username)", $attributes_to_get); I did not find any documentation for this plugin apart from the description of fields in the Ldap options admin screen.The Ldap is different for different people. there should be an option for setting search criteria(filter) & for getting the attributes. ---------------------------------------------------------------------- Comment By: Alex Coles (alexbcoles) Date: 2007-11-07 10:34 Message: Logged In: YES user_id=382403 Originator: NO I had the same issue. Try changing the first lines of ldap/ldap_ro.php and ldap/ldap_core.php from: <? to <?php Then try again. ---------------------------------------------------------------------- Comment By: Sean Wedig (doorknobslayer) Date: 2007-10-12 22:14 Message: Logged In: YES user_id=206759 Originator: NO After a bit of IM discussion with geek99, I found that the LDAP code inherited from the originating plugins used PHP short tags, which was a minor problem. Ultimately, though, geek99 updated to "the latest version" (from WPMUDev.org, I think), and it fixed the problem. Closing this out. ---------------------------------------------------------------------- Comment By: Geek (geek99) Date: 2007-10-11 16:08 Message: Logged In: YES user_id=1910901 Originator: YES the line 27 of the ldap_ro.php code look like : class LDAP_ro extends LDAP { function Authenticate ($in_username, $in_passwd, &$user_data) { // First, connect to the LDAP server ---Line 27 : if(!$this->Dock()) { return LDAP_ERROR_CONNECTION; } // Set up the search stuff $attributes_to_get = array ("fullName", "mail", "givenName", "sn", "phone"); if (get_site_option('ldapLinuxWindows')) { //Linux $this->SetSearchCriteria ("(uid=$in_username)", $attributes_to_get); } else { //Windows $this->SetSearchCriteria ("(cn=$in_username)", $attributes_to_get); } $this->Search(); ---------------------------------------------------------------------- Comment By: Sean Wedig (doorknobslayer) Date: 2007-10-11 15:06 Message: Logged In: YES user_id=206759 Originator: NO Hmm... I'm sure you've guessed that it looks like it's displaying the code. A quick search shows that it seems to be breaking on line 27 of ldap_ro.php... Here's a shot-in-the-dark guess: Take a look at the code and see what line 27 looks like. It should be " if(!$this->Dock()) {" but it's possible that something's amiss with the line, which is causing it to close the PHP tags. So instead of executing the code, it's just displaying it (as if it were page text). It may be an encoding issue. What is the encoding of the file on your development box? -sean ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959075&aid=1811582&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-04-16 04:29:40
|
Bugs item #2962812, was opened at 2010-03-03 13:11 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Aaron Axelsen (axelseaa) Summary: Bulk Add Fails to Create DB tables for New Users Initial Comment: I’m experiencing issues when blog admins bulk add a large group of users (say 30 or so users) that don’t already have blogs, so a personal blog is created for the user in addition to adding them to the admin’s blog (as per my settings to do so in LDAP Options). It appears that a number of tables are not being properly created for their personal blog. ie. wp_716_options and so forth for each blog ID. When you try to go to their blog, you just get “The blog you have requested is not installed properly. Please contact the system administrator.” and “WordPress database error: [Table 'wordpress.wp_716_options' doesn't exist]” in my WP error log. It seems that the very first user in the bulk add list has their blog created properly. Every other user in the list, it appears to succeed to the person adding, but actually fails somewhere on the backend. I am running WPMU LDAP v2.9 and WPMU 2.9.1.1. I have disabled bulk add for now as this does not happen with single user adds. Thanks ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-15 23:29 Message: Well, the feature still works - just not with the auto create blog for new user option. So i'll leave the future there, it will just need to be stated blogs will not be created - and it also needs to not attempt to create them. Thanks again for pointing this out! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-15 13:13 Message: So, unless core WP code changes, you will be removing this feature from future WPMU LDAP releases? ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-06 22:13 Message: I thought about this and looked at the code some - and then I remembered. This actually is not possible. Currently, wordpress only allows for a single new blog to be created per instance. For example, if you try to loop through a list, only the blog for the first user will be created successfully. The rest of the blogs will not be fully created and stuck in a weird state. When I get some more time, i'll investigate whether or not this changes in 3.0 - but in the 2.x trunk, I have not been able to successfully make this work. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:37 Message: I don't use the auto create option myself - so i'm sure i just missed that when going through the creation process for bulk add. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:22 Message: Wow. Actually, I was just taking a look at my DB. Seems that NO tables were created for the block of blog ID's where I've noticed the problem. So, this would include: wp_xxx_commentmeta wp_xxx_comments wp_xxx_links wp_xxx_options wp_xxx_postmeta wp_xxx_posts wp_xxx_terms wp_xxx_term_relationships wp_xxx_term_taxonomy ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:16 Message: Ok. I'll follow this (should have created an account!). Let me know if you need further information to help narrow it down. The bulk add is a very useful feature for us, so hopefully we can figure out what's going on. Thanks. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:15 Message: That's probably whats going on then. Will take a look time permitting and report back. Thanks for the report! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 13:14 Message: Yes. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 13:13 Message: Is your site configured to auto create a blog for new users? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2962812&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-04-15 18:13:42
|
Support Requests item #2962812, was opened at 2010-03-03 19:11 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959075&aid=2962812&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Bulk Add Fails to Create DB tables for New Users Initial Comment: I’m experiencing issues when blog admins bulk add a large group of users (say 30 or so users) that don’t already have blogs, so a personal blog is created for the user in addition to adding them to the admin’s blog (as per my settings to do so in LDAP Options). It appears that a number of tables are not being properly created for their personal blog. ie. wp_716_options and so forth for each blog ID. When you try to go to their blog, you just get “The blog you have requested is not installed properly. Please contact the system administrator.” and “WordPress database error: [Table 'wordpress.wp_716_options' doesn't exist]” in my WP error log. It seems that the very first user in the bulk add list has their blog created properly. Every other user in the list, it appears to succeed to the person adding, but actually fails somewhere on the backend. I am running WPMU LDAP v2.9 and WPMU 2.9.1.1. I have disabled bulk add for now as this does not happen with single user adds. Thanks ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-04-15 18:13 Message: So, unless core WP code changes, you will be removing this feature from future WPMU LDAP releases? ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-07 03:13 Message: I thought about this and looked at the code some - and then I remembered. This actually is not possible. Currently, wordpress only allows for a single new blog to be created per instance. For example, if you try to loop through a list, only the blog for the first user will be created successfully. The rest of the blogs will not be fully created and stuck in a weird state. When I get some more time, i'll investigate whether or not this changes in 3.0 - but in the 2.x trunk, I have not been able to successfully make this work. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:37 Message: I don't use the auto create option myself - so i'm sure i just missed that when going through the creation process for bulk add. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:22 Message: Wow. Actually, I was just taking a look at my DB. Seems that NO tables were created for the block of blog ID's where I've noticed the problem. So, this would include: wp_xxx_commentmeta wp_xxx_comments wp_xxx_links wp_xxx_options wp_xxx_postmeta wp_xxx_posts wp_xxx_terms wp_xxx_term_relationships wp_xxx_term_taxonomy ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:16 Message: Ok. I'll follow this (should have created an account!). Let me know if you need further information to help narrow it down. The bulk add is a very useful feature for us, so hopefully we can figure out what's going on. Thanks. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:15 Message: That's probably whats going on then. Will take a look time permitting and report back. Thanks for the report! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-03 19:14 Message: Yes. ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-03-03 19:13 Message: Is your site configured to auto create a blog for new users? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959075&aid=2962812&group_id=196841 |
|
From: SourceForge.net <no...@so...> - 2010-04-15 02:53:22
|
Bugs item #2986487, was opened at 2010-04-13 08:43 Message generated for change (Comment added) made by axelseaa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2986487&group_id=196841 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Carl Franks (fireartist) Assigned to: Nobody/Anonymous (nobody) Summary: test connection fails in v2.9 Initial Comment: Checking the Test Connection "yes" radio button causes the following error message in v2.9 (latest zip file on sf.net) Call to undefined function wpmuSetupLdapOptions() in C:\\wamp\\www\\blogs\\wp-content\\mu-plugins\\ldap\\lib\\wpmu_ldap_admin.functions.php on line 787 ---------------------------------------------------------------------- >Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-14 21:53 Message: if your getting a blank page - usually that means some type of error is going on. Usually its people forgetting to enable the php extension - but it sounds like thats not the case for you. Have you tried setting the php error reporting to show all errors? Currently the ldap plugin has to be enabled before test connection works - if you do it on the same save action - it would throw that error. However, getting the blank page the second time again leads me to think something may not be configured correctly on your end. Can you try the above and report back? ---------------------------------------------------------------------- Comment By: Carl Franks (fireartist) Date: 2010-04-14 14:31 Message: Thanks for the response. It's set to "enabled" in same form that contains the Test Connection option - is that the only place that it needs set? When I went back and tried it again, I failed to get the same error message - so I started again with a new database and fresh extraction of the wpmu 2.9.2 zip file. This time, once I'd copied the ldap files into the "mu-plugins" directory, went to the Site Admin > LDAP options, selected "enabled", set all the other options appropriately, selected Test Connection, and pressed Submit. - Again I got the same error message listed in the OP. However, once I went back into Site Admin > LDAP, selected Test Connection, and pressed Submit - I got no error - just a blank page. If I try using the Add User form, when I do a user search, I get a blank page. And if I try logging in with a ldap account, I get a blank page. In all of these scenarios, there is no error in the apache error logfile, and the access-log lists each POST with a 200 (success) code. I've tested my LDAP settings with an ldap browser (apache directory studio), so they shouldn't be causing problems. I'm selecting linux server, not windows. The php ldap extension is enabled in my php.ini. display_errors and log_errors are both set to "1". If I can give any further details to help track down what's going wrong, please let me know. -cheers ---------------------------------------------------------------------- Comment By: Aaron Axelsen (axelseaa) Date: 2010-04-13 23:29 Message: Is the ldap plugin set to enabled or disabled when your getting this error? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=959074&aid=2986487&group_id=196841 |
