Drupal 6.x

This branch needs a going over for deprecatable/archivable content. Feel free to update/deprecate as needed.

Instructions on multi-site configuration (also known as "multisite" and "single code base" installations) can be found within the installation instructions.

To allow users to post to and receive email from Drupal forums.

As of version 1.9, CiviCRM includes a CiviCRM_OG_sync module. Once installed upon creation of an organic group it will create a corresponding CiviCRM Group. This is a one-way sync, from OG to CiviCRM.

Prior to CiviCRM 1.9, integration required a separate contributed module.

Note: this is only applicable to Mailhandler versions 6.x-1.x and 7.x-1.x (colloquially "Mailhandler 1.x"). For a tutorial on setting up a more complex post-by-email system and mailing list (which could integrate with a forum or case tracker), using Mailhandler 2.x, see the article Setting up an email-driven workflow with attachments

How to submit Blog post by Email Note, my experiences are for simple email processing. I haven't done anything like tying an email list to a forum.

Step 1: Turn on the mailhandler module

Admin -> Modules
Click on the module

Step 2: Set up an email account to which you will send email

This depends on what you are using for a mail hosting service. I use cpanel, click on Mail , click on Manage/Add/Remove accounts.. Click on Add accounts and set up the email address and the password. For my system, the email can be retrieved as POP3. Again, this depends on the mail hosting service you are using.

Step 3: Configure the mailhandler

Admin -> Mailhandler
Click on Add Mailbox, fill in the appropriate fields.

Email address

How command processing works - technical overview

A command consists of two main parts - a key and a value. In the command type: blog "type" is the key and "blog" is the value. There is explicit handling for commands related to taxonomy. Apart from taxonomy, there is general handling for properties on the node object. For example, commands are searched for and collected on an incoming message. If the command is specific to taxonomy, it will be processed according to the parameters explained in the "Taxonomy commands" section below. If the command is not related to taxonomy, the property on the $node object with the name "key" will get set with its corresponding value. For example $node->type = 'blog' would get executed if the command type: blog is found. Therefore, if you're using another module which owns a property on the node object, you can see how you could assign a value to that property by specifying the name of the property and a value in your mailhandler commands.

List of known mailhandler commands

Node settings commands

comment: 2
(0 if no comments, 1 if read-only comments)

format: 1

These are some simple guidelines for setting up Drupal on a classic Linux-Apache-MySQL-PHP (LAMP) stack that provides a fair amount of security for the rest of your system.

PHP Configuration

To start, some common PHP configuration options can be optimized. On some systems, these settings may already be set, but it never hurts to add them yourself just in case.

PHP settings can be controlled in a number of ways. If you have access to the php.ini configuration file (usually found at /etc/php.ini), you can simply edit this file to cause system-wide changes. If you'd prefer to make these changes just for your Drupal installation, however, the best place to do so is in your Drupal installation's settings.php file.

1. First, increase PHP's memory limit to avoid getting out-of-memory errors when you begin to add a few modules. These errors may look something like this:
   

   Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 30720 bytes) in /path/to/drupal/modules/system/system.module on line 1022

2. In your php.ini file, include a line that reads: memory_limit = 16M. Or…