mls.lds.org
Posted: Tue Jul 13, 2010 8:01 am
I've noticed that I can't log into http://mls.lds.org while using Chrome - I get a bad password error. Logging in with MSIE using the same password works fine.
Community Discussion of Church Technology
https://tech.churchofjesuschrist.org/forum/
https://tech.churchofjesuschrist.org/forum/viewtopic.php?t=5343
Running WinXp Pro here and Chrome won't let me in either.aclawson wrote:Tried it six or seven time, even closing out the browser then going back in and it always said invalid password. Tried it in MSIE and it worked on the first try.
Nice catch. Yes, this is verified with Chrome in Win 7 as well. Chrome must mangle the entry somehow when you hit ENTER.techgy wrote:Edit: Found the problem. When you enter the Unit ID and password do NOT hit the ENTER key. Click the Submit button instead. Pressing the ENTER key will result in a login failure.
If I just hit ENTER in IE8, it just sits there. It's been like that as long as I can remember.techgy wrote:Edit: Found the problem. When you enter the Unit ID and password do NOT hit the ENTER key. Click the Submit button instead. Pressing the ENTER key will result in a login failure.
Ah. Now we're getting closer to the root of the problem, which (IMO) is some poorly coded HTML. I never paid much attention, but Firefox exibits the same behavior.RussellHltn wrote:If I just hit ENTER in IE8, it just sits there. It's been like that as long as I can remember.
First of all the site is primarily for the Stake Technology Specialist to download software to support the Stake/Ward computers. Access is generally limited to him. If that's you then you should contact your stake clerk.markgnorthcott wrote:I've never even heard of this site until now. where do we get the unit's password from?
Maybe. Somewhere in the back of my mind I thought I read of a deliberate decision to do it that way. Something about legal language. For example, I notice for the CDOL, the button is labeled "I agree", so you'd have to "agree" to get in.Mikerowaved wrote:Ah. Now we're getting closer to the root of the problem, which (IMO) is some poorly coded HTML.