Mercurial > pidgin.yaz
changeset 29386:e1dd357fc494
Add back Paul's error message from revision 219b3128f3d96b126a9ed9aff2d2f3277e69dbd4
(disapproved in revision e2fb4cc366c55b86f89304bddac780a92ff73394) with
a slightly improved error message. Thanks for adding this in the first place,
Paul! Sorry it took me months to re-instate it after I complained!
Hopefully AOL won't start asking users to fill out CAPTCHAs in order to
log in, because that would be messy (both our implementation and the
user experience).
| author | Mark Doliner <mark@kingant.net> |
|---|---|
| date | Sun, 07 Feb 2010 09:30:49 +0000 |
| parents | acf7f7637669 |
| children | 88c462455bc8 b62d06a0e8ef |
| files | libpurple/protocols/oscar/clientlogin.c |
| diffstat | 1 files changed, 5 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/libpurple/protocols/oscar/clientlogin.c Sun Feb 07 08:43:26 2010 +0000 +++ b/libpurple/protocols/oscar/clientlogin.c Sun Feb 07 09:30:49 2010 +0000 @@ -413,6 +413,11 @@ purple_connection_error_reason(gc, PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED, _("Incorrect password")); + } else if (status_code == 330 && status_detail_code == 3015) { + purple_connection_error_reason(gc, + PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED, + _("Server requested that you fill out a CAPTCHA in order to " + "sign in, but this client does not currently support CAPTCHAs.")); } else if (status_code == 401 && status_detail_code == 3019) { purple_connection_error_reason(gc, PURPLE_CONNECTION_ERROR_OTHER_ERROR,