Load additional events when using ajax

Relevant bits of code:

Date module parses a single date into a range of itself to itself. So 2011-11 becomes 2011-11 to 2011-11.
http://drupalcode.org/project/date.git/blob/refs/heads/7.x-2.x:/date_api...

This is where we add our value:
http://drupalcode.org/project/fullcalendar.git/blob/refs/heads/7.x-2.x:/...

This is where we check for it:
http://drupalcode.org/project/fullcalendar.git/blob/refs/heads/7.x-2.x:/...

Ok so here is what I found out

If in fullcalendar.fullcalendar.js around line 50 you replace

var date, month, year, date_argument, arguments, fetch_url;
date = $('.fullcalendar', calendar).fullCalendar('getDate');
month = $.fullCalendar.formatDate(date, 'MM');
year = $.fullCalendar.formatDate(date, 'yyyy');
date_argument = year + settings.separator + month;

with this

var prev_date, next_date, prev_month, prev_year, next_month, next_year, date_argument, arguments, fetch_url;
        
prev_date = $('.fullcalendar', calendar).fullCalendar('getDate');
next_date = $('.fullcalendar', calendar).fullCalendar('getDate');
        
prev_date.setMonth(prev_date.getMonth() - 1);
prev_month = $.fullCalendar.formatDate(prev_date, 'MM');
prev_year = $.fullCalendar.formatDate(prev_date, 'yyyy');
        
next_date.setMonth(next_date.getMonth() + 1);
next_month = $.fullCalendar.formatDate(next_date, 'MM');
next_year = $.fullCalendar.formatDate(next_date, 'yyyy');

date_argument = prev_year + settings.separator + prev_month + settings.separator + settings.separator + next_year + settings.separator + next_month;

It'll work when moving between months, but not when the calendar is loaded. I can't figure out where it sets the default date in the initial view. All we would need to do was pass it a range like 2011-10--2011-12 and it will get all the events for October, November and December. Technically we could pass it 2011-10-30--2011-12-03 and we would get the events for the showing month. But we would have to calculate what is the first date showing. This may take some work when having to consider what the user chose as the first day of the week.

Any ideas?

See #1353102: Custom initial date is broken for why initial dates are different/broken.

Here is a patch that is a proof of concept of getting this to work. There are some assumptions made that might need to be changed or removed.

1) I create a default fixed value of a range from the previous month to the next month. probably needs to be checked for ajax being enabled.
2) I then parse that argument to get me the starting date for fullcalendar.
3) For every update using ajax I create a range of the previous month to the next month and use that as the argument.

Hopefully it's in the right direction.

Seems that with ajax turned off it still works fine. Only issue I've found so far is if you try to set a default date. This patch fixes that.

It will get converted to january 2012. The strtotime function takes care of that for php and setMonth() takes care of that for javascript. Just noticed I left a couple console.log's in there. Will have to remove that.

+++ b/js/fullcalendar.fullcalendar.jsundefined
@@ -47,11 +47,25 @@ Drupal.fullcalendar.processOptions = function(settings, dom_id) {
+        prev_date = $('.fullcalendar', calendar).fullCalendar('getDate');
+        next_date = $('.fullcalendar', calendar).fullCalendar('getDate');

Can we use something like next_date = $.extend({}, prev_date); to not run that twice?

That, plus the duplicated lines, plus the console.log(). Otherwise, this makes a lot of sense.

I think @aspilicious meant something like this:

// Instead of:

$start = date('Y-m', strtotime($style_options['times']['date']['year'] . '-' . $style_options['times']['date']['month'] . ' -1 month'));
$end = date('Y-m', strtotime($style_options['times']['date']['year'] . '-' . $style_options['times']['date']['month'] . ' +1 month'));

// Do:

$date_string = $style_options['times']['date']['year'] . '-' . $style_options['times']['date']['month'];
$start = date('Y-m', strtotime($date_string . ' -1 month'));
$end = date('Y-m', strtotime($date_string . ' +1 month'));

Here is an updated patch.

Here is one without the $.extend() code that doesn't seem to be working.

Here is the fixed date copy version.

With Ajax

• with default date: WORKS
• with date from url: ?month=3 shows April with no results
• with no default or url: WORKS

Without Ajax

• with default date: month set to May shows June
• with date from url: ?month=3 shows April
• with no default or url: WORKS

This one removes the $separator variable. Also it fixes the other 3 broken issues reported above.

This version limits the ajax queries to only the visible calendar dates.

Some more cleanup with using formatDate()

+++ b/js/fullcalendar.fullcalendar.jsundefined
@@ -47,11 +47,13 @@ Drupal.fullcalendar.processOptions = function(settings, dom_id) {
+        prev_date = $.fullCalendar.formatDate(start, 'yyyy-MM-dd');
+        next_date = $.fullCalendar.formatDate(end, 'yyyy-MM-dd');

Brilliant.

+++ b/theme/theme.incundefined
@@ -166,12 +166,11 @@ function fullcalendar_check_arguments($view) {
+    $timestamp = strtotime($date_range[0] . " +1 month");

I'm not quite sure I understand this line, and don't we just do $settings['date']['month'] = $month - 1; a couple lines down? Maybe we should comment why we do this here.

I'll test all 6 cases again like in #16, but I think this looks really good.

With ajax, with a query string, nothing is loaded. Here is a patch that moves stuff around.

hook_fullcalendar_options_process is a terrible hook. It runs way too late for most things, and does too much.

Okay, this finally breaks up the insanity of hook_fullcalendar_options_process.

Okay, I hope we never again have to worry about zero-based vs one-based months.

This one works for me in all 6 cases.

@redndahead said this worked in IRC, and I really want to commit this, but I should really let aspilicious double check.

This patch adds the fix from here since it's a small fix and we are already messing with that code. #1206518: Call a specific calendar view through the URL

cross posted

http://drupalcode.org/project/fullcalendar.git/commit/e5a8bf7
Awesome.

Now we just need to figure out http://drupal.org/node/1206742 and we're really pretty much done.