[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] MajorDomo Manual Config
- Subject: RE: [cobalt-users] MajorDomo Manual Config
- From: "Tim Lawson" <timl@xxxxxxxxxxxxxx>
- Date: Wed Aug 1 15:37:03 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> I was planning on
> altering the CGI for the file
> '/cgi-bin/.cobalt/mailListMod/mailListMod.cgi', which the admserv Modify
> Mailing List form posts to. I can't see the file to download via FTP (or
> anything in the .cobalt directory), but I can see it via Telnet. The CGI
> uses Cobalt libraries, one in particular -- Cobalt::List. If someone knows
> where all these libraries and the templates for the adminserv are located,
> that would be great. I can try it once I find all the files, I am just new
> with my Cobalt and don't know my way around much, but I do know CGI/Perl.
Robert,
I know little of CGI and less about where to find the Cobalt libraries...
In my searching the archives I have noticed others having similar problems
as I am having but no answer to the mystery.
I have some solutions of sorts, not sure if possible or how to impliment
it...
Assuming the list name is 'test'
Some possible solutions
1) Can I lock the file 'test.config' somehow so it can be read and not
overwritten by GUI?
2) Make the CGI backup 'test.config' to other dir then restore the file at
end of CGI (This would allow the GUI to add and remove members but not mod
the 'test.config' file. I understand all 'config' changes would be manual
from then onward)
OR THE BETTER SOLUTION (IMHO)
3) Edit the CGI (or whatever damn script) that takes the 'listname' value
from the HTML and dumps it in the 'restrict_post' section of the '.config'
file.
Can't we make it (the script) take the 'listname' value and add a (hard
coded) '.restrict' to the end of it just as it drops the value at the
'restrict_post' line. Then we are left only ever needing to make and edit
'test.restrict'. Anybody getting this far into the CGI could probably make
the 'test.restrict' file get created automatically, only needing a quick
edit in telnet.
Thoughts on this??? Can anybody tell us all how to do it???
Tim