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:
Protect groups and delete command (2000)
WebMerchant 1.6 and https (1997)
Nested tags count question (1997)
Emailer (1997)
WebMerchant? (1998)
WebCat2.0 [format thousands .0f] no go (1997)
A better way to do this?? (2005)
Server slowing down. (1997)
FORMS: Returning a specific page (1997)
Reversed words (1997)
Sorting LISTFILES (1997)
RAM variables (1997)
Searching multiple records for certain info (2000)
[WebDNA] Deliminating encrypted values (2008)
Add - optional parameters textA=.... (1997)
Authenticating users without dialog box (1997)
[OT] Robust order processing (2003)
creator code (1997)
Help! WebCat2 bug (1997)
WebDNA 4.5.1 Now Available (2003)