Need Help?/Calendar

Wrong times displayed in calendar

Sean
posted this on October 5, 2011, 10:12 AM

Updated: Jun 13 2014

new_TripIt_logo_long.png

If your TripIt plans aren't appearing on your calendar at the times you expect, one of a few things may be happening.

Google Calendar

Google Calendar no longer supports floating time zones.

1. In your TripIt settings, under Publishing Your Data make sure you have the setting for Automatically adjust time zones selected.

2. This does mean that your calendar will convert all event times to your current time zone setting. However, if you change your calendar's settings when you travel to reflect the local time zone, these items will show up in the correct time slot once you're in those locations.

Other calendars

1. If you change your calendar's time zone settings when you travel to reflect the local time zone, then be sure to have the setting for Automatically adjust time zones selected.

2. If you don't change your calendar's time zone settings, and always keep your calendar on your home time zone, you can simply ignore time zones for your calendar feed by deselecting the setting for "Automatically adjust time zones."

  • If you change your calendar feed's settings it may take some time for your calendar app to update its cached feed data
  • You can force your calendar's cache to clear by refreshing your feed's URL on your Publishing your TripIt data page (after signing in > User name > Settings > Publishing your Tripit data).  After refreshing, resubscribe to the new URL, wait 15 minutes, and your calendar should be updated.

How to refresh your feed's URL

.Calendar_feed.jpg

Make sure your plans have the right location

When TripIt imports an air, train, or car reservation via the Itinerator, we use the item address to map the location and place it's time zones. If the location or time zones are not correct in nearly all cases you can fix the problem by adding at minimum the city and state or country name.   If you have it, the street addresses is preferable.

 
Topic is closed for comments