Hey Joe,

I have a department at my university that is using the latest versions of mojoPortal and Event Calendar Pro.  (2.3.2.9 MSSQL / 0.0.2.2).  This office been experiencing some weird issues in ECP (for some time) that I, at first attempt, wasn't able to reproduce until delving into things a bit more (my first guess at their problems was user error ).  In any case, I recreated a lengthy description plus screen shots of the issues at http://code.colostate.edu/bug-reports.aspx.  In summary the issues are the following:

1. Incorrect Registration Allowed Date After Adding A Recurring Event
2. Updating Registration Allowed Date Within Series Deletes Prior Recurring Events
3. Updating Registration Allowed Date Unintentially Creates Additional Events
4. Deleting Entire Series Doesn't Behave As Expected

The occurrence of these bugs is largely dependent upon certain steps being taken which I outlined at the above URL.  Anyways, please let me know if you need clarification on any point, and thanks in advance for any help you can provide, as always!

-Shaun



Morning Joe,

I get how things are working now that I understand the logic behind the Registration Allowed piece. We were under the impression that the Registration Allowed Date (specifically, the begin date) would be the same for all occurrences in the series (or at least start that way, until you edit an instance of the series). So, I apologize for wording this as a “bug”, I think this would better fit in the area of feature request now that I understand what’s going on.

This office is using ECP as a registration system for their tutoring program such that, at the beginning of the semester, they want to create a semester's worth of tutoring sessions at one time, and allow a student to register for any of those sessions (perhaps even just one at the end of the semester, and thus not allow automatic admission to all recurrences) without editing any instances of the series. In this scenario, in which they want to keep the Registration Allowed “Begin” Date the same for all instances, it would be handy to have an option to override the current behavior in ECP.

"Bugs" #3/4 below only occur because of our understanding (or misunderstanding!) of my first point (ie, to reproduce those 2 issues you would have to first take the first step that we took and try to update all occurrences using the same begin date, which then breaks apart the series). So, I can see why you weren’t able to reproduce 3 and 4 below, as we weren’t using the system as you intended it.

So, in short, I believe I’m in your paradigm now , and will convey this to my colleagues.

Sounds great - thanks as always!