vemi2709

I seem to have found a solution, I added an authentication filter at line 1403:
if($boolRestoreBlog) restore_current_blog();
add_filter(‘authenticate’,’wp_authenticate_username_password’,20,3);
return $userData;
At least now everything seems to work ok also when ‘Automatically Register Authenticated Users?’ is set to Yes.
I hope there are no security flaws I have made by doing this? 8) …

No luck.

One setting can fix the problem (though we cannot use it in our production), I changed the setting ‘Automatically Register Authenticated Users’ from Yes to No. -VeM-

You couldn’t by any chance give an exact example how to do it ?? ? I tried it myself but had no luck.

Just like that. We have other applications where users can login using both their username (samaccountname) and email ([email protected]) and some of them try to login to WordPress also with email. So, Wordpess username should be samaccountname and user should be able to use both samaccountname and email to login ??

It’s ok if the email is sent when user’s blog’s visibility is changed but now it seems to send an email concerning the visibility change of the main site (ID 1) when in fact a user creates a new site and chooses any other visibility than the default. That’s a bit confusing. We’ll comment out the above line for now so we don’t get those ‘false alarms’. Thanx.