According to http://sourceforge.net/forum/forum.php?forum_id=823681 the WPMU LDAP Plugin is not working with 1.5.1. I can confirm this on a test machine.
Is anyone using LDAP authentication (either this plugin, or another one) with 1.5.1?
Thanks!
According to http://sourceforge.net/forum/forum.php?forum_id=823681 the WPMU LDAP Plugin is not working with 1.5.1. I can confirm this on a test machine.
Is anyone using LDAP authentication (either this plugin, or another one) with 1.5.1?
Thanks!
Hi,
I'm trying to get the plugin working on 1.5.1 but it looks like there is a bigger fix needed to do so.
Right now I'm trying to locate the problem looks like the plugin isnt used though it's activated in the siteadmin-interface.
when you try to login a ldap user it says that the username doesnt exist because
get_userdatabylogin()
returns false,
get_userdatabylogin() checks the SQL database for the user thats why it returns false cause it should check ldap for the user not sql.
hope to find out more if I do so I'll post it here
Take the latest code from svn, it works great:
http://wpmu-ldap.svn.sourceforge.net/viewvc/wpmu-ldap/trunk/
I have tried this and all I get is errors all over the place, Javascript errors, plug-in activation errors saying the function has already been declared, cannot redeclare. The SVN code is not up to snuff.
I gather you want folks here to make guesses as to what errors you're seeing and what issues you're having?
The error I'm seeing is "Fatal error: Cannot redeclare wp_new_user_notification() (previously declared in C:\Inetpub\htdocs\blogs\wp-includes\pluggable.php:929) in C:\Inetpub\htdocs\blogs\wp-content\plugins\ldap\lib\wpmu_ldap_admin.functions.php on line 542
" when trying to activate it, from the plugins directory. I get the same error if I put it in the mu-plugins directory as well, only the page doesn't even load, just shows the error. Therefore I cannot use it at all.
If I disable the original function in the pluggable.php file, then try it, all I get is javascript errors and "cannot modify header because it's already declared". Hence, why I said that the code is not up to snuff.
Sounds like you should be contacting the plugin author.