Re: Multiple 'Users.db' files not possible
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 15831
interpreted = N
texte = >I've been following this thread and now I'm really confused. Like Brian, my >client wants to have their own database of users that will need to supply a >user name and password to be entitled to access certain pages on their site.There's no reason you can't create your own separate users database for each group of people on your site, but you'll have to use a different name than Users.db, and you'll have to create your own page protection system becayse using the [protect] tag works only with the Users.db.Look, I've done this before, I did it when I first started using WebCat more than a year ago and then I finally understood how to use the Users.db to do the same thing, and I dumped my work-around and went back to the Users.db and [protect] tag features already built into WebCat.All I'm trying to tell you is that you don't need a separate database, you can do it all with the Users.db if you want to, and once you understand how it works, you'll see that it's a better solution ... :)>The client needs to be able to add, modify and delete users in this database.Right, so now we're going to call that client a Sub-Administrator, because that's what he is. He's administering a subset of the users on your site, and he is only allowed to administer his own users and no one else's, right?So you create a special administratice template -- just for him -- with access to *only* the records in the Users.db that have HIS and ONLY HIS group's name in the GROUPS field (so technically, when the search context in this special sub-admin template performs a search, it only retrieves the records that have a GROUPS field that exactly matches his group's name. That way, he doesn't end up seeing your admin record or anyone else's records that have his group name in addition to other group names).And when you create a special APPEND form for this sub-admin to use, you have to make WebCat automatically add ONLY that group name in the GROUPS field of the new records it creates.And you don't *ever* display the GROUPS field for this Sub-Administrator to see, because he doesn't have to see what's in the GROUPS field, all he has to know is that when he creates a new record with his own special form, that record will have HIS GROUP NAME -- and no others -- automatically entered into the GROUPS field of those new records.>and I do not see a way to prevent them from seeing the contents of the entire >users.db file if I allow them this type of access.That's because you need to work with WebCat more before you will understand this. It takes time and experimentation, I know, I've been coding WebDNA 6-10 hours a day for more than a year, and I'm telling you that I can do exactly what you need to do, I've done it several times. You can do it too, after you understand how it works ... :)There's so much technical sophistication under the hood of WebCatalog that I'm still finding cool new ways to do things with it. It's a very powerful piece of software, so don't be disappointed that it's taking you more than a few minutes to understand this stuff -- no one can get it the first time around, believe me!>Additionally, their >database will need to have a lot more info than just name and group for each >of their users.Right, what's why you should add a bunch of extra fields to the Users.db. If you do what I've done, you'll probably end up with 20 or 30 extra fields in there, to store things like addresses, phone numbers, notes, etc.Hey, I've even got my Users.db setup to record the date the record was created, and who created it, and the date and time the most recent change was made to every record ... and it even records the USERNAME of the person making that change!Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://webdna.net/
Associated Messages, from the most recent to the oldest:
>I've been following this thread and now I'm really confused. Like Brian, my >client wants to have their own database of users that will need to supply a >user name and password to be entitled to access certain pages on their site.There's no reason you can't create your own separate users database for each group of people on your site, but you'll have to use a different name than Users.db, and you'll have to create your own page protection system becayse using the
[protect] tag works only with the Users.db.Look, I've done this before, I did it when I first started using WebCat more than a year ago and then I finally understood how to use the Users.db to do the same thing, and I dumped my work-around and went back to the Users.db and
[protect] tag features already built into WebCat.All I'm trying to tell you is that you don't need a separate database, you can do it all with the Users.db if you want to, and once you understand how it works, you'll see that it's a better solution ... :)>The client needs to be able to add, modify and delete users in this database.Right, so now we're going to call that client a Sub-Administrator, because that's what he is. He's administering a subset of the users on your site, and he is only allowed to administer his own users and no one else's, right?So you create a special administratice template -- just for him -- with access to *only* the records in the Users.db that have HIS and ONLY HIS group's name in the GROUPS field (so technically, when the search context in this special sub-admin template performs a search, it only retrieves the records that have a GROUPS field that exactly matches his group's name. That way, he doesn't end up seeing your admin record or anyone else's records that have his group name in addition to other group names).And when you create a special APPEND form for this sub-admin to use, you have to make WebCat automatically add ONLY that group name in the GROUPS field of the new records it creates.And you don't *ever* display the GROUPS field for this Sub-Administrator to see, because he doesn't have to see what's in the GROUPS field, all he has to know is that when he creates a new record with his own special form, that record will have HIS GROUP NAME -- and no others -- automatically entered into the GROUPS field of those new records.>and I do not see a way to prevent them from seeing the contents of the entire >users.db file if I allow them this type of access.That's because you need to work with WebCat more before you will understand this. It takes time and experimentation, I know, I've been coding WebDNA 6-10 hours a day for more than a year, and I'm telling you that I can do exactly what you need to do, I've done it several times. You can do it too, after you understand how it works ... :)There's so much technical sophistication under the hood of WebCatalog that I'm still finding cool new ways to do things with it. It's a very powerful piece of software, so don't be disappointed that it's taking you more than a few minutes to understand this stuff -- no one can get it the first time around, believe me!>Additionally, their >database will need to have a lot more info than just name and group for each >of their users.Right, what's why you should add a bunch of extra fields to the Users.db. If you do what I've done, you'll probably end up with 20 or 30 extra fields in there, to store things like addresses, phone numbers, notes, etc.Hey, I've even got my Users.db setup to record the date the record was created, and who created it, and the date and time the most recent change was made to every record ... and it even records the USERNAME of the person making that change!Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://webdna.net/
Kenneth Grome
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:
Adding order weight (1999)
[input] questions (1997)
[WebDNA] Pinterest kinda site? (2013)
Generating unique SKU from [cart] - FIXED! (1997)
random prob (2003)
random random links (1999)
emailer (1997)
[WebDNA] OT - JS help (2008)
Programmer Needed (1998)
WC1.6 to WC2 date formatting (1997)
How do I get WebCatalog to interpret WebDNA tags in .html files? (1997)
Authenticate (1999)
Fun with Dates - finally resolved but.... (1997)
Re[2]: Emailed problem (2000)
# fields limited? (1997)
[WebDNA] error: Permission deny when updating a database (2016)
How to get shownext to just shownext once (1997)
File Upload Problems (HELP!) (2000)
E-Mailer (WebCatb15acgiMac) (1997)
HELP WITH DATES (1997)