<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.0">
</HEAD>
<BODY>
I've found modules for captchas, antispam, and calendaring. There's also one for obfuscating email addresses to confuse programs that are scraping websites. Might be useful.<BR>
<BR>
I think it would be a good idea to require members to register in order to post to forums. Registering could be complete at that point, require admin approval or reply to an email acknowledging a registration request. I prefer the email method.<BR>
<BR>
I'd rather not require moderators unless we have a problem with posts.<BR>
<BR>
On Wed, 2010-11-17 at 16:37 -0700, Crawford Rainwater wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Pardon the fork, but I figured it might be helpful.
Comments about Drupal and some answers to Dennis' questions below. Linux ETC uses Drupal with PostgreSQL (formally MySQL, but we are migrating off of that) back ends since the late v4.x days. Our current web site is a "simple" Drupal one for reference with quite a few things "hidden" to the general public.
</PRE>
</BLOCKQUOTE>
<PRE>
</PRE>
I happened to use PostgreSQL when I installed Drupal on my computer. Why did you drop MySQL?<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
----- <A HREF="mailto:dennisjperkins@comcast.net">dennisjperkins@comcast.net</A> wrote: -----
>
> We might have a second meeting too. Regarding our current setup, I
> know we have an email server and a web server and something written in
> PHP. Drupal is written in PHP and needs a database; either MySQL or
> PostgreSQL will do. If we migrate, what needs to be moved?
>
Basically a "cut and paste" job of "current" site to Drupal site I suspect. I would personally and professionally suggest PostgreSQL for the DB back end. A basic static site could be up (does not include the MailMan side) fairly quickly.
</PRE>
</BLOCKQUOTE>
<BR>
I've found that it is very easy to set up blogs and forums. I don't know yet how to organize blogs for easy access. <BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
> I want to see about having the forums and mailing lists work together.
> That might be the most difficult part.
>
Possible to do via Drupal. Greg, feel free to chime in here some for more specifics.
</PRE>
</BLOCKQUOTE>
<PRE>
</PRE>
I've found two modules that should work. It does require some email server tweaking to make it work.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
> I want a set of procedures drawn up for maintaining the site, so it is
> easier for anyone to take over.
>
As long as the database back end and the Drupal directories are kept up to par, migrating from server/system A to B is not hard (assuming same DB back ends and PHP versions here). "site content editor" (i.e., David A. and Jed currently) would go in and update respective pages as needed and publish from there. Back end patching and admin work for Drupal is fairly simple save I have to RTFM each time to remember the process for version upgrades.
--- Crawford
The Linux ETC Company
10121 Yates Court
Westminster, CO 80031 USA
voice: +1.303.604.2550
web: <A HREF="http://www.linux-etc.com">http://www.linux-etc.com</A>
_______________________________________________
clue-admin mailing list
<A HREF="mailto:clue-admin@cluedenver.org">clue-admin@cluedenver.org</A>
<A HREF="http://cluedenver.org/mailman/listinfo/clue-admin">http://cluedenver.org/mailman/listinfo/clue-admin</A>
</PRE>
</BLOCKQUOTE>
<BR>
<BR>
</BODY>
</HTML>