10994 Posts in 2728 Topics by 1819 members
|Go to End||Next >|
12 April 2010 at 3:14am
I can't replicate the issue with the recurring events. In my experience, that's usually a user error caused by leaving an end date in the repeating date, so it never gets a chance to repeat. Make sure that's either empty or far into the future.
All the other stuff is checked in.
12 April 2010 at 6:10am
Unreal. That's solved all of those issues. Yeah, looks like the issues I was having with Recurring Events comes from my inexperience with the feature. To clarify, is the following correct?
a) An Event that is Recurring should only have one DateTime and that DateTime must not have an End Date
b) If the Start Date specified in DateTime does not fit the Recurring pattern setup for the Event, the Event will not show for that date
I'm now in SS template world. When I click though to an Event, inside the following block the vars $ICSLINK, $_Dates and $_Times are coming back empty. I'm pretty sure they're supposed to be the Dates/Times of the Event that was clicked on?
<% control CurrentDate %>
<h4><a href="$ICSLink" title="Add to Calendar">$_Dates</a></h4>
<% if StartTime %>
<% end_if %>
<% end_control %>
I have subclassed Calendar, CalendarEvent and CalendarDateTime but only to extend in minimal ways, nothing about dates. Would you have an idea of what I should check out? I'm not sure exactly what it should be returning but I'm sure empty strings isn't right.
Thanks so much for all this help!
12 April 2010 at 6:26am
Ah dang. Seems the Announcements tab of a Calendar page is now empty - the Announcements table is missing.
12 April 2010 at 6:59am
For you question about recurring events, you're pretty much correct, only you may have an end date if the recursion pattern expires at some point in time. If left empty, the recurring event repeats until the end of time. When developing this functionality we went back and forth on how to represent the boundaries of a recurring event. Turns out most users expected that if a date/time record had an end date, the recursion should end at that point. So we went with that. I do see a lot of people using the same start/end dates that end up canceling out the recursion, though. Makes me wonder if I should update it so that matching start/end dates will result in infinite recursion as well as a start date with a null end date.
If your start date doesn't match the pattern, the date is ignored. That's correct.
Not sure what's up with your CurrentDate control. Is it even entering the control? If so, put $ID in there to make sure it's returning an object. I can't replicate the problem on the demo site.
The bug on the announcements tab has been resolved and checked in.
Thanks for your continued testing. Always helps to have a live one when you're making incremental hot fixes like this.
12 April 2010 at 11:46am
Diary as well as the last Event Calendar doesn't run.
Diary doesn't accept the date and makes much more trouble.
12 April 2010 at 12:08pm
EventCalendar 2.4 is on the trunk. For the 2.3 version, use /branches/2.3/event_calendar
12 April 2010 at 11:14pm
Thanks for your run-down on Recurring Events, that all makes much more sense to me now!
Right now what I'll probably do is add a literal field above the Recursion checkbox that explains to CMS Users what is required (DateTime-wise) for a Recurring Event to working as intended.
I started afresh with the latest rev but am still having CurrentDate control issues. Yes it is entering the control, but ID doesn't bring back anything. Confusing because it was a fresh install.. my next idea was to try adding an Event on your test site - and it's not working there either.
So either I need a good forehead slap because I'm not doing some part of the add Event process correctly (quite likely lol), or it's in the mod somewhere. If you get a few mins would you mind having a look at this event, confirming that you're seeing the prob too, and checking if I've missed something?
13 April 2010 at 12:22am
Page http://silverstripe.org/event-calendar/ seem to be wrong: it indicates
Compatible with: SilverStripe 2.2.3, 2.3
Subversion access: http://bluehousegroup.svn.beanstalkapp.com/modules/trunk/event_calendar
but as svn trunk is r99 as well one needs to have two different links: to 2.4 and 2.3 versions with the clear indication which is which
This is also the case with the DataObjectManager, Image Gallery, but not SWFUpload where it is indicated that it is compatible with 2.2-2.4.
Sure, one can find relevant info on forum but still module pages should be updated
|Go to Top||Next >|