Connect with us!
Phone  Email  Twitter  LinkedIn  Feed

Error message

  • Warning: Illegal string offset 'media' in load_subtheme_conditional_styles() (line 426 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: Illegal string offset 'condition' in load_subtheme_conditional_styles() (line 427 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: Illegal string offset 'path' in load_subtheme_conditional_styles() (line 428 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: Illegal string offset 'path' in load_subtheme_conditional_styles() (line 429 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: Illegal string offset 'load_respondjs' in load_polyfills() (line 322 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: Illegal string offset 'load_html5js' in load_polyfills() (line 322 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: Illegal string offset 'load_scalefixjs' in load_polyfills() (line 322 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: Illegal string offset 'load_onmediaqueryjs' in load_polyfills() (line 322 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • Warning: in_array() expects parameter 2 to be array, string given in polly_wants_a_cracker() (line 556 of /home/morris/d7/sites/all/themes/adaptivetheme/at_core/inc/load.inc).
  • User warning: The following module is missing from the file system: commerce_cart. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_checkout. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_customer. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_file. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_line_item. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_order. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_payment. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_price. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_product. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).
  • User warning: The following module is missing from the file system: commerce_tax. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1181 of /home/morris/d7/includes/bootstrap.inc).

Sharing Your Calendar with Non-Daylite Users

Google Calendar

Many Daylite users would like to share their Daylite calendar with non-Daylite users; however, Daylite only provides one mechanism for this: an authenticated, CalDAV feed. Presumably Marketcircle did not provide the older iCalendar (iCal) format for two reasons:

  • It’s not authenticated and as such could be a privacy issue.
  • CalDAV is a more recent standard and the future of iCalendar is uncertain.

Having only an authenticated feed of your calendar is problematic when you want to share it, because the credentials to access the feed are the same as those to log in to Daylite. In addition, services like Google Calendar and Yahoo Calendar, while allowing you to use CalDAV to sync your calendars on the service to other clients, do not allow you to sync information in the other direction. So although you can subscribe to a Google Calendar within Daylite, the reverse is not true.

But by using a go-between like BusyCal [see here for a better option—5/13/2014], it’s possible to channel your Daylite calendar to Google and vice versa. (Unfortunately, I’ve found no other intermediary that works—and it doesn’t work with Yahoo.)

Before I go into the specific steps, I should note that BusyCal 2 lacks the specific feature that makes this possible; you’ll need version 1.6.4 to get this to work.

First, follow my instructions for setting up your Daylite account in CalDAV. Next, connect your Google calendar to BusyCal (Calendar > Connect to Google Calendar…).

The unifying step is only available once you’ve connected your Google calendar: right-click on the Daylite calendar(s) you want to share and select Publish to <name of your Google account>. Now your Daylite calendar will be available in Google and changes made in Google (or BusyCal) will be reflected back in Daylite. (Thanks to theMikeD for pointing this out to me.)

Finally, you can now share your Google/Daylite calendar. You have several options:

  • Select Share from the menu that appears when you hover your cursor over the calendar, then specify the people that can see the calendar and their permissions. This option is for those people who use Google Calendar.

  • Select Calendar settings, then choose ICAL or HTML under Calendar Address. This requires that the calendar be made public (see the Share settings above). ICAL gives you a read-only feed that others can subscribe to in their calendar client, while HTML gives an address they can use to view in a web browser.

Google Calendar settings

  • Select Calendar settings, then choose ICAL under Private Address. This read-only feed is similar to the one above, but doesn’t require that your calendar be made public.

Update: Marketcircle’s Scott Stevenson has some caveats for Google syncing.

Tags: