I've committed the initial D6 port to HEAD (#222217: Port to 6.x), but I haven't yet tested any of the event 6.x-2.* integration. Sadly, there's no official release to test against, so I have no idea if event is even in a state worth testing yet. Let's use this issue for any discussion, patches, etc, related to that. Thanks.

Comments

killes@www.drop.org’s picture

I've installed the current signup snapshot and it seem to work well.

dww’s picture

@killes: Have you tested auto-close and reminder emails with event2? Are the reminders sent at the right time, and is the %time token properly replaced in those messages? Does auto-close happen at the right time? Those are the two features that most need to be checked. Also, is the start time listed properly on the signup admin page at admin/content/signup? Thanks.

briggsm’s picture

I think this comment is applicable here - I'm testing signup with Calendar/Date combination. Specifically with Repeating Dates (an event/content type that has a repeating date). It appears that Signup unchecks the "Send reminder X day(s) before EventName" checkbox, after it sends the reminder email. This works for a 1-time event, but if the event repeats, you won't get the reminder email the next time the event happens. I think it would be good if you could sign up for a repeating event, and get reminded each time the event occurs.

Let me know if you need more details.
Thanks!
Mark

dww’s picture

@briggsm: This is about event.module, as linked in the original post. You're using Calendar/Date, so at minimum you're talking about #330821: Test/fix CCK date 6.x-2.* integration. However, since you're talking about repeating dates, you really mean #298122: Integrate Signup with the Date Repeat API.

killes@www.drop.org’s picture

I've tested everything as requested in #2 and it seems to be working.

dww’s picture

Status: Active » Fixed

I just checked w/ killes in IRC and he confirms that auto-close and reminder emails are working fine. Calling this fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.