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:
Starting WebCat under linux (2000)
[OT] Linux -> Winderz (2005)
Help name our technology! (1997)
Emailer setup (1997)
HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997)
Multiple security dbs (1997)
hard carriage returns and sendmail (1998)
(1997)
WebCatalog Upgrade Pricing? (1997)
Re[3]: 2nd WebCatalog2 Feature Request (1996)
WebCat for Unix?? (1997)
Triggers Suck! (2000)
PCS Customer submissions ? (1997)
All questions are welcome on this list (1997)
randomness (1997)
WebCat2b12plugin - [search] is broken ... not! (1997)
Help name our technology! I found it (1997)
Errata: WCS Newbie question (1997)
searching with groups (1997)
frames & carts (1997)