Plone recurring events
idea by natea
Add events to Plone which occur more than once with the same details and on a regular basis.
target
Project progress
The project has already been 0% completed, but the developer has stalled the development.
You need to come to an agreement with the developer. You may just need to pledge more money.
The project’s comments may contain more information.
Developer Info
natea is developing this project for $5000 over 2 months.
Go to the developer’s website.
Project Info
License is open-source.
8 people are pledging, but no development has yet been paid.
Project Tags
calendar calendaring dateable events hcal ical icalendar plone plone4artistscalendar python schedule zope zope3Project details
This project aims to make it possible to add an event that is recurring, meaning that it occurs more than once. This is currently not possible in Plone - the only way to do it is to duplicate the event by a copy-paste operation. We propose to implement recurring events within Plone.
Much of this work has already been completed by Lennart Regebro as documented in PLIP #158 and on his blog but there are still much refactoring, UI work and tests that need to be completed before it’s ready for public use.
The work outlined in the 6.5 days is as follows:
Recurring events:
-
Finishing up the events: 1 day.
-
iCalendar support for recurring events: 2 days. The Marshalling hack is ugly and limited to Plone Events, so it’s not pluggable and doesn’t support the event extensions like recurrence and extra location info.
-
A replacement for the calendar portlet that supports recurring events. 0.5 days.
New event schema:
- Using archetypes.schemaextender to completely revamp the ATEvent schema into two or more pages that make some sort of sense from a usability perspective. (1 day)
Dateable 1.0:
-
Replacing the rest of p4a.calendar. (1 day)
-
Better tests (1 day)
-
The recurrence support above
We are planning to do the bulk of this work during the Plone Calendaring Sprint which is taking place April 28-May 4 in Boston, MA.
You can support the development of recurring events by making a pledge here, or if you want to support the sprint itself, we have a set up a sponsors page where your company/organization can make a donation.
2 comments (oldest first)
A great, worthy and long long long overdue project. My very best wishes to all (I wish I could come sprint in Boston too).
Can I put in a request here to consider first/last/third XXXday of the week type recurrence specifications., and also ‘every wednesday’ type specifications. These are very typically the sort of recurrences that appear in the real world, but many CMS solutions ignore them, and claim they have recurrent events on the basis of a fixed day number of each month, and often no other type of recurrence.
Actually if anyone has a reference to a good existing web interface to these specifications I’d be interested to hear about it.
Add a comment
Before you add a comment you must be signed up – it takes about 30 seconds. Sign up now.