cjhaas
(@chrisvendiadvertisingcom)
I just wanted to thank you for this! I was print_r‘ing all around trying to figure out why it appeared that my settings weren’t being saved!
I have created a branch that contains the code to run this plugin as a multisite network-activated plugin.
In normal site-by-site activate it works as the original.
If network-activated it will do the following instead:
- move the settings page to the network admin settings area
- save all settings at the network level so they affect all sites in the multisite installation.
https://github.com/sjparsons/simple-ldap-login/tree/network-version
I’ve submitted a pull request to Clifton, the original author, and hopefully this can be included into the plugin. Comments and feedback are welcome on the pull request.
https://github.com/clifgriffin/simple-ldap-login/pull/11
Hi Sam,
First, thank you for the time you’ve invested in adding to the code that Clifton developed to integrate WordPress with an LDAP directory. Your enhancements answered a bunch of the questions I had when first installing and configuring the plugin. I am running the latest version of simple-ldap-login, which includes pull request #11 – your code.
Since you say you’re running a relatively large WordPress Network with multiple sites and many users logging in via LDAP, I thought I’d run by you two issues I’m seeing.
1. I am experiencing a very similar problem as the one described by MerlIAV in this post. Essentially, when a new user logs into one of the network sites for the first time using his LDAP credentials, his WordPress account is created and he is given subscriber status on that site. Perfect! However, if that same user then tries to log into another site on the network, WordPress successfully logs him but doesn’t add him as a subscriber on the second site. Instead, it just logs him in and redirects his focus back to the first site. MerlIAV proposed a code edit in order to address this scenario, but I wanted to check with you since I believe you must have run into this situation on your site.
2. Through extensive testing, I’ve noticed that this second issue is present with the simple-ldap-login plugin regardless of whether the WordPress install is a multisite network or a singlesite blog. Here’s the scenario. User A logs into the site with LDAP credentials, and his WP account is automatically created. Good. That user is then given Administrator permissions on the site by an existing admin, and posts several articles successfully. Then, if a user clicks on the author’s name on any of the posts, hoping to get a list of all posts by that user, WordPress returns its generic “Not Found. It looks like nothing was found at this location” error. If the exact same set of tasks is completed with a user whose WP account was manually created in WP (not auto-created via LDAP), clicking on the user’s name in a post successfully returns the list of all posts by that user. I’ve looked in the database, but can’t see a difference between the way LDAP-created and native-WP-created accounts exist.
I guess I’m kind of hoping that others have seen these issues as well, and would love to know how they’ve been addressed.
Thanks
Joe
