SCSubscribe2

Using SeedCode Subscribe with Google Calendar

SCSubscribe2.GoogleCalendar History

Hide minor edits - Show changes to output

June 22, 2015, at 04:55 PM by 142.4.217.188 -
Changed line 25 from:
->''' 6.''' To revoke or "unpublish" a private link, just delete that calendar entry from SeedCode_Subscribe_Setup.fmp12. If you want to republish it using a new link, duplicate the calendar first, then delete the original. Duplicating a calendar will clear the log, but everything else will be preserved, including your filters. Then just send your users the new private link. Note that while revoking a private link will preclude further updates, it won't delete data already synced to subscribers' Google accounts.
to:
->''' 6.''' To revoke or "unpublish" a private link, just delete that calendar entry from SeedCode_Subscribe_Setup.fmp12. If you want to republish it using a new link, duplicate the calendar first, then delete the original. Duplicating a calendar will clear the log, but everything else will be preserved, including your filters. Then just send your users the new private link. Note that while revoking a private link will preclude further updates, it won't delete data already synced to subscribers' Google accounts. If you want to make sure existing data is deleted for Google users the next time the subscription refreshes, leave the original calendar active, but edit its filter criteria to yield a null data set (thanks to Ian Blackburn for this tip!).
June 22, 2015, at 03:25 PM by 142.4.217.188 -
Changed line 25 from:
->''' 6.''' To rescind or "unpublish" a private link, just delete that calendar entry from SeedCode_Subscribe_Setup.fmp12. If you want to republish it using a new link, duplicate the calendar first, then delete the original. Duplicating a calendar will clear the log, but everything else will be preserved, including your filters. Then just send your users the new private link.
to:
->''' 6.''' To revoke or "unpublish" a private link, just delete that calendar entry from SeedCode_Subscribe_Setup.fmp12. If you want to republish it using a new link, duplicate the calendar first, then delete the original. Duplicating a calendar will clear the log, but everything else will be preserved, including your filters. Then just send your users the new private link. Note that while revoking a private link will preclude further updates, it won't delete data already synced to subscribers' Google accounts.
April 10, 2015, at 03:34 AM by 142.4.217.188 -
Changed lines 29-31 from:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours" but in our experience it's a good bit less often than that.
to:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours" but in our experience it's a good bit less often than that.

Note that the Private URL uses the Guest login account in the SeedCode_Subscribe_Setup file, so make sure it's active.
January 03, 2014, at 12:35 AM by 76.120.65.113 -
Changed lines 17-23 from:
->''' 2.''' Anyone who gets this private link can use it to see the calendar. Subscriptions that use the private link essentially get their log in credentials from what you entered as a username and password on tab 1: so users aren't asked to log in. Thus be judicious about who you send these links to. Read about [[security | securing this app]] to make sure you have this setup correctly.

->''' 3.''' Don't remove any of the field objects or the "Filters" portal
from the "CalendarsXML" layout in the SeedCode_Subscribe_Setup.fmp12 file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.

->''' 4.''' You can rename SeedCode_Subscribe_Setup.fmp12 if you need or want to (you may need to if you host it on a shared server). Just know that any private URLS you've already distributed would need to be changed to reflect the new name. New URLs take the changed file name automatically.

->''' 5.''' To rescind or "unpublish" a private link, just delete that calendar entry from SeedCode_Subscribe_Setup.fmp12. If you want to republish it using a new link, duplicate the calendar first, then delete the original. Duplicating a calendar will clear the log, but everything else will be preserved, including your filters. Then just send your users the new private link.
to:
-> '''2.''' The Private Link uses the "Guest" account in SeedCode_Subscribe_Setup.fmp12, so that account must remain enabled. The Guest account uses a privilege set called "XML Only", which is set up to only allow access via XML (not FileMaker or PHP). The "XML Only" privilege set has limited access to tables and layouts, primarily gathering its data from the "CalendarXML" layout.

->''' 3.''' Anyone who gets this private link can use it to see the calendar
. Subscriptions that use the private link essentially get their log in credentials from what you entered as a username and password on tab 1: so users aren't asked to log in. Thus be judicious about who you send these links to. Read about [[security | securing this app]] to make sure you have this setup correctly.

->''' 4.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode_Subscribe_Setup.fmp12 file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.

->''' 5.''' You can rename SeedCode_Subscribe_Setup.fmp12 if you need or want to (you may need to if you host it on a shared server). Just know that any private URLs you've already distributed would need to be changed to reflect the new name. New URLs take the changed file name automatically.

->''' 6
.''' To rescind or "unpublish" a private link, just delete that calendar entry from SeedCode_Subscribe_Setup.fmp12. If you want to republish it using a new link, duplicate the calendar first, then delete the original. Duplicating a calendar will clear the log, but everything else will be preserved, including your filters. Then just send your users the new private link.
August 08, 2013, at 11:15 PM by 50.132.84.245 -
Changed lines 9-11 from:
Things to keep in mind when using a private link:

-> '''1.''' The SeedCode_Subscribe_Setup.fmp12 file
and your FileMaker file (the calendar data source) must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder (PHP files) can be on a different server as described [[Remote PHP Deployments | here]].
to:
Once you've copied that private link to your clipboard, head to Google Calendar and click "add by URL" which is an option under "Other calendars".

Things to keep in mind when using a private link and Google Calendar:

-> '''1.''' In order for this to work, the SeedCode_Subscribe_Setup.fmp12 file and your FileMaker file (the calendar data source) must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder (PHP files) can be on a different server as described [[Remote PHP Deployments | here]].

-> That may mean hosting both SeedCode_Subscribe_Setup_DEMO.fmp12 and AppointmentsExample.fmp12 on your FileMaker server if you're playing with our demo files
.
August 08, 2013, at 11:13 PM by 50.132.84.245 -
August 01, 2013, at 12:14 AM by 67.190.87.90 -
Added lines 18-19:

->''' 5.''' To rescind or "unpublish" a private link, just delete that calendar entry from SeedCode_Subscribe_Setup.fmp12. If you want to republish it using a new link, duplicate the calendar first, then delete the original. Duplicating a calendar will clear the log, but everything else will be preserved, including your filters. Then just send your users the new private link.
July 29, 2013, at 02:54 PM by 50.132.84.245 -
Changed lines 5-6 from:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link. The private link is accessible in SeedCode_Subscribe.fmp12 on tab #4, "Results and Sharing":
to:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link. The private link is accessible in SeedCode_Subscribe_Setup.fmp12 on tab #4, "Results and Sharing":
Changed lines 11-12 from:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and your FileMaker file (the calendar data source) must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder (PHP files) can be on a different server as described [[Remote PHP Deployments | here]].
to:
-> '''1.''' The SeedCode_Subscribe_Setup.fmp12 file and your FileMaker file (the calendar data source) must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder (PHP files) can be on a different server as described [[Remote PHP Deployments | here]].
Changed line 15 from:
->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode_Subscribe.fmp12 file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.
to:
->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode_Subscribe_Setup.fmp12 file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.
July 29, 2013, at 02:51 PM by 50.132.84.245 -
Changed line 3 from:
!! Private Links & Hosting SeedCode_Subscribe.fmp12
to:
!! Private Links & Hosting SeedCode_Subscribe_Setup.fmp12
July 29, 2013, at 02:51 PM by 50.132.84.245 -
Added lines 16-17:

->''' 4.''' You can rename SeedCode_Subscribe_Setup.fmp12 if you need or want to (you may need to if you host it on a shared server). Just know that any private URLS you've already distributed would need to be changed to reflect the new name. New URLs take the changed file name automatically.
July 29, 2013, at 02:19 PM by 50.132.84.245 -
Changed line 13 from:
->''' 2.''' Anyone who gets this private link can use it to see the calendar. Subscriptions that use the private link essentially get their log in credentials from what you entered as a username and password on tab 1: so users aren't asked to log in. Thus be judicious about who you send these links to. Read about [[security | securing this app]] for more info.
to:
->''' 2.''' Anyone who gets this private link can use it to see the calendar. Subscriptions that use the private link essentially get their log in credentials from what you entered as a username and password on tab 1: so users aren't asked to log in. Thus be judicious about who you send these links to. Read about [[security | securing this app]] to make sure you have this setup correctly.
July 29, 2013, at 02:08 PM by 50.132.84.245 -
Changed lines 11-12 from:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and your FileMaker file (the calendar data source) must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder (PHP files) can be on a different server. Just edit the configuration.ini file to reflect the FM Server address.
to:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and your FileMaker file (the calendar data source) must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder (PHP files) can be on a different server as described [[Remote PHP Deployments | here]].
Changed lines 15-16 from:
->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode_Subscribe file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.
to:
->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode_Subscribe.fmp12 file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.
Changed line 19 from:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours" but in our experience it's a bit less often than that.
to:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours" but in our experience it's a good bit less often than that.
July 24, 2013, at 02:31 AM by 67.190.87.90 -
Changed line 11 from:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and the FileMaker file that is your calendar data source must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder can be on a different server, as long as the .ini file is edited to reflect the FM Server address.
to:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and your FileMaker file (the calendar data source) must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder (PHP files) can be on a different server. Just edit the configuration.ini file to reflect the FM Server address.
July 24, 2013, at 02:24 AM by 67.190.87.90 -
Changed line 11 from:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and the FileMaker file that is your calendar data source must be hosted on the same FileMaker Server.
to:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and the FileMaker file that is your calendar data source must be hosted on the same FileMaker Server. The seedcode_subscribe_engine folder can be on a different server, as long as the .ini file is edited to reflect the FM Server address.
July 24, 2013, at 02:20 AM by 67.190.87.90 -
Changed line 11 from:
-> '''1.''' The SeedCode_Subscribe.fmp12 file must be hosted on same FileMaker Server as the "seedcode_subscribe" folder.
to:
-> '''1.''' The SeedCode_Subscribe.fmp12 file and the FileMaker file that is your calendar data source must be hosted on the same FileMaker Server.
July 08, 2013, at 11:59 PM by 50.132.84.245 -
Changed lines 13-16 from:
->''' 2.''' Anyone who gets this private link can use it to see the calendar. Subscriptions that use the private link essentially bypass any FileMaker security.

->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator
file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.
to:
->''' 2.''' Anyone who gets this private link can use it to see the calendar. Subscriptions that use the private link essentially get their log in credentials from what you entered as a username and password on tab 1: so users aren't asked to log in. Thus be judicious about who you send these links to. Read about [[security | securing this app]] for more info.

->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode_Subscribe
file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.
July 08, 2013, at 11:56 PM by 50.132.84.245 -
Changed lines 5-6 from:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link. The private link is accessible on tab #4, Results and sharing:
to:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link. The private link is accessible in SeedCode_Subscribe.fmp12 on tab #4, "Results and Sharing":
July 08, 2013, at 11:55 PM by 67.190.87.90 -
Changed lines 5-6 from:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link. The private link is accessible on tab #4, Results & Sharing:
to:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link. The private link is accessible on tab #4, Results and sharing:
July 08, 2013, at 11:15 PM by 67.190.87.90 -
Changed lines 5-6 from:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link.
to:
To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar, you will need to use a special private link. The private link is accessible on tab #4, Results & Sharing:
July 08, 2013, at 11:14 PM by 67.190.87.90 -
Added lines 7-8:
Attach:seedcode_subscribe_private_link.png
July 08, 2013, at 11:11 PM by 67.190.87.90 -
Changed lines 11-12 from:
->''' 2.''' Anyone who gets this private link can use it to see the calendar.
to:
->''' 2.''' Anyone who gets this private link can use it to see the calendar. Subscriptions that use the private link essentially bypass any FileMaker security.
July 08, 2013, at 11:10 PM by 67.190.87.90 -
Changed lines 7-8 from:
Things to keep in mind when using private link:
to:
Things to keep in mind when using a private link:
July 08, 2013, at 06:43 PM by 67.190.87.90 -
Changed lines 3-4 from:
!! Private Links & Hosting SeedCode Subscribe_Creator.fmp12
to:
!! Private Links & Hosting SeedCode_Subscribe.fmp12
Changed lines 9-10 from:
-> '''1.''' The SeedCode Subscribe_Creator file must be hosted on same FileMaker Server as SeedCode Subscribe.
to:
-> '''1.''' The SeedCode_Subscribe.fmp12 file must be hosted on same FileMaker Server as the "seedcode_subscribe" folder.
Changed lines 13-14 from:
->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the PHP files.
to:
->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the .phar file.
June 27, 2013, at 12:16 AM by 67.190.87.90 -
Changed line 17 from:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refres
to:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours" but in our experience it's a bit less often than that.
June 22, 2013, at 04:48 PM by 198.134.91.204 -
Added lines 3-4:
!! Private Links & Hosting SeedCode Subscribe_Creator.fmp12
June 22, 2013, at 04:47 PM by 198.134.91.204 -
Changed lines 7-12 from:
1. The SeedCode Subscribe_Creator file must be hosted on same FileMaker Server as SeedCode Subscribe.

2. Anyone who gets this private link can use it to see the calendar.

3. Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the PHP files.
to:
-> '''1.''' The SeedCode Subscribe_Creator file must be hosted on same FileMaker Server as SeedCode Subscribe.

->''' 2.''' Anyone who gets this private link can use it to see the calendar.

->''' 3.''' Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the PHP files.
Changed line 15 from:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours" but in our experience it's a bit less often than that.
to:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refres
June 22, 2013, at 04:47 PM by 198.134.91.204 -
Changed lines 1-2 from:
To subscribe to calendars that don't authenticate and/or have a URL-length limitation, (most notably Google Calendar), you will need to use a special private link.
to:
(:title Using SeedCode Subscribe with Google Calendar:)

To subscribe in calendar applications that don't support authentication and/or have a URL-length limitation, most notably Google Calendar
, you will need to use a special private link.
Changed lines 7-10 from:
1.The  SeedCode Subscribe_Creator file must be hosted on same machine as SeedCode Subscribe

2
. Anyone who gets this private link can use it to see the calendar
to:
1. The SeedCode Subscribe_Creator file must be hosted on same FileMaker Server as SeedCode Subscribe.

2.
Anyone who gets this private link can use it to see the calendar.
Changed line 15 from:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours".
to:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours" but in our experience it's a bit less often than that.
June 13, 2013, at 09:39 PM by 67.190.87.90 -
Changed line 13 from:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. It appears Google refreshes its calendar subscriptions only once every 24 hours.
to:
Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. Google has stated that they refresh calendar feeds "every few hours".
June 13, 2013, at 09:29 PM by 67.190.87.90 -
Added lines 11-12:
!!Refreshing your Google Calendar
June 13, 2013, at 09:29 PM by 67.190.87.90 -
Changed lines 9-11 from:
3. Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the PHP files.
to:
3. Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the PHP files.

Unfortunately Google doesn't refresh its calendar subscriptions in real time like iCal does, and there's no way to force a refresh of a subscribed calendar in Google. It appears Google refreshes its calendar subscriptions only once every 24 hours
.
June 12, 2013, at 10:02 PM by 67.190.87.90 -
Added lines 1-9:
To subscribe to calendars that don't authenticate and/or have a URL-length limitation, (most notably Google Calendar), you will need to use a special private link.

Things to keep in mind when using private link:

1.The  SeedCode Subscribe_Creator file must be hosted on same machine as SeedCode Subscribe

2. Anyone who gets this private link can use it to see the calendar

3. Don't remove any of the field objects or the "Filters" portal from the "CalendarsXML" layout in the SeedCode Subscribe_Creator file, and don't rename any of those fields. When publishing to Google Calendar, SeedCode Subscribe will look for this layout and these fields based on names that are hard-coded in the PHP files.
(855) SEEDCODE
[email protected]
Follow us: