Re: $Append for Users outside the ADMIN group
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 13920
interpreted = N
texte = >How can I allow my customers to maintain their databases and use the>append command without giving them ADMIN access?>>I don't want to delete the append command from the list of allowed>command.Please think about using this technique:Delete the append command from the list of allowed command, then use[append] contexts in your forms instead.Any [append] forms you don't want the public to use can easily beprotected with the [protect 'groups'] tag. Several groups can beallowed access to your [append] page (not just the 'admin' group)while denying all others, like this:[protect admin,vendors,clients]This tag will allow only members of the 'admin' group OR the'vendors' group OR the 'clients' group to access the page. Make sureto put this tag at the top of the pages you want to protect, a goodplace for it is immediately after the tag.Use the same technique for all your other commands, too. Then removeall those commands from the CommandsAllowed Preference so you don'thave to worry about other people sending direct commands from theirbrowser ... and potentially messing up your databases.Sincerely, Ken GromeWebDNA Solutions808-737-6499http://www.hui.net/dna/webdna.html
Associated Messages, from the most recent to the oldest:
>How can I allow my customers to maintain their databases and use the>append command without giving them ADMIN access?>>I don't want to delete the append command from the list of allowed>command.Please think about using this technique:Delete the append command from the list of allowed command, then use
[append] contexts in your forms instead.Any
[append] forms you don't want the public to use can easily beprotected with the [protect 'groups'] tag. Several groups can beallowed access to your
[append] page (not just the 'admin' group)while denying all others, like this:[protect admin,vendors,clients]This tag will allow only members of the 'admin' group OR the'vendors' group OR the 'clients' group to access the page. Make sureto put this tag at the top of the pages you want to protect, a goodplace for it is immediately after the tag.Use the same technique for all your other commands, too. Then removeall those commands from the CommandsAllowed Preference so you don'thave to worry about other people sending direct commands from theirbrowser ... and potentially messing up your databases.Sincerely, Ken GromeWebDNA Solutions808-737-6499http://www.hui.net/dna/webdna.html
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:
protect tag on NT IIS (1997)
docs for WebCatalog2 (1997)
Re:trouble (1997)
upgrading (1997)
Bulk Processing Offline (2004)
Alcatraz must have been nicer than this... (2000)
PIXO Support (1997)
WebCatalog/Mac 2.1b2 New Features (1997)
WCS Newbie question (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
[WebDNA] math and blank /no value (2014)
WC2.0 Memory Requirements (1997)
OR-searching (2000)
NT Version on IIS 4.0 (1997)
Bug Report, maybe (1997)
[ConvertChars] problem (1997)
Include a big block of text (1997)
[WebDNA] How does waitforfile actually work? (2009)
writefile and texte (1997)
Cart creation techniques (was Problems with Price field) (1997)