This module allows users to post responses to other posts. Through administer you can configure what types of comments are accepted: anonymous, anonymous requiring an email address, or registered users only. You can also configure permissions for types of users (authenticated, administrative, or anonymous) so that comments written by the respective types of users enter an approval queue before they are published or are automatically published. Comments in the approval queue must be manually accepted and published by a site administrator. Comments are also searchable. Comments can be viewed seperate from their posts for easy editing and deleting.

Allows for the creation of web forms which can be filled out by users and submitted to the survey's creator. Submissions are emailed to a chosen email address and are also stored in the database. Survey creators can also create/specify a custom “Thank You” page for respondents.

Survey questions can be entered as textfields, passwords, text areas, radio buttons, pull down menus (selection), check boxes, or file (to upload files for the surveyor). Surveyors can specify whether or not multiple selections are allowed.

Surveyors can also require that respondents validate themselves by the use of email address, data input, URL input, or zip code. The responses to a survey can be viewed online, as well as downloaded in an Excel-compatible format. Users are able to set up books for created surveys through this same interface.

This module allows you to solicit volunteers for events. Users can set the number of volunteers necessary for the event as well as the messages that will be sent to volunteers to thank them for volunteering, letting them know that the number of necessary volunteers has been reached and their assistance is appreciated but not necessary, or that they have been placed on the volunteer waiting list. This module also sends out reminders 24 hours before the event and solicits feedback 24 hours after the event.

This functionality can only be used after the c

This module allows users to send invitations for events to other users via email so that they can RSVP . RSVP creators can also choose whether or not to make the invitation list viewable by all, allow invitees to email one another, or allow attendees to invite others through this interface.

This functionality can only be used after the creation of an event and must be connected to a specific event.

Manange RSVP allows users to edit the invitee list and notification options that were determined during the creation of the ori

The Event module includes a field for an event's location and drop-down menus for the date and time of an event. It also adds a calendar navigation block to the sidebar so that readers can click on a date and list which events are scheduled for that date, as well as a page listing upcoming events, sorted chronologically. Users are able to set up RSVP , volunteer signups , and books for created events through this same interface. An »

• Login or register to post comments
• Read more

Much like a phone book, the contact module allows the creator to sort contacts into different contact lists (which can be exported into a spreadsheet) and to maintain information for each contact for use in other modules (such as RSVP ). This information includes email address, name, zip code, city, state, and telephone number by default. Additional information can be added through administer contact . This information can be entered as text fields, passwords, text areas, radio buttons, pull down menus (selection), check boxes, or file (to upload files for the surveyor).

Some CivicSpace modules, such as search, notify and aggregator, have periodic tasks that must be triggered by the script cron.php included with your CivicSpace installation. You can do this manually in your browser by visiting your cron URL page (a blank page will display once the cron tasks have been executed).

However, the better way to do this is to have cron.php executed automatically using the Linux/UNIX crontab function.

• The following example crontab line will activate the cron script
  on the hour:

  0 * * * * wget -O - -q http://www.example.com/cron.php

• If your host has the text browser lynx on the system, make use of the file provided in your Drupal installation in scripts/. Edit scripts/cron-lynx.sh, subsituting the name of your site. Then setup a crontab every hour:
  

  00 * * * * /home/www/drupal/scripts/cron-lynx.sh

Alternatively, Drupal has a poormanscron module available for download. However, this module is much less efficient in terms of system resources compared to the methods described above. The poormanscron module checks to see if cron needs to run every single time a page is viewed on the site.

More information about cron is available in the adminstration help page and at the Drupal Handbook Cron system and crontab page.