Download & Extend

Calendar

Requires Views and the Date API (packaged with the Date module).

This module will display any Views date field in calendar formats, including CCK date fields, node created or updated dates, etc. Switch between year, month, and day views. Back and next navigation is provided for all views. Lots of the Calendar functionality comes from the Date module, so any time you update the Calendar module you should be sure you also update to the latest version of the Date module at the same time.

See also Date iCal, a project that contains code and features needed to either import or export dates using iCal feeds. The functionality that used to be in the Calendar iCal module has been moved into that module.

Be sure to read Debugging Information before reporting a problem. Going through those steps may resolve your problems and will help provide enough information to tell if this is a bug.

Event

This is a simple module to keep track of events and show them to users in various calendar displays. It also provides an event API to allow other modules to store and work with date data.

FullCalendar

Provides a Views display, style and row plugin for displaying nodes using Adam Shaw's FullCalendar jQuery plugin.

Information

There is a good deal of info in the issue queue, but if you're on IRC, come by the #drupal-fullcalendar channel and say hello!

Updating

As of 7.x-2.0-beta1, the Colorbox integration is part of the FullCalendar Options submodule.

Please remember to run update.php first, or clear all caches.

The FullCalendar Colors submodule requires the Colors API module. There is an upgrade path, be sure to run update.php and clear your caches.
Specifically, if you are using FullCalendar beta2, you must use Colors beta2.

The template files (*.tpl.php) have been removed, if you still wish to use those, please install FullCalendar Templates.

Installation

See the documentation for installation instructions.

Usage

See the documentation for usage information.

Credit

Maintainer and developer: tim.plunkett

Agenda

The Agenda module allows you to display a list of upcoming events from Google Calendar as a block on your website.

The events are automatically downloaded and cached from the Calendar IDs specified in the Agenda administration page. Unlimited calendars can be added, and the colours for each calendar can be specified in the CSS file.

The output is fully themeable, and uses jQuery for dynamic effects such as rounded corners, and click-toggling extra information.

Note: If your dates are displaying a day off, you might be suffering the effects of Daylight Savings Time. Try installing and enabling the Date API and Date Timezone modules, then Daylight Saving Times are handled correctly.

Entity Registration

Entity Registration is a simple, flexible module for allowing and tracking user registrations for events, or just about anything you want people to sign up for. Entity Registration can be integrated with Drupal Commerce to allow fee-based registrations: sell tickets to your stuff! This module is also handy if you want to collect information along with registrations: like shoe-size for a bowling event.

jQuery Countdown

Provides the jQuery Countdown plugin by Keith Wood, along with a simple API function (jquery_countdown_add) to easily add countdown/countup timer elements to the page.

Availability Calendars

The Availability Calendar module allows you to add an availability calendar to entities. Example use cases are tourist accommodation, e.g. bed and breakfast, holiday homes or self catered apartments, and car or motor bike rental.

An availability calendar shows your customers at what dates your accommodation is still available and at what dates it is already booked.

Event Views

Requires both the Event module and the Views module. The Event Views module exposes event fields to the Views module, creates year, month, day, and week argument handlers, and provides default event views that filter events using a drop-down date selector, the jscalendar selector, if installed, or by arguments in the url. Argument combinations can include year, year/month, year/month/day, and year/week. You can also combine the event arguments with content type and taxonomy arguments for more granularity.

Note that until recently this module was included with the event module's tarball.

The Drupal 6 version of this module has now been released and works with Views API 2. Currently is supports Views Filters, Views Sorting, Views Arguments, and Views Fields. It also supports Views Relationships for NID.

Events calendar feature

Here is an example of how to build a list of events with a calendar block that filters the listed events for a particular day in Drupal 7.

What does this feature do?

• Checks that you have the required modules. Note: modules calendar, ctools, views and date should be in their latest development versions. Read this related issue for more details
• Creates a content type Event with a date field (start and end date).
• Creates a view /events that lists current events and accepts a date parameter in the URL in order to see events for a particular date.
• Loads a clone of the Calendar view called Events calendar with the block display customized to highlight days where there are events.
• Adds a bit of custom code so a day in the calendar block with events links to the events view appending the date (ie. /events/2011-08-18).

Step by step guide

In order to manually recreate what this feature does, follow the Step Guide.

Views Date range

This module provides a new Views argument plugin for date fields that allows for arbitrary date ranges in summary views. If you need to generate a listing of nodes by quarter, academic term, or some other site-specific date range then this is the module for you.

Note: This module has only been tested on MySQL 5.x and I'm fairly sure it will not work on PostgreSQL. Unfortunately it requires doing seriously bizarre things in SQL that are not at all portable.

Once this module is enabled, you will find a new Views Argument handler under the "Date" group called "Date: Date range". It works in the same way as the normal "Date: Date" argument, except that instead of setting a granularity for the summary view you may configure your own arbitrary set of date ranges at the bottom of the configuration form.

These date ranges should be in the order you wish them displayed, and together should cover the entire year. They may be given any label you wish.

When the view is displayed, if no date is given then a summary view will be generated that uses the specified date ranges rather than more common ranges like a summary by month or by year. Each date range will be within a given calendar year, so will be along the lines of "Quarter 3 2008", "Quarter 1 2009", etc.

Signup Integration for Ubercart

UC_Signup provides integration between Signup.module and Ubercart, allowing users to purchase signups for events.

Signup-enabled nodes are configured as Ubercart products.

The customer can purchase signups for herself and/or other people.

Example use cases:

• 1 User signs up for 1 or more events
• 1 User signs up 2 people for the same event
• 1 User signs up 4 people for 3 different events, providing profile information for the two users who do not already have accounts on the site.

If the people do not have accounts on the site the customer is prompted to create a new account for that person, entering any core user profile fields that are enabled on the site. If there are matching user accounts for the email addresses entered, then UC_Signup does not ask for their profile information.

When the order is submitted, temporary signups are created to ensure that the customer is only charged if space is available in the event(s). Once checkout is complete, if the order balance is not cleared, the signups are cancelled. If the balance is cleared, the signups are converted from temporary to final signups. UC_Signup stores this distinction in the uc_signup_log database table.

Signup Status

The Signup Status module extends the Signup module's functionality by allowing users with permission to administer signups on signup-enabled nodes to set the status of a user's signup. This can be used, for example, to mark users as "Paid" or "Completed." By default, the module comes with two default statuses, "Approved" (the default status) and "Wait listed."

This module features:

• Limit number of signups per status.
• Wait list functionality for the signup module with optional auto-transition to "Registered" status.
• Printable rosters as HTML, PDF or CSV.
• Modifications to the Signup Broadcast form that allows signup creators to email a group of signups based on signup status.
• Views module support through several fields and filters.

Several optional modules are included in this package, which include:

• Signup Status Log: An administrative log of signup status changes.
• Signup Status Certificates: Grant certificates to users based on their status. See "Configuring Certificate Templates" below.
• Signup Status Mailer: Email users when their signup status has changed.

Commons Events

Events features for Drupal Commons.

See the main Drupal Commons issue queue for related Commons Events issues.

RSVP

RSVP lets users invite people to attend an event. Users create an 'RSVP' from an event, send an invitation email to a list of people and then track who has looked at the invitation and their responses. Invitees can view and reply without having user accounts.

RSVP creators can be setup the RSVP to hide other attendees, allow attendees to send email messages to the group, or invite more attendees.

Who Bought What|Ubercart

VERSION 7 now available.

This is for Ubercart. If you are using Ubercart to sell tickets or entries to an event or perhaps a race, it's very helpful to have a list, per item, of who bought what. For a competition, this will become an entry list. For a performance, this may become your will-call attendance list.

You may simply want to know who bought what! Who are the purchasers of a given item can be useful in any of a number of instances... recalls, promotions, and the like.

This module collects and displays relevant information about purchases, including purchaser name, quantity, payment status, and all attributes.

Finally, the result may be downloaded as a csv so you can do whatever you want with it.

Enterprise Events

Enterprise Events is an App for managing events on your site. It is a part of the Open Enterprise distribution but can be installed on any Drupal 7 site.

Features

• event content type with date field
• view listing page and block of events that can be filtered by categories
• categories block view
• enhanced admin view for better content administration

Installation

1. Install the module and dependencies. There are three ways to install using Drupal 7:
   • Do a traditional install by downloading all the modules from Drupal.org and follow instructions
   • One click install via the LevelTen Apps Server. You must install the apps connector modules first.^*
   • Start your site with the Open Enterprise Drupal distribution. The apps server connectors are included - along with a lot of other great stuff.^*

   ^* Using the apps server greatly streamlines the process.

2. Once installed, a Events item will appear on the main menu. Visit the page and click "+ Add event" to get started.

Issues

Maestro

The Maestro module is a workflow engine/solution that will facilitate simple and complex business process automation.

Maestro has a number of components that include the workflow engine and the visual workflow editor. The workflow editor is used to define the workflow, creating a workflow template. The workflow engine runs in the backgound and executes the workflow tasks, testing the tasks execution results and branch the workflow if required. The workflow engine will run every x seconds and execute all tasks that are in the queue which have not yet completed. Once they execute and return a success status, the engine will archive them and step the workflow forward. Both these components have been developed to support any number of different task types. New task types can be developed and added much like the Drupal CCK module can support new field types. Initially we will have the following task types:

• Content Type Task: Assign a task to a user to create a new content node - task definition allows you to select from available content types.

User Alert

This module provides a simple way to show a short-term urgent message on the website. Think of CNN Breaking News, when they show a short message the top of the site (or the 'Welcome!' style messages at StackExchange websites). This module works for both anonymous and authenticated users by using a cookie, and recording actions in the database. This solves the need to show messages independent of the users authenticated status.

With User Alerts, you can:

• Alert users about breaking news, or a special same-day sale for ecommerce
• Schedule publishing of alerts via Scheduler
• Override display with TPL and CSS

How to use this module:

1. Enable User Alerts
2. Set the appropriate permissions for selected roles
3. Set the User Alert block in the appropriate region of your theme.
4. Create a user alert node.

You can also set some global settings for alerts at admin/settings/user-alert.

Unpublished alert nodes are removed from the system automatically. This is to prevent an old alert being seen by a user (if the cookie was cleared or expired, for example) if a node was republished accidentally.

Node Repeat

We need to have one good module. Not a lot of half good.
#894680: Merge similar "node repeat" module

This module allows creating multiple repeats/duplicates/clones of nodes based on date sequences. The date sequences are created with the Date Repeat module (part of Date). The nodes must have a CCK Date field, which in the new nodes created by Node Repeat are populated with dates from the sequence. A typical use case might be for creating an event that repeats regularly and for which your users need to Signup.

Node types that have one or more Date field(s) can be set to allow repetition by selecting the Date field to use. If a node type is set to allow repetition then a Repeat tab will appear on nodes of that type to allow creating/editing repeats for that node. Under the Repeat tab if the node is already part a sequence then options for editing that sequence are displayed, otherwise options for creating a sequence from the node are displayed.

Documentation

Usage and Features for 6.x-1.1

For unstable versions please take a look at the release notes.

Known issues

#927452: DST problems

Roadmap

#894680: Merge similar "node repeat" module

MERCI (Manage Equipment Reservations, Checkout and Inventory)

MERCI can extend any content type into a list of unique reservable items (like studios) or buckets of interchangeable items (like DV cameras). We followed the approach used by Organic Groups, Feed API, and Scheduler and added MERCI's configuration to the Edit tab of those content types.

GETTING STARTED WITH MERCI:

• Documentation on drupal.org
• Setting Up MERCI
• Importing Equipment with Custom Fields
• Configuring CiviCRM to work with MERCI
• Reporting with MERCI
• Managing MERCI with Views
• Taking Inventory with Barcodes

DRUPAL 7 MODULE STATUS

MERCI is relatively stable for Drupal 7. If not, please post an issue. If upgrading from Drupal 6 you will need to roll back field_merci_date and remigrate it. More info on migrating the fields is here: http://drupal.org/node/1144136

CiviCRM Events Calendar

The CiviCRM Events Module pulls and display the CiviCRM events in a calendar using the Jquery Plugin fullcalendar .

Requirements
Jquery Plugin fullcalendar .

The current version for D6 and D7 is tested with 1.4.2 version of fullcalendar.

Configurations Available :
Currently the calendar settings available are :
1. Show/Hide End date.
2. Show/Hide Past Events.
3. Restrict events upto particular months.
4. Filter events of Specific Types.

Installation:

Download the Jquery Plugin fullcalendar . and copy the file 'fullcalendar.js' in js folder and copy fullcalendar.css in css folder. You are done, you can see the Events Calendar at /events/calendar.

Commerce Registration

Overview

Provides Drupal Commerce with the ability to sell registrations via the Entity Registrations module.

Dependencies

Entity Registrations (at least 7.x-1.1)
Drupal Commerce

Disclaimer

This module, along with Entity Registrations, is still in beta. That means there can be substantial code changes, although the schema is relatively stable. However, this does not completely remove the possibility of any major changes that will affect interaction between the two modules. Check the issue queue for any possibly existing problems.

Set Up

Use Drupal Commerce as usual.

If you don't already have a product display set up, create one with a product reference field.

Add a Registration field to the commerce product type you want.

Create a product and set the Registration type (or create one if you haven't already), add a new product display with that reference, and add the settings to the DB as above.

Add to Cal

A field formatter providing a widget for exporting events to:

• Google Calendar
• Yahoo! Calendar
• iCal
• Outlook

The field formatter provides a button next to the field that shows a drop-down menu. This menu contains links to the supported formats, and includes basic styling that can be easily modified through CSS.

For screenshots and a more detailed explanation of how this module works, check out this blog post.

After installation, we recommend clearing your cache, or you may see a strange behavior where the .ics file downloads try to load as nodes rather than triggering a download. (/admin/config/development/performance)

Signup Profile

Profile fields on Signup forms.

Ubercart Event Registration

Watch a demo video of this module!

The Ubercart Event Registration module is a feature package paired with a small 'glue' module which yields a simple event registration system. The main goal here was to tie together webform module with Ubercart 2.x to give us a registration sign-up form which could have completely custom and unlimited form information, unique to each event, which can be updated easily by a site editor with limited Drupal experience.