Recurring Events

Warning

This product has not had a release in over 1 year and may no longer be maintained.

Scripts by Steven Haddox & Larry Lay that allows for the implementation of recurring events (as individual objects) within Plone.

Project Description

NOTES:

• Implementation of Recurring Events 2.0 has begun, view the Roadmap here.
• Recurring Events 1.0 has been released (on our promised deadline of March 31)!

You can join the Plone Recurring Events mailing list at: http://groups.google.com/group/Plone-RecurringEvents.

 

 

Recurring Events Version 2.0 Roadmap:

1. Utilize the same logic as from Recurring Events 1.0
   • Subclass event.py
   • Add support for Yearly frequency
2. Make recurring events implementation globally possible
3. One Object within the Plone site
   • Catalog will handle date ranges (including infinite events)
   • Support iCal standards
   • Allow for single event exceptions within a recurring event
4. Calendar Support:
   • Plone Portlet calendar
   • CalendarX
   • CalPlone

Recurring Events Version 1.0

This package will provide for the ability to create recurring events within a Plone site. Currently it is not in a product state but requires that the user create a new version of event.py and schemata.py within the filesystem and then imports several files within the ZMI.

Benefits of this implementation:

• Should work with Plone 2.1.0 or greater (2.1.0, 2.1.1 both tested)
• You can create recurring events within Plone (not possible with default installation).
• You can modify single events within a recurring event sequence (not possible with other proposals as of yet).
• You can upload files that are inserted as 'related items' to a single / recurring event.

Drawbacks with this implementation:

• Recurring events will be recreated within a subfolder with the event's title.
• Recurring events must have an end-date. The farther out the end-date, the longer the request takes to process as a new object must be created for each applicable date within the date range.
• There is an event object created for each date within the start and recurring end date range.

Future goals for this implementation:

• Consider subclassing the current Event.py into a separate file (avoiding the modification of the Event.py file)
• Modify the object creation code to utilize cloning instead of full-object creation (saving time)
• Try to find a way to create the objects as a background task (allowing user to browse instead of waiting for the event creation scripts to finish
• Package the scripts/files into a Product that can be installed through the QuickInstaller