Hi all! Quick question... I have a site in progress based on the C# version of the book: http://sigilent.com

My question is: when I go to the Login page (link on top right) and click on Login with all fields blank, the Required Field Validators don't seem to kick in and catch it. Instead, the login proceeds anyway (with blank username and password) and at the top, you get this:

"Welcome, "

When this was being tested locally (http://localhost/Sigilent), I wasn't seeing this problem at all! Any ideas?

Thanks much!

-----
mencher cat, mencher cat. boo. cattydear. what a lovely!

__________________
-----
mencher cat, mencher cat. boo. cattydear. what a lovely!

I think I solved it, never mind. For anyone who might have encountered this as well: The default "login" page was hardcoded to properly work using the "localhost/Sigilent" path on my workstation, and so when deployed to the actual server, it was dying. Changing this seems to have worked...

Allen

-----
mencher cat, mencher cat. boo. cattydear. what a lovely!

Hi everyone! I have a follow-up question that's related to my original problem (which got solved).

My new question is: when I click on the Login button of the Login.aspx page, what could be causing the validators to NOT kick in until after the page submits at least once? Unlike before, no "bogus" login occurs ("Welcome, "). It does complain that you can't login with a blank username or password (or a wrong username/password combination).

However, now it seems like the page has to submit at least once, giving me the annoying summary message "Sorry, we could not log you in as . Please check your username or password." BEFORE I even see the "please enter username/password" warnings.

I've checked everything top to bottom it seems, but I can't for the life of me figure out why this is happening.

Any ideas very welcome!

Allen

-----
mencher cat, mencher cat. boo. cattydear. what a lovely!

Hello, all. In typical lame fashion, I figured out (again) exactly what was wrong probably not less than 10 minutes after posting, although after spending several hours fruitlessly just prior. For the benefit of anyone experiencing this:

Basically, this was because the validation scripts located at "\aspnet_client\system_web\1_1_4322" (specifically webuivalidation.js) were not being found by the web application (sigilent.com) in it's default location off of C:\inetput\wwwroot. I had placed the site's files in a different directory and drive. All I had to do was copy the files in 1_1_4322, keeping the same folder structure, off of the application's root directory, and boom, everything's working normally again...

Cheers,

Allen

-----
mencher cat, mencher cat. boo. cattydear. what a lovely!

"aspnet_regiis -c" will also install the client files.

This is needed anytime you change the virtual root.

Eric