Create events

Creating events is not much different from creating content for the other content types in Sitefinity CMS. There are, however, a few specifics, related to the calendar, specifically - the time frame and recurrence of the event.

NOTE: Keep in mind there might some minor differences when creating events, depending on whether you are working in the new content editing experience or in the classic interface. For details, see the Recurring events section in this article.

The following table provides you with details about the event-specific properties you define, apart from the ones common for other content types. For more information, see Create and edit content.

Property

Description

Calendar

Select the calendar that the event belongs to, for example, Conferences.
The dropdown box contains a list of all created calendars. For more information, see Manage event calendars.

NOTE: If you did not create a calendar, different than the default one, all events are automatically associated with the Default calendar.

Event start and event end

Schedule the start and end date and time of the event. You can also create an all-day event. For both types of events, you can specify the event time span, for example, a day or a few days.

NOTE: If your event is recurring, you specify the end date in the Recurring event section.

Time zone

You can select a time zone for the event that is different than the (UTC -12:00) default one. For more information about configuring the default time zone, see Configurations API.
Sitefinity CMS automatically handles daylight saving time.

NOTE: All-day events are always created in the (UTC -12:00) default zone.

Location

Assign a location to the event by entering an address.

Contact information

Provide contact information and details.

Recurring events

When you define the recurrence of an event, you specify whether the event is repeated and if yes – when and how often.

IMPORTANT: Be aware there are some key differences in how you define recurring events in the classic UI and in the new content editing experience. Therefore, we recommend that you edit and publish events created in the classic UI only in the classic UI. Alternatively, you can work with recurring events in the new content editing experience only. Otherwise, errors in the recurrence logic may occur. This is especially the case for more complex recurrences as compared to the standard ones, for example, a simple weekly event.

Say your event’s first occurrence (start date) is Monday, Dec 10. To select the interval of repetition, choose one of the options:

  • Don’t repeat
    You schedule the event in the Event start and event end section.
  • Every day
  • Every workday
  • Weekly on Monday
  • Monthly on 10th
  • Yearly on Dec 10th

 Next, you specify the event’s end occurrence:

  • Never
    Do not end the event.
  • On <date>
    Select a particular date.
  • After <number> occurrences
    A selected number of repetitions.

Define recurring events in the classic UI

In the Repeat event dropdown box, choose one of the following:

None  To schedule the starting and the ending date and time of the event, use the Event start and Event end input fields. 
Daily 
  1. Choose the Start time and the End time of the event.
  2. Under Repeat…, select the interval of repetition.
    • You can enter an interval.
      For example, if you enter 2, the event will be repeated every other day.
    • You can also select to repeat the event every day, except the weekend.
  3. In Event start, select the date of the first occurrence of the event.
  4. In Event end…, you can choose to end the event after:
    • A selected number of repeated.
    • On a particular date.
    • Do not end the event.
Weekly 
  1. Choose the Start time and the End time of the event.
  2. Under Repeat…, select the interval of repetition.
    For example, if you enter 2, the event will be repeated every other week.
  3. Select the weekdays when the event will occur.
  4. In Event start, select the date of the first occurrence of the event.
  5. In Event end…, you can choose to end the event after:
    • A selected number of repeated.
    • On a particular date.
    • Do not end the event.
Monthly 
  1. Choose the Start time and the End time of the event.
  2. Under Repeat…, perform one of the following:
    • Enter the day of the month when the event will occur and enter the interval of repetition.
      For example, if you enter 5 and 2, the event will occur on the fifth date of every other month.
    • Select the week of the month that the event will occur, then select either the exact weekday or select between day, weekday, and weekend day. Enter the interval of repetition.
      For example, you can select the third Monday of every second month.
  3. In Event end…, you can choose to end the event after:
    • A selected number of repeated.
    • On a particular date.
    • Do not end the event.
Yearly 
  1. In Event start, select the date of the first occurrence of the event.
  2. Under Repeat…, perform one of the following:
    • Select the month and enter the day.
      The event will occur annually on this date.
    • Select the week of the month that the event will occur, then select either the exact weekday or select between day, weekday, and weekend day. Select the month.
      For example, you can choose the first Sunday of April.
  3. In Event end…, you can choose to end the event after:
    • A selected number of repeated.
    • On a particular date.
    • Do not end the event.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Web Security for Sitefinity Administrators

The free standalone Web Security lesson teaches administrators how to protect your websites and Sitefinity instance from external threats. Learn to configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?