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:
[OT] JavaScript Error (2002)
Preventing Merchant Settling ? (1997)
How much is too much? I can never remember the answer. (2002)
New Site Announcement (1998)
windows 95 netscape 3.01 browser bug? (1997)
2.0Beta Command Ref (can't find this instruction) (1997)
Storefront Case Studies (1998)
Date format problems (1997)
HTML Editors (1997)
Problems with [Applescript] (1997)
[WebDNA] [BULK] 7.x and 6.x on same server (2012)
expired beta (1997)
WC2b15 File Corruption (1997)
FORMS: Returning a specific page (1997)
more on my bbs (1997)
Exclamation point (1997)
Max Record length restated as maybe bug (1997)
Hard Questions ? (1997)
converting tabs (1997)
XML Parse with XML WebDNA Syntax... (2004)