Re: WebCat editing, SiteGuard & SiteEdit
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 10834
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 ? Sven,Maybe a better solution to quitting the CGI would be to send a [closedatabase] command to all the open databases. This will allow WebCat2 to close databases without actually quitting.You can create a special form that quits all the databases with a single click, then tell your users they have to use that form and click the button before they will see their recent changes ... :)Sincerely, Ken
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 ? Sven,Maybe a better solution to quitting the CGI would be to send a
[closedatabase] command to all the open databases. This will allow WebCat2 to close databases without actually quitting.You can create a special form that quits all the databases with a single click, then tell your users they have to use that form and click the button before they will see their recent changes ... :)Sincerely, Ken
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:
Webdna sends your serial number on Internet (2003)
Rendering out a page (1997)
WebCatalog NT beta 18 problem (1997)
Re:2nd WebCatalog2 Feature Request (1996)
emailer on Windows Beta 18 (1997)
PSC recommends what date format yr 2000??? (1997)
StoreBuilder Shopping Cart (2000)
RE: E-mailer error codes (1997)
Problems appending to database (1997)
Emailer help....! (1997)
QuitFeedback & DBNotOpened errors (1997)
Almost a there but..bye bye NetCloak (1997)
WebCat B13 Mac CGI -- Frames question (1997)
Signal Raised Error (Part III) (1997)
[WebDNA] [announce] CICADA Gold Products (2009)
Merging databases (1997)
Error with [applescript] (1999)
IP lookup tool via tcpconnect (2002)
[removehtml] (was: Undocumented tags and contexts) (2000)
Error: Can't open order file. Ignoring [OrderFile] context (2000)