Lugares y horarios de las reuniones

Location = The place where the club meets.

Schedule = The schedule indicating when the club meets.

Each club can have several locations and several schedules. A schedule always refers to a single location. That is why you must first create the possible location(s) before you can create a schedule.

Locations are typically restaurants or places where the club meets regularly or occasionaly. A web meeting with a constant address can also be considered as a location.

The location of a one-off event should be entered in the event itself.

The schedules include details such as the day of the week and the frequency of regular meetings.

Locations

The schedules and locations are displayed in the footer on the club's home page, including a route planner and a google map. If there are several schedules, the display changes every 4 seconds. If no schedule or location is defined, or if they are not linked together, an empty footer appears.

On the left and right edges of the blue image there are arrows to scroll through the schedules. (Slider)

The name is sufficient for the description of the location, but in order for the map and directions to be displayed, it is necessary to enter the complete postal address.

🔄 Schedules

Schedules define when and with which periodicity the meetings take place.

You must define the day of the week and the periodicity. In addition, you define the start and end time, and the location, as well as some default parameters of the meetings.

If your meetings take place at different times during the week of the month, or if your schedules are different in summer and winter, create several schedules and describe the specific rules in the Description tab of the schedule.

B4bUrmv9P0aXAAAAAElFTkSuQmCC

Generation of dependent events

The deployment of Polaris version R1.04 (August 2024), with its improved event registration functionality, offers four options for managing prices and payments, to make it easier to create an event according to its characteristics and needs.

This diversity of event types has led to the removal of the “Dependent Events” functionality.