Recurring Google Appontments

[Dean Maunder]

E!A seems to only sync the first occurrence of a recurring appointment that is created in the Google calendar.

Is there any way to make it sync all recurring appointments up to the limit of sync_future_days?

[Dean Maunder]

If anyone is struggling with this, the solution was to update the following in google_sync.php.  

line: 297

$params = array(

            'timeMin' => date3339($start),

            'timeMax' => date3339($end),

        );

to:

$params = array(

            'timeMin' => date3339($start),

            'timeMax' => date3339($end),

            'singleEvents' => true

        );

[Alex Tselegidis]

Well Done! :D

[Sam Filo]

Does not work, it is the same

[Dean Maunder]

Work's OK for me Sam, but without any further troubleshooting information (post your code, post any errors you get), I'm afraid I'm not going to be much more help.

[Craig Tucker]

I have also tried this as listed above.  I am not seeing the recurring appointments in the Easy!Appointments Calendar.  What I do see is an unavailable period stamped with the original appointment but noting on the following weeks in EA.

[Craig Tucker]

Also, no error codes are coming up.  My code is:

[Craig Tucker]

Perhaps there is something that needs to be turned on in the Google Developer Console for the Calendar API,  It is enabled but perhaps there is a something that is being blocked?  I have atttached a screen shot of all that I see in the back end when a recurring appointment is set up in Google Calendar.  Apparently when I construct a recurring appointment another event "Unavailable" is added to the time slot for that day only. Odd.  I see no PHP errors. No additional appointments are added. 

[Dean Maunder]

Hi Craig,

I don't remember doing anything in the Google settings, but that doesn't mean I didn't.

Unfortunately we are not using EasyAppointments any more, so I'm not going to be much help.  

My best advice is to see what the code is doing when you run a sync, e.g. what it is requesting from Google and in what format, and what Google is responding with.

Regards,

Dean

[Craig Tucker]

Thanks Dean,

What I am seeing is that the  add_unavailable function is triggered for any recurring appointment modification on an event in the Google calendar after synchronization.  So,the update_appointment function is only working one way -- E!A to Google Calendar.

[Alex Tselegidis]

I'm sorry guys but v1.0 of E!A does not support recursive appointments. It will be added in a future release.

[Craig Tucker]

Hi Alex,

I don't think Dean's method was using E!A to manage recurring appointments but was using Google Calendar to handle that through the synchronization. I am not sure that the solution he posted here is sufficient to allow this.  He must have done more than the snippet of code here.  Which makes me think that a more graceful solution is to just have Google Calendar be the backend.  

[Craig Tucker]

This will allow the recurring events to show up into the calendar after synchronization.  I remarked out the timeMax and the slots were populated with recurring events that were set up on the google calendar.

       $params = array(

'singleEvents' => 'true', 

                        'timeMin' => date3339($start),

                        //'timeMax' => date3339($end)

The problems 

1. they are populated with "Unavailable" headings instead of the appointment type and client name.  The appointment type ends up in the notes section.  This should be easy to fix.
2. If the appointment is deleted on the E!A side, the corresponding is deleted on the google side but not the other way around.  I think this should also be easy to fix.  

So, I will keep playing with this.  

[Alex Tselegidis]

Seems promising :)

[Craig Tucker]

what I think I would like to do is to skip sync all together and just post the appointment data directly to Google Calendar. I think I would keep the client database as it is. Because it's more flexible. But why try to duplicate what is already existing in Google Calendar? it can already send reminders to all participants at any interval. It already does recurring appointment. And there are many other complex features that would be difficult to duplicate programmatically. And the API is so open. So I'm going to play with that.