NetTalk Central

NetTalk Web Server => Web Server - Ask For Help => Topic started by: kevin plummer on March 19, 2008, 04:02:35 AM

Title: Enter Key
Post by: kevin plummer on March 19, 2008, 04:02:35 AM

On the generic login screen how do I set the login button to fire after the user enters a password and hits the enter key?

Cheers,

Kevin

Title: Re: Enter Key
Post by: Johan de Klerk on March 19, 2008, 04:59:55 AM

Hi Kevin,

This was a problem with one of the Pre-Releases and Bruce fixed.

It is fixed in the 4.30 final release.

Regards

Johan de Klerk

Title: Re: Enter Key
Post by: kevin plummer on March 19, 2008, 02:24:38 PM

Bruce, was there another version after PR7 or is 4.30 Official the same? If I upgrade will all my users have to clear their cache? I had a real headache with this last time...

Title: Re: Enter Key
Post by: Mike Grigsby on March 20, 2008, 07:27:35 AM

Also, to carry on from my thread, I did upgrade to the official 4.30 release (I was on the last pre release before... 7?), cleared the cache, and still have the problem with the Enter key not working.  This is a real problem for me that I need to get resolved. I'm not sure how to fix it. I could temporarily break the generated code if I could follow how it's being implemented, but it's not obvious to me.

Title: Re: Enter Key
Post by: Bruce on March 21, 2008, 09:43:55 AM

Hi Kevin,

I think the enter key was corrected in the Pr7a build. However I do recommend you upgrade to the "official" release as there were a couple of minor changes.

Mike - do you have an example of the enter key still being a problem - it seems to be sorted in the various shipping examples...

Cheers
Bruce

Title: Re: Enter Key
Post by: kevin plummer on March 22, 2008, 12:57:45 PM

Bruce, will users need to clear their Cache if I upgrade?

Title: Re: Enter Key
Post by: Bruce on March 23, 2008, 10:51:27 PM

Hi Kevin,

I don't think there were any major changes to the scripts. Pressing Ctrl-F5 on their side would be a "good thing" (but it'll happen naturally within a few days anyway.) If anything it's possible the bug fix was in the scripts, so it might solve their problem.

Cheers
Bruce