Timeline for Redirect user using the 'wp_login_failed' action hook if the error is 'empty_username' or 'empty_password'
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S May 29, 2019 at 17:26 | history | suggested | CommunityBot | CC BY-SA 4.0 |
Added priority suggested in the comments
|
| May 29, 2019 at 16:35 | review | Suggested edits | |||
| S May 29, 2019 at 17:26 | |||||
| Oct 17, 2018 at 9:58 | comment | added | GigiSan |
@TomDyer is right, deducing from the question the correct statement should be add_filter( 'authenticate', function(...) {...}, 99, 3);
|
|
| Sep 15, 2018 at 1:19 | comment | added | Cush |
The $username parameter in wp_login_failed is a string according to the developer docs for wp_login_failed - how do we get an error object from it now?
|
|
| Mar 6, 2018 at 12:33 | comment | added | Tom Dyer | Upvoted as a good answer but please correct the issue with the authenticate hook. Without passing a priority and number or arguments, this will always trigger a failed login action due to the way filters and hooks work (by default, they only allow one argument to be passed to the method). | |
| S Apr 4, 2015 at 16:53 | history | suggested | Gabriel | CC BY-SA 3.0 |
Remove code formatting from explanation at top, improve grammar, misc
|
| Apr 4, 2015 at 15:39 | review | Suggested edits | |||
| S Apr 4, 2015 at 16:53 | |||||
| Apr 4, 2015 at 10:37 | history | edited | palash140 | CC BY-SA 3.0 |
added 668 characters in body
|
| Apr 4, 2015 at 8:10 | review | Late answers | |||
| Apr 4, 2015 at 8:28 | |||||
| Apr 4, 2015 at 7:55 | review | First posts | |||
| Apr 4, 2015 at 9:45 | |||||
| Apr 4, 2015 at 7:53 | history | answered | palash140 | CC BY-SA 3.0 |