moff

If it helps, we just made an extra custom field and use that as the display in the backend list. You just have to change the label on description to allocate it to something else. users will often just put a . in the field to pass validation. Annoying, but works for us.

That’s great @gauravdohole! That’s even better than downloading. I hope that was new functionality in the update, because I don’t remember seeing that in Advanced Setting previously! Thanks for your prompt response.

This is a really great idea. I’d be most interested in the same functionality.

thanks for posting.

Thanks @caimin_nwl, I had found the wp_signon code in the login-with-ajax.php, but it looks like it authenticates just like the native WordPress login form. I cant find any differences with the login method used in Login With Ajax to account for why it fails to authenticate against Active Directory, while the WordPress default form does it just fine.

I expect the Active Directory plugin I am using is intercepting the login form submission to then authenticate against Active Directory, so the only reason I can think of why Login With Ajax doesn’t work, is a difference in form submission.

Maybe it’s just the nature of Ajax form submission that preventing the other plugin from intercepting the form?