Re: Customer login feature
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 57651
interpreted = N
texte = You could use the same kind of logic that the multigroupchecker uses, but instead of doing an [authenticate] - you could redirect the user to the login page. Now for tracking the user through their session, you could use a cookie.For this I usually set a session_id and save their user_id in a text file. I use the session_id (from the cookie) to connect the user with their user_id stored in the file. All this you put in a file which gets included on every page.Running out the door - sorry if a bit vague. Let me know if you need further assistance, I have sample code I could provide a little later.- CharlesOn May 5, 2004, at 11:22 AM, Mark Derrick wrote:> Hi,>> just looking to get a feel for how people are implementing "Customer > Login" features.> I'm talking about the pretty typical kind of thing you see at Amazon, > etc - allowing you to log in once and the site then remembering you > until you leave.>> I've looked at using [Authenticate]/[Protect] etc, but would like to > find a neater solution which doesn't use the authenticate pop-up > window.> I'd prefer to just use a login section coded into the front page, > which allows people to log in if they wish to (to obtain access to > extra features).>> Any suggestions/examples of how people are using WebDNA to do this?>> Thanks.>> Mark.>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list
.> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/>-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
You could use the same kind of logic that the multigroupchecker uses, but instead of doing an [authenticate] - you could redirect the user to the login page. Now for tracking the user through their session, you could use a cookie.For this I usually set a session_id and save their user_id in a text file. I use the session_id (from the cookie) to connect the user with their user_id stored in the file. All this you put in a file which gets included on every page.Running out the door - sorry if a bit vague. Let me know if you need further assistance, I have sample code I could provide a little later.- CharlesOn May 5, 2004, at 11:22 AM, Mark Derrick wrote:> Hi,>> just looking to get a feel for how people are implementing "Customer > Login" features.> I'm talking about the pretty typical kind of thing you see at Amazon, > etc - allowing you to log in once and the site then remembering you > until you leave.>> I've looked at using [authenticate]/[protect] etc, but would like to > find a neater solution which doesn't use the authenticate pop-up > window.> I'd prefer to just use a login section coded into the front page, > which allows people to log in if they wish to (to obtain access to > extra features).>> Any suggestions/examples of how people are using WebDNA to do this?>> Thanks.>> Mark.>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/>-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
charles kline
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
search form problem.. (1997)
WebCat Versions (2003)
Bug Report, maybe (1997)
all records returned. (1997)
OT - SE robot question (2003)
Monitoring Script (2008)
[OT] gMail accounts (2004)
[LOOKUP] (1997)
Automatically submitting form with web cat. (2001)
Problem (1997)
WebCatalog can't find database (1997)
Okay, I give up... (1999)
Can a database get stomped by simultaneous access? (1997)
Only charge card when product shipped ? (1997)
[WebDNA] making all fields on a form mandatory (2013)
Duplicate Cart ID (2001)
PSC recommends what date format yr 2000??? (1997)
Forms Search Questions (1997)
Using Eudora instead of Emailer, and cron facility (1998)
[WebDNA] SMTP via gmail is NOT POSSIBLE (2013)