You could add a username field, but it won’t do anything in
conjunction with this Action. All this Action does is redirect the
user to a folder or page named for whatever is entered in the password
field. If you want to do anything with the user name later, you’ll
need to store it somewhere. The simplest thing would be to stash it in
a cookie; then you can write it out on the top of the page somewhere:
“Welcome back, username!” or check to see if the visitor did actually
log in and isn’t accessing the page from a bookmark.
What’s your requirement here, besides the client asking for it?
Well, I guess I was asking for a little more information, then. He wants it, he wants you to request it from the user, but then what? Do you need to store it and use it again later? Depending on your requirements (or his, anyway) there’s a lot of different things you could do, with varying levels of complexity. I could just tell you to implement a database and PHP login system, with all sorts of bells and whistles, and that would certainly work. But it might be massive overkill for your purposes.
Hi Username, if you want SIMPLE… it is the “server end”. Put the pages you want to protect in a folder, have a link from that page 2 any page in your new FW folder and before you can get in… it asks for a Username & Password before the page is accessed (Client Happy). Have as many passwords & usernames as your heart desires. Right now with this action your password is shown in your HTML. Call your server or the server of this website, they will point you in the right direction, is it a problem doing this?