Re: WebCat editing, SiteGuard & SiteEdit
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 10833
interpreted = N
texte = >Hi Grant, > >You said >>3) SiteGuard provides the exact same Group abilities that WebCatalog has. > >you are right, big surprise :-) > >My mistake, it was SiteEdit I meant doesn't seem to support groups. > >You also said >>1) It doesn't hurt to have remote people send $Quit commands to >>WebCatalog. It just reloads databases from disk the next time it needs them. > >Which we accept and fully agree with. > >What we specifically want to do is give the WebCat and/or SiteEdit >authorized users the ability to quit especially the WebCat.acgi, so that >they can test database changes/edits. However, we don't want to give them >full ADMIN privileges in either SiteEdit or WebCat ... for obvious >reasons. We don't care if the Quit ability is through WebCat or >SiteEdit, all we care about is minimizing the distribution of ADMIN >privileges. > >As far as I can tell, the only way to get access to the Quit command >for running applications is if you are in SiteEdit with ADMIN access. Am >I mistaken ? Look in the commands QUIT in the online docs, set up a page with this link on it,
Reset Data Bases or whatever . Use the password or protect scheme to guard that page.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
Associated Messages, from the most recent to the oldest:
>Hi Grant, > >You said >>3) SiteGuard provides the exact same Group abilities that WebCatalog has. > >you are right, big surprise :-) > >My mistake, it was SiteEdit I meant doesn't seem to support groups. > >You also said >>1) It doesn't hurt to have remote people send $Quit commands to >>WebCatalog. It just reloads databases from disk the next time it needs them. > >Which we accept and fully agree with. > >What we specifically want to do is give the WebCat and/or SiteEdit >authorized users the ability to quit especially the WebCat.acgi, so that >they can test database changes/edits. However, we don't want to give them >full ADMIN privileges in either SiteEdit or WebCat ... for obvious >reasons. We don't care if the Quit ability is through WebCat or >SiteEdit, all we care about is minimizing the distribution of ADMIN >privileges. > >As far as I can tell, the only way to get access to the Quit command >for running applications is if you are in SiteEdit with ADMIN access. Am >I mistaken ? Look in the commands QUIT in the online docs, set up a page with this link on it,
Reset Data Bases or whatever . Use the password or protect scheme to guard that page.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
grichter@panavise.com (Gary Richter)
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:
ConvertChars? (1998)
It finally happened ... (2003)
ImageMagick on OSX (2003)
taxTotal, grandTotal (1997)
WebCat2: Items xx to xx shown, etc. (1997)
taxTotal (1997)
[WebDNA] weekday question (2013)
Encryption method used for [encrypt]? (2000)
Security for malls with different webmasters (1998)
Apoligy (1997)
Include a big block of text (1997)
5.0 Pricing (2003)
Sample Tearoom Search Error (1997)
Frames and WebCat (1997)
[Sum] function? (1997)
MS Access (1999)
OT: zipcodes (2002)
question: back button prevention (1997)
Generating Report Totals (1997)
SMSI: databases corrupted on crash and permission issues on (2002)