[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: Sun Aug 5 11:03:03 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> I think the hard code thing would be easier than what I'm
> thinking (for the
> admin, that is, but what about the user).
I agree, my original idea of the hard code would really benefit the admin at
this point (that is all I required, but for some it may not be good enough)
Wish I knew how to find the part I would edit to make it (the CGI) take the
listname value and add the .restrict part.
> I found all of the files, I believe that control not only the Majordomo
> configurations, but everything for that matter. The CGI that the
> online GUI
> forms post to when a user is modifying a MD list is calling Perl modules,
> for instance 'use Cobalt::List'. These modules are located at
> '/usr/lib/perl5/site_perl/5.005/Cobalt/', at least on my RaQ3.
> Everything is
> CGI/Perl, so I will be attempting to add a field onto the GUI
> form to allow
> entering a 'restrict_post' value. And then modify the CGI/Module to accept
> the information and right the appropriate value in the config file when it
> is modified. If it works, then I'll add something to allow them
> to edit the
> file. Can you specify an absolute or relative path in the 'restrict_post'
> variable in the MD config file? I've never tried, but if it works to put
> '/home/sites/home/site#/majordomo/list.restrict' as the value,
> that would be
> great. Has anyone tried that before in a Majordomo list? Maybe I'll pass
> that one along to the Majordomo users list.
Food for thought... If you create a file name in the lists directory without
an extension (.anything) it shows up in the GUI as a sperate list.
Using this principal, how good would it be to have the CGI make not only
'list1' but also make 'list1_admin' in the GUI so you could make the
'list1.config' have the line 'restrict_post = list1_admin'.
This allows the GUI user to add or remove people from list1_admin who are
allowed to submit content emails to list1.
Thoughts??? please remember I am not technically advanced like you guys...