Schedule Plugin

External requirements: This plugin requires the following additional components that must be installed separately:

• OpenLayersMap
• geophp

Search and install the plugin using the Extension Manager. Refer to Plugins on how to install plugins manually.

See the plugin in action here (fr.) or here (fr.) and some documentation here

Different block are connected. Some popup appears according selection. The maps are interactive…

On a dedicated schedule page:

{{schedule>agenda prop >!}}

On a sidebar:

{{schedule>agenda table >!}}

On a event page

<schedule>
56243 | 47.6177 | -2.7357 | Centre Culturel Grain de Sel \\ 5 ter, rue des écoles \\ 56 860
</schedule>

Schedule by lines:

{{schedule>nameSpace [help] [id="id"] [(<|=|>)(!|+-delta|jj/mm/aa|jj/mm/aaaa)] [#maxLine] [prop|form|ctrl] [(member|what|audience|noMember|noWhat|noAudience)="x1,x2,..."] }}

• nameSpace – name of the schedule. Multiple schedules could be manage in a site
  (by default the nameSpace of the page where the syntax appears)
• help – give a help
• id – to permit many schedule table (with different parameters) on a same page
• <|=|> – filer before, after or same as the indicated date
• ! – today
• +-delta – some days after or before today
• jj/mm/aa|jj/mm/aaaa – specific date
• #maxLine – maximum events
• ctrl – add remove command per event for connected users
• form – ctrl + form to add event for connected users
• prop – form + form to add event for anybody
  messages are send to administrators when new proposal since last acknowledgement.
• member|what|audience – filter according initiator, event or public
• noMember|noWhat|noAudience – exclude some initiator, event or public

A compact representation (table + map):

{{schedule>nameSpace table [(<|=|>)(!|+-delta|jj/mm/aa|jj/mm/aaaa)] }}

• nameSpace – name of the schedule. Multiple schedules could be manage in a site
  (by default the nameSpace of the page where the syntax appears)
• <|=|> – filer before, after or same as the indicated date
• ! – today
• +-delta – some days after or before today
• jj/mm/aa|jj/mm/aaaa – specific date

On a event page to localize the event:

<schedule>
inseeCode | lat | long | name ~br~ street ~br zipCode ~end~
...
</schedule>

One line per plot.

• inseeCode – code give by the French public structure (unique number per city)
• lat and long – gps coordinates
• complete address ends by zip code of the city (not unique for cities in France)
• ~br~ add new line
• ~end~ turn around ckgedit side effect

The user may not have to use this syntax. This part of code is automatically generated with the “wizard” button associated to each new event.

Management:

{{schedule admin }}

Capability to move events form on schedule to an other (archive operations).

• scheduleGroup – user group who can fill the event form without captcha
• adminGroup – admin group who can remove or archive schedules
• dataDir – directory for xml database for events
• groupsDir – nameSpace where members group (sub organization) could be found
• noSchedule – not a member (ignore this directories as a sub organization)
• sharedDir – share nameSpace for common events of different organizations
• scheduleSubDir – root of events pages (contains a directory by organization)
• scheduleWhat – 3 kinds of events (A ⇒ red | B ⇒ orange | C ⇒ green)
• scheduleAudience – different kind of audience
• iconName – icon name looking for in organization directory (square icon is better)
• iconWidth – icon size
• repeatPosition – repeated events are grouped or separated
• bubblePosition – popup of compact representation are shown on left or right

I am trying to set-up this plug-in and I am confused with the dataDir, groupsDir and scheduleSubDir.

• Are they directories or wiki namespace ?
• What should be their actual content ? wiki page or something else ?

An example will help. Thanks — Bruno Généré 2019-09-27 17:45