I just upgraded to the latest version. However, none of my recurring events are getting returned now.
When I go the recurring event it appears that "End Date" is now mandatory. I don't believe this was the case before.
The problem is that supplying the end date essentially turns the event into a single-occurrence event. If I enter a date and time, say, an hour past the start date/time the event shows up properly, but there's no recurrence.
If I enter a date that's past the start date it becomes a (single) multi-day event.
EndDate was always ment to be mandatory on recurring events. For recurring events the enddate indicates the end of the last occurance of the event. I'm not able to recreate your issue, but if you post an example screenshot it would be helpfull.
This forum doesn't seem to support uploading images and I don't have time to upload them elsewhere right now, but here's the output:
I have created two events for this test:
Title: test event (recurring)
Start date: 2017-01-01 12:00:00
End date: 2018-01-01 12:00:00
Recurrence: Weekly - every single week on Monday
Title: test event (single)
Start date: 2017-01-04 14:00:00
End date: 2017-01-04 16:00:00
Recurrence: none
The single event has a start and end date that denotes a 2-hour event. However, the end date of the recurring event turns each event into a multi-day (even multi-month) event. Perhaps I'm assigning a different definition to "end date"?
After your last post I did some thinking, and I have made a new version where I have made some changes.
Startdate is the same, endDate is optional, but when supplied this will determine the duration of the event. The new optional field recur until will decide how long the event will recur, if not provided the event will recur forever.
I also added the possibility to add except days, where you can add date where the event will not happen.
I have not had much time to test this version, but I still have released it so you can try it if you want to.
The result you got in your JSON-feed seems to be the result I would expect. The only thing is that I have failed to edit the endDate for the recurring events. (But that is fixed in the 0.1.7 version)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: Nullable object must have a value.
Source Error:
Line 14: DateTime endDateTime = DateTime.ParseExact(Request.QueryString["end"], "yyyy-mm-dd", System.Globalization.CultureInfo.InvariantCulture);
Line 15:
Line 16: foreach (CalendarEvent ce in Calendar.getEvents(DateTime.Now.Date, DateTime.Now.AddDays(10000), "eventDate", true))
Line 17: {
Line 18:
Also, I'm not seeing the new field "recur until" for recurring events.
This error was because of daily recurring events with no days selected. Should be fixed now.
After the installation of the latest version you may have to clear your browser cache, to se the latest changes. If that doesn't work you may even have to set you Umbraco to debug mode to re-minify the javascripts.
I've deleted all the calendar items just to be sure, and now it seems to be working. Still having to enter the end date via the calendar instead of typing the value, though. The "recur until" field also still doesn't show up.
The recur until field should be visible when you select to have a recurring event. In a new build of 0.1.7 I have fixed the endDate-validation, so it should now also validate on direct input.
To be sure the new js is loaded please clear your browser cache, a hard reload (Ctrl+F5) won't always reload the files. (In Google Chrome settings you can choose to disable cache while using dev.tools(F12-tools), in IE doing a Ctrl+F5 while running Dev Tools seems to to it, but Firefox needs to remove cache or disable cache in about:config and set network.http.use-cache to false)
Bug? Recurring events broken in latest release (0.1.6)
I just upgraded to the latest version. However, none of my recurring events are getting returned now.
When I go the recurring event it appears that "End Date" is now mandatory. I don't believe this was the case before.
The problem is that supplying the end date essentially turns the event into a single-occurrence event. If I enter a date and time, say, an hour past the start date/time the event shows up properly, but there's no recurrence. If I enter a date that's past the start date it becomes a (single) multi-day event.
EndDate was always ment to be mandatory on recurring events. For recurring events the enddate indicates the end of the last occurance of the event.
I'm not able to recreate your issue, but if you post an example screenshot it would be helpfull.
This forum doesn't seem to support uploading images and I don't have time to upload them elsewhere right now, but here's the output:
I have created two events for this test:
Output (2017-01-01 - 2017-02-15):
(See http://our.umbraco.org/projects/website-utilities/ksumbraco7calendar/ksumbraco7calendar/55517-Feature-Suggestions for the source code that generates the JSON output)
The single event has a start and end date that denotes a 2-hour event. However, the end date of the recurring event turns each event into a multi-day (even multi-month) event. Perhaps I'm assigning a different definition to "end date"?
After your last post I did some thinking, and I have made a new version where I have made some changes.
Startdate is the same, endDate is optional, but when supplied this will determine the duration of the event.
The new optional field recur until will decide how long the event will recur, if not provided the event will recur forever.
I also added the possibility to add except days, where you can add date where the event will not happen.
I have not had much time to test this version, but I still have released it so you can try it if you want to.
The result you got in your JSON-feed seems to be the result I would expect. The only thing is that I have failed to edit the endDate for the recurring events. (But that is fixed in the 0.1.7 version)
Hi Ole Martin,
I'm encountering a couple of issues with 0.1.7:
Nullable object must have a value.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Also, I'm not seeing the new field "recur until" for recurring events.
Thoughts?
This error was because of daily recurring events with no days selected. Should be fixed now.
After the installation of the latest version you may have to clear your browser cache, to se the latest changes.
If that doesn't work you may even have to set you Umbraco to debug mode to re-minify the javascripts.
web.config around line 117
Should I still use 0.1.7?
No luck on getting the new field ("recur until") to show, even after enabling debug.
Looks like there's another bug that may have slipped in; the end date needs to be at least a day after the start date.
Update: apparently the end date needs to be entered by using the calendar; typing (or copy/paste from the start date) doesn't properly validate.
I've deleted all the calendar items just to be sure, and now it seems to be working. Still having to enter the end date via the calendar instead of typing the value, though. The "recur until" field also still doesn't show up.
The recur until field should be visible when you select to have a recurring event.
In a new build of 0.1.7 I have fixed the endDate-validation, so it should now also validate on direct input.
To be sure the new js is loaded please clear your browser cache, a hard reload (Ctrl+F5) won't always reload the files. (In Google Chrome settings you can choose to disable cache while using dev.tools(F12-tools), in IE doing a Ctrl+F5 while running Dev Tools seems to to it, but Firefox needs to remove cache or disable cache in about:config and set network.http.use-cache to false)
Aaargh! Clearing my browser cache did the trick. :-|
By the way, the "Except on" field is a very nice addition too!
is working on a reply...