I was thinking the same... its the distinction between a weekly club where a person goes every week and wants to show that... versus say an Intro to EasySocial class which is held every week but a person would only be going once.

would sure be useful to be able to distinguish somehow!

similar thinking can actually apply to general stream postings too... should they show on the one instance, or on all the instances. this is important for being able to communicate to all attendees.

I wonder if the solution could be to let the event creator pick whether the recurrences should be unique events (as they are now) or virtual ones which just link back to the master which would have the attendees and stream items intact? hope that makes sense... I think it would work great like that.

If the event is happening every year and every Sunday of the week. It would be kind of annoying to click through each Sunday of the Month and annoying to see that this User is attending say 45 times in the stream. Don't you think? I agree with you Andy that the Attendee information should be tied to the Parent/Master event. Would be nice also if there is a setting for Admin to Show or Not Show Attendees - but visible to Owner and Admins only.

Question is, can we turn off Event Stream for user attending?

Hi,

Hmm if you are the creator and you are creating a recurring event (be it group event or not), the creator should be automatically listed as attending to all the event.

Guests however, currently the way it works is, if you are editing an existing event, and there are already an existing guests in the event, if there are recurring event needed to be created upon that edit, then all the guests are carried over. However, new guests who are attending a recurring event currently, will only apply to 1 single event.

Yes you can turn off the event stream for user attending at backend -> Application -> Events - Guests

Hi Jason... Yes that's what we thought... so any thoughts on the concept of the option to tie recurrence instances to the master event in terms of the stream and attendees etc (presumably this saves lots of processing time / hassle and in many cases might be what people prefer).

I think my example above illustrates the likely 2 different uses people have for recurrence.... recurring events that always attract the same people and comments / questions... and then recurring events that you'd only really expect people to attend once.

HI,

Currently the way it works is, each recurring event is created as an independent event. There are "some" links in between but in terms of "stream" and "guests", they are independent.

I understand that some may want recurring to be "linked" but due to certain limitation (especially on server performance), currently we are opting to go with, recurring are just basically series of event that is created independently based on the pattern that you've defined. Each event stands independently as its own.

Hi Jason,

Hmm if you are the creator and you are creating a recurring event (be it group event or not), the creator should be automatically listed as attending to all the event.

Well, I tested it with Group Events and I was the Creator and only added to the Parent event.

I understand that some may want recurring to be "linked" but due to certain limitation (especially on server performance), currently we are opting to go with, recurring are just basically series of event that is created independently based on the pattern that you've defined. Each event stands independently as its own.

I agree with you on this Jason, I know how recurring records could affect server performance. I've seen this with JEvents, I'd like to suggest different way of blocking users from creating tons of repeats. Could it be a better way to add a cap on the Calendar, to how far a user can set in terms of Year in setting their End Repeat On instead of Recurring Limit number? Reason is, users does not know that they are only allowed to repeat 50 times. If you cap their max date to 1 year, then they can only create/repeat events say from 2014 to 2015.

The beauty of treating each repeats as independent entry is with some events may start regularly say on Mondays but after 3 weeks they have to change it to Wednesday for some reason. So the event creator can simply edit that particular repeat and change the Date without affecting the entire event repeats. By the way, what happened to the Edited repeat when the event creator edit the Parent Event? Will it override all the repeats?

But to what Andy is saying, if I understand it right, I agree with him, that the Event attendance info should be tied to the Parent event and not for each repeat independently. Depending on how the table was designed, you can still filter the widgets to show Attendance for each repeat.

Why not add an option to the Event to:

• Record Attendance as a Whole - when a User click Attending they are auto added to all Repeats
  
• Record Attendance by Repeat - when a User click Attending they are only recorded to attend on what ever Repeats they click
  

This way, event creator can set each event depending on their needs or the event design.

Thanks,

Jackson

Hi,

1. Currently it is not possible to link guest attendance across recurring event.

2. I will investigate the creator not attending child events and fix it.

3. Currently the only limit that we are imposing is the total number of recurring allowed. If the pattern surpasses the allowed limit, an error message will be visible on the field immediately to notify user.

4. If you edit an existing event with recurring events and change the pattern, existing child events won't get deleted, and new recurring events will be created. You can opt to clear old recurring events (there is a button on the field).

Hi,

I tested this locally and I am not able to reproduce this issue. Are you still able to reproduce this issue on your site?

Hi Jason,

Sorry for the late reply. Yes, I was able to replicate this issue on Group Events but it does work if I am creating personal events. Just not with Groups though.

Thanks,

Jackson

Hi Jason,

I am getting a white screen of death when creating an Event, turned on Error Reporting and getting this:

Notice: Undefined variable: now in /public_html/media/com_easysocial/apps/fields/event/startend/startend.php on line 41



Fatal error: Call to a member function format() on a non-object in /public_html/media/com_easysocial/apps/fields/event/startend/startend.php on line 41



Fatal error: Access to undeclared static property: JLoader::$classes in /public_html/libraries/loader.php on line 195

Thanks,

Jackson

Hi,

Hmm that is a separate issue. I've patched it on your site as well.

Hi Jason,

Confirmed! Your patch worked! and the white screen error is gone, what was that?

Thank you so much Jason, you guys are awesome!

Jackson

Thanks for updating Jackson, glad that your issues are resolved now