You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you'd like to have a different event timezone default than the app default (usually UTC), update it via the CP. This is used on individual events that do not have a timezone set (see Fieldset below).
12
11
13
-
The default collection for your events is `events`, if you use a different one, publish the config file and then update it via the CP.
12
+
The default collection for your events is `events`, if you use a different one, update it in the addon settings.
14
13
15
14
For the ICS downloads, it will use `address`, `coordinates`, and `description` fields if they exist. If your field is named something else, use a [Computed Value](https://statamic.dev/computed-values). `coordinates` must be a keyed array:
16
15
```
@@ -74,13 +73,18 @@ days:
74
73
75
74
**Common Parameters**
76
75
77
-
All of the above (except Download Link) have a `site` parameter you can pass the handle of the site to get the events from. It defaults to your default site. **Note**: if you use Livewire you may need to set this from Antlers, using `{site:handle}`
76
+
All of the above (except Download Link) have :
77
+
*`site` - handle of the site to get the events from. It defaults to your default site. **Note**: if you use Livewire you may need to set this from Antlers, using `{site:handle}`
78
+
*`timezone` - all occurrences will be shifted to this timezone
78
79
79
80
**Additional Variables** (normal entry data is available)
80
81
81
-
*`start` - Carbon date/time of the occurrence start
82
-
*`end` - Carbon date/time of the occurrence end. Note if it's an all date event this will be set to 11:59:59pm
83
-
*`has_end_time` - Boolean that indicates if this occurrence has a set end time. In All Day events, this is `false`
82
+
*`start` - Carbon date/time - occurrence start
83
+
*`end` - Carbon date/time - occurrence end. Note if it's an all date event this will be set to 11:59:59pm
84
+
*`has_end_time` - Boolean - `true` if occurrence has a set end time. In All Day events, this is `false`
85
+
*`spanning` - Boolean - `true` if occurrence spans multiple days
86
+
*`spanning_start` - Boolean - `true` if `spanning` and this is the first one
87
+
*`spanning_end` - Boolean - `true` if `spanning` and this is the last one
84
88
* when it is a multi-day event, there is also an array of `days` that contains:
0 commit comments