Ok, I made those changes.  I actually was doing the sha1 that way
before, but changed it to see if that was the problem.  If you take a
look at it now, I think you'll laugh.  Basically, the alert shows the
correct info (the sha1'd password), but what is displayed is still
plain text.  I'm wondering if this is related to the issue with the
plugin sending info twice (one of the other threads going around right
now).

On 2/16/07, Benjamin Sterling <[EMAIL PROTECTED]> wrote:
> Brian,
> two things and a suggestion:
>
> try
>
> $( '#account_pass' ).val(hex_sha1( $( '#account_pass' ).val()));
>
> $( '#account_pass_confirm' ).val(hex_sha1( $( '#account_pass_confirm'
> ).val()));
>
> instead of
>
> accform.account_pass.value = hex_sha1( accform.account_pass.value );
> accform.account_pass_confirm.value = hex_sha1(
> accform.account_pass_confirm.value );
>
>
> Just before you do "return true;" alert($( '#account_pass' ).val()); just to
> make sure it is converted.
>
> also, I would suggest that you don't do
>
>  if(error) { // errors
>  $( '#account_pass' ).val("");
>  $( '#account_pass_confirm' ).val("");
>  return false;
> }
>
> that will make your end user frustrated, IMO
>
> hope this helps
>
> --
>
> Benjamin Sterling
> http://www.KenzoMedia.com
>  http://www.KenzoHosting.com
> _______________________________________________
> jQuery mailing list
> discuss@jquery.com
> http://jquery.com/discuss/
>
>


-- 
Brian Ronk

_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Reply via email to