Re: Who is doing sign-ups-got it
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 17124
interpreted = N
texte = I am in a similar situation, and really like your ideas. Putting the access.db separate for each website is vital for some of the stuff I do, as I have customers who want to send a updated file of cleared users daily to their website (and as I am doing competitors websites, I need to have some good-happy feelings that never will the two sites data mix...) Brian B. Burton BOFH --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.com ---------- >From: Kenneth Grome
>To: WebDNA-Talk@smithmicro.com >Subject: Re: Who is doing sign-ups-got it >Date: Fri, Apr 17, 1998, 6:50 PM >>>I think I found Ken's examples in the archive about modifying the >>multigroup checker and changing out the user.db. So I will go with Kens >>example over the weekend and see what happens. >> >>Let me try this unless someone has tried this and it does not work > > >Hi Gary, > >I'm not sure what you've found in the archives, so here's a review: > >I've adopted the practice of using a different database -- instead of the users.db -- for the sites I create for others. This makes it easy for me to create a drag-and-drop installation for my clients. Each site is instantly portable when *ALL* the templates and db's for the entire site are contained within a single folder. > >Here's what I do: > >1- create a new folder for my client's web site >2- create a duplicate of the users.db and rename it access.db >3- create a duplicate of the multigroupchecker file and rename it protect >4- in the protect file, change all occurrences of users.db to access.db >5- place these and all other templates and db's into my client's web site folder >6- use tags like the following for protecting pages inside my client's web site: > >[include file=protect&groups=group1,group2,group3] > >By the way, you can add as many additional fields to the access.db as you need. So if you're registering users and giving them protected access to certain pages, the access.db is the natural place for their registration data to be maintained ... :) > >Sincerely, >Ken Grome >808-737-6499 >WebDNA Solutions >mailto:ken@webdna.net >http://www.webdna.net > > >
Associated Messages, from the most recent to the oldest:
I am in a similar situation, and really like your ideas. Putting the access.db separate for each website is vital for some of the stuff I do, as I have customers who want to send a updated file of cleared users daily to their website (and as I am doing competitors websites, I need to have some good-happy feelings that never will the two sites data mix...) Brian B. Burton BOFH --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.com ---------- >From: Kenneth Grome >To: WebDNA-Talk@smithmicro.com >Subject: Re: Who is doing sign-ups-got it >Date: Fri, Apr 17, 1998, 6:50 PM >>>I think I found Ken's examples in the archive about modifying the >>multigroup checker and changing out the user.db. So I will go with Kens >>example over the weekend and see what happens. >> >>Let me try this unless someone has tried this and it does not work > > >Hi Gary, > >I'm not sure what you've found in the archives, so here's a review: > >I've adopted the practice of using a different database -- instead of the users.db -- for the sites I create for others. This makes it easy for me to create a drag-and-drop installation for my clients. Each site is instantly portable when *ALL* the templates and db's for the entire site are contained within a single folder. > >Here's what I do: > >1- create a new folder for my client's web site >2- create a duplicate of the users.db and rename it access.db >3- create a duplicate of the multigroupchecker file and rename it protect >4- in the protect file, change all occurrences of users.db to access.db >5- place these and all other templates and db's into my client's web site folder >6- use tags like the following for protecting pages inside my client's web site: > >[include file=protect&groups=group1,group2,group3] > >By the way, you can add as many additional fields to the access.db as you need. So if you're registering users and giving them protected access to certain pages, the access.db is the natural place for their registration data to be maintained ... :) > >Sincerely, >Ken Grome >808-737-6499 >WebDNA Solutions >mailto:ken@webdna.net >http://www.webdna.net > > >
Brian B. Burton
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:
Help name our technology! (1997)
About (2001)
2.0 Info (1997)
[WebDNA] setting up a dev server on Windows 7 or 8? (2014)
Multiple prices (1997)
WebTen Type 2 Crash on start (2000)
Foreign Chars ( יאצה and so on) (1998)
WC 2.0 frames feature (1997)
Q: old cart serial problem (2000)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
StoreBuilder help/question... (2000)
rotating thumbnails (1997)
Error: this shopping cart has already been submitted (2003)
WebDNA Developer Resource Center (2002)
Problems with [Applescript] (1997)
RE: New WebCatalog Version !!! (1997)
Problem with empty form-variables in [search] (1998)
can you reassign loop index? (1998)
acrobat -> wc (1998)