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 WebCat2to close databases without actually quitting.You can create a special form that quits all the databases with a singleclick, then tell your users they have to use that form and click the buttonbefore 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 WebCat2to close databases without actually quitting.You can create a special form that quits all the databases with a singleclick, then tell your users they have to use that form and click the buttonbefore 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:
Re:Emailer and encryption (1997)
WebCat2 - Getting to the browser's username/password data (1997)
Problems reading files created by WC (1997)
[showif]/[hideif] question (1997)
webcat2b12 CGI -- Date comparisons (1997)
refreshing IE with posted .tmpl (1997)
BUG?- .html extention and not working. (2000)
[WebDNA] Any way within WebDNA to tell if a file can be modified by current user? (2010)
Emailer Error: 158 (2003)
Document Contains No Data! (1997)
[WebDNA] Lookup vs. Search (was: 3-5 GB of native WebDNA db...) (2009)
ShowNext truncating passed variable?? (1997)
re:check boxes (1997)
Date to days (2002)
WebCat2b13MacPlugIn - More limits on [include] (1997)
Fun with dates (1997)
restarting service remotely on NT (1997)
OT: IP addres checking (2003)
Database changes (1998)
PIXO (1997)