Quick question about RSVP times. If someone RSVPs "Maybe" and then updates it to "Yes", it changes their time to when they updated their RSVP. Would it be possible to keep the time as the original time they RSVPd "Maybe"?

Can anyone tell me what the following means when someone gets a reminder email:

I know that the first part is the date of the event but what is the "13905 Days" part?

I have this weird bug and I quite don't know how to explain it:

When I click on the event be it with a test account or my admin account, it shows just fine.

But when some specific users click on the same event, it shows as being closed with a whole different list of attendees.

I peeked in the DB and there's no trace of those users being registered to this event, so i'm quite puzzled.

EDIT:
Apparemtly it's linked to timezones. I live in australia and thus set up the event accordingly to my timezone for sunday. But for US people, the event is on a saturday evening and for some reason they can't register, as if the event wouldn't know the difference between 0 and 1 day.

Also the server is based in Australia, so tht might be the source of this issue?

Ok, that's completely irrational, and I've no idea what's going on with my install of this mod.

If I set up an expiration date through the admin options, half of the attendees can't see the other half, depending on their timezone.
Also expiration date is off by one day (before)/ one week (after) still depending on your timezone.

If I create an event without an expiration date, but activate it afterwards, it works just fine.

Can someone help with a problem please ? I've just installed this on 3.6.8 and it works fine other than my users are having a 'Style' issue when they view the events.

Any ideas ?

http://www.throttlejockey.co.uk/foru...0569#post70569

The link to the calendar event opens up in a new window in the style that others aren't using.

Quick Reply is not working for Events Thread. I get the below error

I have the same problem. But I'm not sure if it is this mod, or the Event Forums mod.

I edited the template to remove the Quick Reply box in our calendar forum.

yeah, im not sure where the problem comes from either :(

how hard is it to adjust this mod to change it from having options yes no and maybe, to Entrant, Spectator, no

I've been having no end of headaches trying to figure out the following problem but I've finally found a resolution.

Problem:

I have Event Attendance, Event Forums and the bridge installed on my vB3.6.8pl2 board.

When I post using quick reply from a threaded-mode view to an event whose RSVPs have closed, I get the following message:

This does not happen when replying from linear mode, via quick reply or not.

Solution:

After lots of investigation, false starts, long pauses and just ignoring it, I've discovered the following in version 1.2.1, in the calendar_rsvp_form template.

Notice the </form> tag? That's the closing tag for a form opened at the top of this template, except the form was opened outside of the if block. When RSVPs close, the closing form tag is lost.

The easy resolution is to change the block above to the following:


Notes:

The reason this does not affect linear mode posters is because the posting is done via AJAX. However, for threaded-mode users the posts are actually POSTed. Normally, they'd be posted off to the newreply.php script correctly but because a form block further up isn't close, the submit information for the quick reply block now believes its supposed to be posting to calendar.php. That'd be fine, except that the action "newpost" is not recognised by calendar.php so it eventually falls back to its default action of posting an error. Also, because none of the rest of the body in calendar.php is called, none of the calendar hooks fire (fortunately, otherwise this would have been impossible to debug) so the hook that forcibly forwards the user to the thread for that event (Event Forums functionality) doesn't fire.

But all this is ultimately caused by a misplaced </form> tag inside the Event Attendance code. Hence the bug report/solution here.

Hope that helps. :)