Advanced cal / partner integration¶

Table of Contents¶

Advanced cal / partner integration 1

`Introduction 3 <#1.1.Introduction|outline>`_

What does it do? 3

Screenshots 3

`Users manual 4 <#1.2.Users%20manual|outline>`_

FAQ 4

`Administration 5 <#1.3.Administration|outline>`_

FAQ 5

`Configuration 6 <#1.4.Configuration|outline>`_

FAQ 6

Reference 6

`Tutorial 7 <#1.5.Tutorial|outline>`_

`Known problems 8 <#1.6.Known%20problems|outline>`_

`To-Do list 9 <#1.7.To-Do%20list|outline>`_

`ChangeLog 10 <#1.8.ChangeLog|outline>`_

Important guidelines 11

`HowTo update a manual to the new layout 12 <#2.1.HowTo%20update%20a %20manual%20to%20the%20new%20layout|outline>`_

`Issues with Open Office documentation for TYPO3 13 <#2.2.Issues%20w ith%20Open%20Office%20documentation%20for%20TYPO3|outline>`_

Inserting images 13

Paragraph styles 13

Linking 14

Meta data and updates 14

Help by documentation.openoffice.org 14

Introduction¶

User/Administration manual¶

Configuration¶

The extension is configured trough constants in the page template. Please see the table below for valid variables and values.

plugin.tx_advcalpartner {
    relationshipTypePids = 1,2
    limitToOrganizations = 1

    limitToLocations =
    includeSubLocations = 0
}

Tutorial/Example¶

Let's assume that we have the following structure that is used within one installation to feed several domains / localized sites from the same data source:

|-> Parish 1
| |-> Region 1_1
| | |-> Building 1_1_1
| | |-> Garden-area 1_1_1_1
| | |-> Garden-area 1_1_1_2
| |
| |-> Region 1_2
| | |-> Building 1_2_1
| | |-> Building 1_2_2
| | |-> Building 1_2_3
| | |-> Garden-area 1_2_1
| |
| |-> Region 1_3
|   |-> Building 1_3_1
|
|-> Parish 2
  |-> Region 2_1
    |-> Building 2_1_1
    | |-> Room 2_1_1_1
    | |-> Room 2_1_1_2
    |
    |-> Building 2_1_2
    |
    |-> Garden-area 2_1_1

Both parish's hold their data together in one Typo3 installation, but data rendering for the public calendars is separated for the web site of Parish 1, the site of Parish 2 and a third (joined) site showing all events.

As the locations of Parish 1 are widely spread, visitors are mainly interested in having an rough overview of what events take place when and where. A month-like preview is used to look 6 weeks ahead in the future (realized by cal_weekpreview); but in addition, there is the need to have dedicated list views for Region 1_1, 1_2 and 1_3. So, the overview pages with week previews get a new marker placed near to the event title: ###ADVCALPARTNER_LOCATION_1### ,the page showing all events from both parishes renders ###ADVCALPARTNER_LOCATION_0### to distinguish both easily, a CSS hover shows some more details by rendering ###ADVCALPARTNER_LOCATION_1### .

This structure itself is modeled with separate partner records, each of type “Organization”. Using them with cal 'as is' adds another problem to editors: The drop down field for location selection is sorted alphabetically, resulting in

Building 1_1_1
Building 1_2_1
Building 1_2_2
Building 1_2_3
Building 1_3_1
Building 2_1_1
Building 2_1_2
Gardenarea 1_1_1_1
Gardenarea 1_1_1_2
Gardenarea 1_2_1
Gardenarea 2_1_1
Parish 1
Parish 2
Region 1_1
Region 1_2
Region 1_3
Region 2_1
Room 2_1_1_1
Room 2_1_1_2

Not really userfriendly...

To-Do list¶

• give users a tree-style input form for easier event creation/editing (planned for release version 0.9)
• limit calendar output to certain locations (planned for release version 2.0)
• improve source code documentation (planned for release version 1.5)

ChangeLog¶

8