Chekin' in

[Daniel Abrams]

So I see now. Clone 0 means one event. Clone 1 means one subevent. Clone 2 means 2 subevents.

When would there ever be one sub-event? I was thinking a one-day event would not need subevents, but I guess one might want multiple subevents in one day - two topics simultaneously, for instance.

I guess that means it's good the way it is. I'll move on.

Cloning is to add days to an event in the case of multi-day events. Not really sub-events, but days for an event. For example, a two day weekend seminar. It's not for creating multiple subevents in a single day. Yes, the date and time are the same each time you clone, but you are supposed to edit those for each clone to create another day.

[Daniel Abrams]

Should not be the case. Noty seeing browser cached stuff?

[Hollis Brown]

No, that doesn't explain it.

[Daniel Abrams]

No, that doesn't explain it.

Can I see this?

[Hollis Brown]

There should be nothing here:
https://development.chapteroffice.com/calendar/

[Hollis Brown]

So I see now. Clone 0 means one event. Clone 1 means one subevent. Clone 2 means 2 subevents.

When would there ever be one sub-event? I was thinking a one-day event would not need subevents, but I guess one might want multiple subevents in one day - two topics simultaneously, for instance.

I guess that means it's good the way it is. I'll move on.

Cloning is to add days to an event in the case of multi-day events. Not really sub-events, but days for an event. For example, a two day weekend seminar. It's not for creating multiple subevents in a single day. Yes, the date and time are the same each time you clone, but you are supposed to edit those for each clone to create another day.

But you could use it that way--Same day--same times--different descriptions.

[Daniel Abrams]

There should be nothing here:
https://development.chapteroffice.com/calendar/

What did you do? You deleted the first day, but the cloned days remain. Yes?

[Daniel Abrams]

So I see now. Clone 0 means one event. Clone 1 means one subevent. Clone 2 means 2 subevents.

When would there ever be one sub-event? I was thinking a one-day event would not need subevents, but I guess one might want multiple subevents in one day - two topics simultaneously, for instance.

I guess that means it's good the way it is. I'll move on.

Cloning is to add days to an event in the case of multi-day events. Not really sub-events, but days for an event. For example, a two day weekend seminar. It's not for creating multiple subevents in a single day. Yes, the date and time are the same each time you clone, but you are supposed to edit those for each clone to create another day.

But you could use it that way--Same day--same times--different descriptions.

Not the intended purpose. Keep it that way, or force cloned days to be different days?

[Daniel Abrams]

So I see now. Clone 0 means one event. Clone 1 means one subevent. Clone 2 means 2 subevents.

When would there ever be one sub-event? I was thinking a one-day event would not need subevents, but I guess one might want multiple subevents in one day - two topics simultaneously, for instance.

I guess that means it's good the way it is. I'll move on.

Cloning is to add days to an event in the case of multi-day events. Not really sub-events, but days for an event. For example, a two day weekend seminar. It's not for creating multiple subevents in a single day. Yes, the date and time are the same each time you clone, but you are supposed to edit those for each clone to create another day.

But you could use it that way--Same day--same times--different descriptions.

Not the intended purpose. Keep it that way, or force cloned days to be different days?

I think we should force as different days. Otherwise, they become more like presentations which is something else which we will be be bringing back later.

[Hollis Brown]

So I see now. Clone 0 means one event. Clone 1 means one subevent. Clone 2 means 2 subevents.

When would there ever be one sub-event? I was thinking a one-day event would not need subevents, but I guess one might want multiple subevents in one day - two topics simultaneously, for instance.

I guess that means it's good the way it is. I'll move on.

Cloning is to add days to an event in the case of multi-day events. Not really sub-events, but days for an event. For example, a two day weekend seminar. It's not for creating multiple subevents in a single day. Yes, the date and time are the same each time you clone, but you are supposed to edit those for each clone to create another day.

But you could use it that way--Same day--same times--different descriptions.

Not the intended purpose. Keep it that way, or force cloned days to be different days?

Leave it the way it is.

[Hollis Brown]

So I see now. Clone 0 means one event. Clone 1 means one subevent. Clone 2 means 2 subevents.

When would there ever be one sub-event? I was thinking a one-day event would not need subevents, but I guess one might want multiple subevents in one day - two topics simultaneously, for instance.

I guess that means it's good the way it is. I'll move on.

Cloning is to add days to an event in the case of multi-day events. Not really sub-events, but days for an event. For example, a two day weekend seminar. It's not for creating multiple subevents in a single day. Yes, the date and time are the same each time you clone, but you are supposed to edit those for each clone to create another day.

But you could use it that way--Same day--same times--different descriptions.

Not the intended purpose. Keep it that way, or force cloned days to be different days?

I think we should force as different days. Otherwise, they become more like presentations which is something else which we will be be bringing back later.

That gets us into the discussion of having a basic manage-events and an advanced manage-events. Basic would be what we have. Advanced would include presentations and speakers and stuff. Otherwise admins are going to be overwhelmed. So leaving it like it is in basic makes sense to me.

[Hollis Brown]

There should be nothing here:
https://development.chapteroffice.com/calendar/

What did you do? You deleted the first day, but the cloned days remain. Yes?

Don't remember. I first deleted everything to start with a clean slate. I don't think I checked the calendar to find all those events gone. Some of what is there, I think you created before I started testing. Some of what I created today is gone and some is still there. That's what I know.

I could get more strategic in my testing now that we know what we're looking for.

[Daniel Abrams]

So I see now. Clone 0 means one event. Clone 1 means one subevent. Clone 2 means 2 subevents.

When would there ever be one sub-event? I was thinking a one-day event would not need subevents, but I guess one might want multiple subevents in one day - two topics simultaneously, for instance.

I guess that means it's good the way it is. I'll move on.

Cloning is to add days to an event in the case of multi-day events. Not really sub-events, but days for an event. For example, a two day weekend seminar. It's not for creating multiple subevents in a single day. Yes, the date and time are the same each time you clone, but you are supposed to edit those for each clone to create another day.

But you could use it that way--Same day--same times--different descriptions.

Not the intended purpose. Keep it that way, or force cloned days to be different days?

I think we should force as different days. Otherwise, they become more like presentations which is something else which we will be be bringing back later.

That gets us into the discussion of having a basic manage-events and an advanced manage-events. Basic would be what we have. Advanced would include presentations and speakers and stuff. Otherwise admins are going to be overwhelmed. So leaving it like it is in basic makes sense to me.

Okay, gonna make some changes tomorrow. So, more more testing until I'm done tomorrow.

[Daniel Abrams]

There should be nothing here:
https://development.chapteroffice.com/calendar/

What did you do? You deleted the first day, but the cloned days remain. Yes?

Don't remember. I first deleted everything to start with a clean slate. I don't think I checked the calendar to find all those events gone. Some of what is there, I think you created before I started testing. Some of what I created today is gone and some is still there. That's what I know.

I could get more strategic in my testing now that we know what we're looking for.

I think what happened is how I described. I edited so when delete event, all attached subevents are also deleted. Tomorrow after I've made some changes, we will get back to testing.

[Daniel Abrams]

Okay, let's get back to testing. Let's start with this first. Create an one day event, and then clone subevents in the same day.