Table of Contents 

What Does it Do? 

The SAV Library Plus is the library required to run extension generated by means of the SAV Library Kickstarter when the library type plus is used.

The SAV Library Kickstarter generates extensions without any PHP coding, thanks to simple configuration parameters. It includes:

• Creation of multiple views of the data,
• Frontend input of the data,
• Views with folders,
• Simple interface in the Kickstarter with Context Sensitive Help,
• Generation of emails,
• Generation of RTF files using database tags,
• Data export in CSV format,
• Many other features.

The latest developments of the SAV Library Plus extension are available in GitHub ( SAV Library Plus ).

Related Extensions 

Several examples of extensions generated by the SAV Library are available in the TER.

• SAV Library Examples (sav_library_exampleX, where X is a number) - these extensions are described in the tutorial section.
• Other examples can be found in the Other examples section of this manual: Downloading documents (sav_download), Minutes of meetings (sav_meetings).

The extension sav_filters provides filters to work with the extensions generated for the SAV Library Plus or the SAV Library Mvc.

Screenshots 

The following screenshots come from the SAV Library Examples. The example #X is related with the exentension sav_library_exampleX and is described in the tutorial #X section of this manual.

Example 1 – Creating Text and Image 

List View 

Single View 

Edit View 

Example 2 – Creating Link, Text Area, Selector 

List View 

Single View 

Edit View 

Example 3 – Creating Folders, MM Table in a Subform 

Single View 

Edit View 

Example 4 – Double-Window Selector, Table in a Subform Which is not in Relation With Items 

Single View 

Edit View 

Example 6 – Email and RTF 

Edit View 

Example 7 – Guest Book (Multiple Forms) 

Guest Form (Edit View) 

Guest Inputs Validation (List and Edit Views) 

List View 

Teaser View 

Example 8 – Fe Users Admin and Export 

List View of the ADMIN Form With Export Icon 

Export View Using a Previously Saved Configuration 

Example 9 – XML Graph 

Example10 – Using TypoScript (Gallery With a Map) 

List View 

Single View With a Map 

General Folder 

1. Help: click on the word Help to access to this section of the documentation.
2. Select form: use this selector to select the form name. Let use recall that the sav_library_plus makes it possible to build several forms associated with the same extension, thus providing different views of your tables.
3. Show all if no filter: if set, all items are displayed if no filter is applied, for example by means of the sav_filters extension.
4. If no information available: use the selector to choose what to display when no information are available.
5. Max number of items : maximum number of items that will be displayed in a page. If set to 0, all items are displayed.

Input Controls Folder =====================

1. Help: click on the word Help to access to this section of the documentation.
2. Allow authenticated FE users to input data: if set, frontend inputs are allowed by authenticated users (set by default).
3. Allowed groups: if you select user groups, user must belong to one of these groups to be allowed to input data in the frontend.

4. Input Admin field: put here a field under the form tableName.fieldName (if you use only fieldName, the main table is taken as tableName). This will restrict the input to users that have Admin right for this field in their TSConfig. For example, if one user has extKey_Admin=value1,value2 in his TSConfig, he/she will be allowed to edit or delete items for which fieldName is equal to value1 or value2 for the extension extKey. The fields or the folders which have the attribute editAdminPlus= 1; can be modified if the user has the Admin+ rights. For example, if the TSConfig is extKey_Admin=value1+,value2 , the user is an Admin+ for the records where fieldName is equal to value1 and just Admin for the records where fieldName is equal to value2. Users become Super Admin if their TSConfig is extKey_Admin=\*.

   Note

   Two special entries are also allowed:

   • fe_users.uid: it may be used if the main table is fe_users. In this case, access is granted if the authenticated frontend user uid is the same as the main table uid (see Tutorial 8 for an example).
   • cruser_id or your_main_table.cruserd_id: in this case, the access is granted if the authenticated frontend user has created the current record, i.e. its uid is equal to the cruser_id field in the current record.
5. No “new” button: no new button is added to the form. It means that you can modify existing records but you cannot create new record.
6. No “edit” button: an edit button will not be added in front of the records in List views.
7. No “delete” button: a delete button will not be added in front of the records in List views.
8. Add a “delete” button only for records created by the user : add a delete button only for records created by the user.
9. Input start date: if set, inputs in the frontend will not be possible before this date.
10. Input end date: if set, inputs in the frontend will not be possible after this date.
11. Apply date limit: use the selector to set either Nobody, All, Admin plus users, All excluding Super Admin. The date limit is applied according to this selector.

Advanced Folder 

1. Help: click on the word Help to access to this section of the documentation.
2. Permanent filter: you can use this field to add a WHERE clause part to the WHERE clause of the form query.
3. Add a fragment (# content id) to links: the content id is added as a fragment to the links.
4. SELECT query to allow data to be displayed (if void display is always allowed): the SELECT query entered in this field is used to check if data can be displayed. It the query result is not empty the access is granted. It may be used in very specific cases to protect access to the data. Because it is very specific, for security reasons, only admin users can fill this field when needed.
5. Allow the use of the “query” property: the query property makes it possible to execute queries in Edit or Update views. Because any query may be executed, for security reasons, only admin users can check this field when this property is needed.
6. Allow the use of the exec function in export: The use of the php exec function is allowed in export which makes the execution of text processors possible, for example.

Help Pages Folder 

1. Help: click on the word Help to access to this section of the documentation.
2. Help page for the List view: use this selector to choose a page of your site which will be use as a help page for the List view. In this case, an icon is displayed in the title bar of your extension.
3. Help page for the Single view: use this selector to choose a page of your site which will be use as a help page for the single view. In this case, an icon is displayed in the title bar of your extension.
4. Help page for the Edit view: use this selector to choose a page of your site which will be use as a help page for the edit view. In this case, an icon is displayed in the title bar of your extension.

At the Library Level 

Changes are made in TypoScript and will be applied to all extensions using the SAV Library Plus. The syntax is the following:

plugin.tx_savlibraryplus.iconRootPath = yourIconRootPath
plugin.tx_savlibraryplus.imageRootPath = yourImageRootPath

At the Extension Level 

There are two different ways of changing the icon or images root paths.

1. Create a Resources/Public/Icons (resp. Resources/Public/Images) directory in the generated extension in which you put your icon files with the same names as in the default directory Resources/Public/Icons (resp. Resources/Public/Images) in the extension sav_library_plus.
2. Create a directory where you want in the fileadmin directory, in which you put your icon files with the same names as in the default directory. Then, in the Setup of your template, write:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.iconRootPath = yourIconRootPath
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.iconImagePath = yourImageRootPath

where yourExtensionNameWithoutUnderscores is the key of the extension you have created with the SAV Library Kickstarter, but without underscores if any, and yourIconRootPath (resp. yourImageRootPath)is the relative path of the directory where you have put your icons (resp. images).

You may also want to apply the changes only for one form in one specific extension. The syntax becomes:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.iconRootPath = yourIconRootPath
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.iconImagePath = yourImageRootPath

At the Library Level 

Changes are made in TypoScript and will be applied to all extensions using the SAV Library Plus. The syntax is the following for the template, layout and partial root paths:

plugin.tx_savlibraryplus.templateRootPath = yourTemplateRootPath
plugin.tx_savlibraryplus.layoutRootPath = yourLayoutRootPath
plugin.tx_savlibraryplus.partialRootPath = yourPartialRootPath

The default partials directory Resources/Private/Partials contains the defaut title bars and footers respectively in TitleBars and Footers sub-directories. If you use your own partials, your destination directory must have the same organization and must contain the same files as in the default partials directories. It may happen that you want to change only the title bar or the footer for one type of view, for example the EditView as in Tutorial 8. The syntax is the following where viewType is either listView, singleView or editView:

plugin.tx_savlibraryplus.viewType.partialRootPath = yourPartialRootPath

In that case your partials directory needs only to contain the partials for the title bar and the footer of the given view (see sav_library_example8).

At the Extension Level 

Changes are made in TypoScript and will be applied to one specific extension. The syntax is the following:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.templateRootPath = yourTemplateRootPath
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.layoutRootPath = yourLayoutRootPath
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.partialRootPath = yourPartialRootPath

You may also want to apply the changes only for one form in one specific extension. The syntax becomes:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.templateRootPath = yourTemplateRootPath
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.layoutRootPath = yourLayoutRootPath
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.partialRootPath = yourPartialRootPath

To change the partial root path for a specific view type, please use:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.viewType.partialRootPath = yourPartialRootPath
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.viewType.partialRootPath = yourPartialRootPath

At the Page Level 

Changes are made by means of the Page TSConfig. The syntax is the following:

tx_yourExtensionNameWithoutUnderscores_pi1.formName.templateRootPath = yourTemplateRootPath
tx_yourExtensionNameWithoutUnderscores_pi1.formName.layoutRootPath = yourLayoutRootPath
tx_yourExtensionNameWithoutUnderscores_pi1.formName.partialRootPath = yourPartialRootPath

To change the partial root path for a specific view type, please use:

tx_yourExtensionNameWithoutUnderscores_pi1.formName.viewType.partialRootPath = yourPartialRootPath

At the Extension Level 

The configuration of any field can be changed at the extension level by TypoScript. The syntax is the following:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.viewType.fields[.tableName].fieldName.fieldProperty = propertyValue

For example, assume that one wants to change the width and the height of the image in the List view in the Tutorial1.

• The tx_yourExtensionNameWithoutUnderscores_pi1 is tx_savlibraryexample1_pi1,
• the formName is Contact,
• the viewType is listView (use singleView, editView for the other types),
• the tableName is the table in which the field fieldName is. It can be omitted if the field is in the main table.
• the fieldName is image,
• the fieldProperty is width or height.

It leads to the following configuration:

plugin.tx_savlibraryexample1_pi1.Contact.listView.fields.image.width = 200
plugin.tx_savlibraryexample1_pi1.Contact.listView.fields.image.height = 200

At the Page Level 

The configuration of any field can be changed at the extension level by means of the page TypoScript Config. The syntax is the following:

tx_yourExtensionNameWithoutUnderscores.formName.viewType.fields[.tableName].fieldName.fieldProperty = propertyValue

Using the same example as above, it leads to:

tx_savlibraryexample1.Contact.listView.fields.image.width = 200
tx_savlibraryexample1.Contact.listView.fields.image.height = 200

Style Sheet 

There are several style sheets provided with the date picker. The default CSS is calendar-win2k-2.css. You can change the default CSS at the extension level or library level by using the following TypoScript configuration:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1. datePicker.stylesheet = yourFormat
plugin.tx_savlibraryplus.datePicker.stylesheet = yourStyleSheet

For example:

plugin.tx_savlibraryplus.datePicker.stylesheet = EXT:sav_library_plus/Classes/DatePicker/css/calendar-tas.css

Tooltip and Title Bar Formats 

The date format of the tooltip (footer bar of the date picker) or the title bar can be changed at the extension or library level by the following TypoScript configuration:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.datePicker.format.toolTipDate = yourFormat
plugin.tx_savlibraryplus.datePicker.format.toolTipDate =  yourFormat

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.datePicker.format.titleBarDate = yourFormat
plugin.tx_savlibraryplus.datePicker.format.titleBarDate =  yourFormat

Default values for the title bar is %B, %Y and depends on the language for the tool tip (see the variable Calendar._TT[“TT_DATE_FORMAT”] in files in the directory Classes/DatePicker/lang).

At the Library Level 

Parameters are added in TypoScript and will be applied to all extensions using the SAV Library Plus. The syntax is the following:

plugin.tx_savlibraryplus.link.additionalParams = &param1=1&param2=3

It may happen that you want to add parameters for one type of view:

plugin.tx_savlibraryplus.viewType.link.additionalParams = &param1=1&param2=3

At the Extension Level 

Parameters are added in TypoScript and will be applied to one specific extension. The syntax is the following:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.link.additionalParams = &param1=1&param2=3

You may also want to apply the parameters only for one form in one specific extension. The syntax becomes:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.link.additionalParams = &param1=1&param2=3

To add parameters to a specific view type, please use:

plugin.tx_yourExtensionNameWithoutUnderscores_pi1.viewType.link.additionalParams = &param1=1&param2=3
plugin.tx_yourExtensionNameWithoutUnderscores_pi1.formName.viewType.link.additionalParams = &param1=1&param2=3

At the Page Level 

Parameters are added by means of the Page TSConfig. The syntax is the following:

tx_yourExtensionNameWithoutUnderscores_pi1.formName.link.additionalParams = &param1=1&param2=3

To add parameters to a specific view type, please use:

tx_yourExtensionNameWithoutUnderscores_pi1.formName.viewType.link.additionalParams = &param1=1&param2=3

Table of Contents 

Extension Configuration 

Views 

This extension relies on three views:

• A List view which displays all the items associated with the query,
• A Single view which displays only information associated with one item,
• An Edit view which makes it possible to edit an item in the frontend.

Let us note that most extensions deal with one form with three views: one view to list the items, one view to display an item and one view to edit an item. However, an extension may only have one List view. It can also contain several forms with different views as it is explained in Tutorial 7. Click on the List view to open it.

The item template defines how each item will be displayed. In general, it is an <ul> list with <li> elements which contain the fields to display. Fields must be written as markers ###fieldname###.

Click on the help icon to get more information.

Then, click on the Single and Edit views where no specific configurations are required.

Queries 

Each form has an associated query to select the items that will be displayed in the List view. Use the Context Sensitive Help icon to get the description associated with each field.

Forms 

The Form section is the place where the forms are specified, i.e. the views and the query are selected. Use the Context Sensitive Help icon to get the description associated with each field.

Field Configuration 

A specific configuration can be provided for each field in each view. Configuration are available in the database table. Click on the data base table. Three tabs associated with your three views have been generated. By clicking on a tab, then on a field you will see the configuration parameters of all the field for the selected view. The Context Sensitive Help icon provides on line information about the allowed attribute for the field type (see also the SAV Library Kickstarter Reference for the description of the attributes).

How to Specify the Size of the Image? 

The image is displayed in the List and Single views. The following configuration parameters define a 50x50 image, for example in the List view:

width = 50;
height = 50;

How to Change the Number of Items Displayed by Page in the List View? 

By default, the Max number of items in the flexform is set to 10, just change this number. Setting this number to 0 will display all items. Using the default configuration, you will get:

Now, if you set Max number of item to 2, you will obtain:

How to Introduce an Alphabetic Selector? 

It is often useful to select records based on, for example, the first letter of the name. The extension sav_filters was specially built to deal with this problem.

• Download sav_filters from the TER, read the documentation and install it.
• Add the plugin sav_filters as a content element in the same page as the extension sav_library_example1.
• Configure the flexform by filling the table name and the field name. A Context Sensitive Help is available.

• Save your configuration and go in the frontend.

Only the letters corresponding to the first letter of existing records can be selected. Click on a letter to select the records.

Table of Contents 

How to Display a Title in the Upper Icon Bar of the View? 

A title can be associated with each view. It is defined in the `Title bar` section of the views. Text, language markers or field markers can be used.

For example, if you use $$$formTitle$$$ in the Title bar field, this language marker will be replaced by its definition in the locallang.xlf file. In this example, formTitle is defined as `CD Collection`` for the default language and ``Liste de CD` for the French language. Therefore, the output becomes:

Now, if you use ###artist### - ###album_title### in the Title bar section of the Single and Edit views, the markers ###artist### and ###album_title### will be replaced by the respective values of the field artist and album_title for the current record. If these markers are used in the Title bar section of the List view, they will be replaced by the label associated with the fields. Thus, the output is the following for the Single view:

How to Display the Labels Associated With Each Field in the Title Bar? 

As explain above, field markers used in List view are replaced by the label associated with the fields. Therefore, if the Title bar section is the following:

<ul>
   <li class="artist">###artist###</li>
   <li class="title">###album_title###</li>
   <li class="date">###date_of_purchase###</li>
   <li class="category">###category###</li>
   <li class="image">###coverimage###</li>
</ul>

The title bar becomes:

How to Change the Order of the Item List by Clicking on the Label in the Title Bar? 

For example, assume that we want to change the displayed order by clicking on Artist (or Artiste if you use the french language).

• Add the following configuration parameter in the artist field of the List view.

orderLinkInTitle = 1;

• Add the following configuration in the WHERE Tags section of your query. Click on the plus icon to add an entry.

In this configuration, use filedname+ or fieldname- and associate the order clause you want. In general + can be used for the ascending order and - for the descending order.

By default, the displayed link will behave as a toogle between the ascending and the descending sort. However you can control the display using the property orderLinkInTitleSetup which introduces links associated with icons. For example, using `orderLinkInTitleSetup = :value:ascdesc;`` or ``orderLinkInTitleSetup = asc:value:desc;` will respectively provide the following outputs:

Of course, you may keep the toggle link by writing respectively orderLinkInTitleSetup = :link:ascdesc; or orderLinkInTitleSetup = asc:link:desc;.

The icon color will change depending on the sort order as shown below. In the following caption, the descending order is displayed.

How to Reorganize the Fields with Folders? 

Folders may be introduced in the Single and Edit views to provide a better organization of the information. Click on the plus icon to add a folder.

In this example, two folders are defined. If the labels General and Comments are defined in the locallang.xlf file, they will be replaced by their definition in the selected language, otherwise they are used as it. Then, set a folder to each selected field of the `CD Collection`` table for the ``Single` view as shown below, save and generate the extension:

If you set all the fields to the folder General except the field description which is set to Comments, the following views are obtained in the frontend where the folder General and Comments have a French translation in locallang.xlf.

Table of Contents 

MM Table 

Now, let us assume that you want to lend your CD to your friends. Well, even with friends it is useful to keep trace of your CD! One solution is to build a new table which will be in a MM-relation with your main table. One CD can have been borrowed by several friends.

In this table tx_savlibraryexample3_lending, the name of each friend is kept as well as its phone number, its email, the lending date and the return date. All the lending operation will be displayed in a folder Lendings (Prêts in French).

A field rel_lending was created by means of the SAV Library Kickstarter in the tx_savlibraryexample3_cds as a relation n:n with the table tx_savlibraryexample3_lending.

• cutLabel = 1; means that the label of this field will not be displayed (it is just a personal choice !)
• maxSubItems = 5; overrides the Max number of relations value (it is also a personal choice !)

In the Edit view, almost the same configuration is used. The attribute addDelete will add a delete icon in front of each item in the sub-form so that you can delete them.

Let us recall that the Context Sensitive Help provides information on the attributes that can be used. In following captions, three different attributes are used:

• noDefault = 1; is an attribute for Date type fields. It means that no default value, i.e. the current date, will be displayed when a new item is created.
• fusion = begin; and fusion = end; are General attributes which can be used almost with every fields. fusion = begin; starts the process of writing fields consequently on the same line, while `fusion = end;` stops the process.
• func = makeEmailLink; belongs to Functions attributes, they can also be used almost with every fields for which it makes sense to apply thy function. It will generate an email link the current value of the field.

Queries 

A GROUP BY clause is needed in the Query to display only one item per CD in the List view. If this clause is not added, we get as many repeated outputs for same item as the number of sub-items associated with it (the reason is that SAV Library Plus extension generates left join relations between the tables).

Table of Contents 

New Relations 

A new table tx_savlibraryexample4_friends was created with four fields: friend_name, friend_phone, friend_email as string inputs and friend_preferred_music as a database relation. In this example, it is clear that your friends are not associated with one CD. They should be in the table but with no relation with the CD item. We need a new input in the table tx_savlibraryexample4_cds, such that you will be able to add your friends in an element browser as shown in Example 3, `but without creating a relation field in the table` .

This is done by selecting `Just create the Element Browser (no relation)` as shown in the caption below.

As we want to select only our friends, a where clause is added to the field which will select the records. They must have the correct cruser_id in the tx_savlibraryexample4_friends table.

Let us assume that we want to select our friend's preferred music styles from a double-window selector. Since our friends may have several preferred styles, we have to build a MM relation. In this example, we have chosen to use a non-true MM relation, that is no MM table is built and, instead, TYPO3 uses a comma-separated list. If you prefer to use a true MM relation just select the checkbox.

Table of Contents 

Attributes in the Single View 

The Single view contains the call to the hook in the field hook_content defined as Only shown in SAV form. The attributes must define the hook name and the hook parameters.

The hook name is defined by means of the hookName property.

hookName = SavLibraryExample5;

The hook parameters are defined by the hookParameters property as a JSON array.

hookParameters = {
  "template": "Test.html",
  "uid": "###uidMainTable###"
};

Configuration of the Hook in the File ext_localconf.php =======================================================

The class to be called is set in the variable $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['sav_library_plus']['hooks']['YourHookName'] in the file ext_localconf.php file.

// Adds a hook for SAV Library Plus
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['sav_library_plus']['hooks']['SavLibraryExample5'] = \YolfTypo3\SavLibraryExample5\Hooks\SavLibraryPlus::class;

In this example, the class \YolfTypo3\SavLibraryExample5\Hooks\SavLibraryPlus is in the file typo3conf/sav_library_example5/Classes/Hooks/SavLibraryPlus.php.

Rendering the Hook 

The class \YolfTypo3\SavLibraryExample5\Hooks\SavLibraryPlus extends the class \YolfTypo3\SavLibraryPlus\Hooks\AbstractHook. The method renderHook($parameters) is called to render the hook.

In this example, this method creates a template view, whose name is provided by the hook parameter template and fetches the current record associayed with the Single view.

/**
 * Renders the hook
 *
 * @param array $parameters
 *
 * @return string
 */
public function renderHook($parameters)
{
    // Gets the parameters
    $template = $parameters['template'];
    $uid = $parameters['uid'];

    // Creates a view for more fluid processings of the template
    /** @var StandaloneView $view */
    $view = GeneralUtility::makeInstance(StandaloneView::class);
    $view->setTemplatePathAndFilename('EXT:sav_library_example5/Resources/Private/Templates/' . $template);

    // Selects the record
    $queryBuilder = GeneralUtility::makeInstance(ConnectionPool::class)->getQueryBuilderForTable('tx_savlibraryexample5');
    $rows = $queryBuilder->select('*')
        ->from('tx_savlibraryexample5')
        ->where($queryBuilder->expr()
        ->eq('uid', $queryBuilder->createNamedParameter($uid, \PDO::PARAM_INT)))
        ->executeQuery()
        ->fetchAllAssociative();

    // Assigns the row variable
    $view->assign('row', $rows[0]);

    // Renders the content
    $content = $view->render();

    return $content;
}

The FLUID template is in the folder Resources/Private/Templates of the extension. It compares the values of the field and displays them in the ascending order.

<div class="hookHeader">
    <f:translate key="message" extensionName="sav_library_example5" />
</div>
<ul class="hookList">
    <f:if condition="{row.field1} < {row.field2}">
        <f:then>
            <li>{row.field1}</li>
            <li>{row.field2}</li>
        </f:then>
        <f:else>
            <li>{row.field2}</li>
            <li>{row.field1}</li>
        </f:else>
    </f:if>
</ul>

Table of Contents 

Installation 

Download this example from the TER (sav_library_example6).

1. Install the extension,
2. Copy the file invoice.rtf, which is in the extension directory, in the fileadmin directory,

3. Add the following line in the field TSconfig of the page where you have installed the extension. It will overload the email sender defined in the extension as it will be described in the configuration section.

   tx_savlibraryexample6.View1.editView.fields.email_flag.mailSender
   = your_email@your_provider

   Copied!

Using the Extension 

Use the input form to enter a conference participant as in the following caption.

Then select the email language (default or French) and click on the email icon. If the email is correct, the form will slightly change as shown below. You cannot click on the email icon anymore (if you need to re-send the email, cancel the checkbox at the right hand side of the email icon and save the form).

You should have received an email as the one below:

Dear Yolf,

Thank you for your registration to the conference.

Your registration includes:

√ Conference

- Proceedings

- Meals

√ Banquet


Your invoice will be available at the registration desk.

Looking forwards to seeing you.

Best regards,

The conference organization committee.

To generate the RTF file, click on the icon associated with the invoice, then open the generated file by clicking on the link and print it (the fields are automatically updated).

Field email_flag 

The field email_flag is associated with the email generation. Let us analyze its configuration shown below. Do not forget to use the Context Sensitive Help to get information about the field type attributes and to click on the sav_library_plus / general attributes.

• fusion = begin;. This attribute is used with fusion = end; in the field email_language to have both fields aligned.
• mail = 1;. It tells that an email is associated with the field.
• fieldForCheckMail = email;. The email will be sent only if the field email is not null.
• mailSender = conference.organization@example.com;. This attribute defines the email sender. You can change it with your email and remove the line you have added in the TSconfig of the page.
• mailSubject = $$$mailSubject$$$;. It defines the mail subject. Since $$$tag$$$ is used, it means that localization is used. Therefore, the mail subject is defined in the file locallang.xlf in the extension directory Resources/Private/Language. Open this file in your favorite editor and check the xml tag <trans-unit id="mailSubject" xml:space="preserve">.
• mailMessage = $$$mailMessage$$$;. This attribute is the same as the previous one for the message to be sent. As you can check in the file locallang.xlf, the xml tag <trans-unit id="mailMessage" xml:space="preserve"> contains ###fieldName### markers that were replaced by their values in the received message.
• mailMessageLanguageFromField = email_language;. This attribute indicates that the language for the mail is provided by the value of the field email_language.

This is one of the possibilities for sending emails. See the Context Sensitive Help to see how to send emails each time you save the form (mailAlways) or when data have changed (mailAuto).

Field email_language 

Nothing special about this field. It contains only:

• fusion = end;. It closes the fusion, thus the next field will be on the next line.

Field invoice 

This field is used to generate the RTF file. Its configuration is:

• generateRTF = 1;. It tells that RTF should be generated.
• templateRTF = fileadmin/invoice.rtf;. It defines the template file for the generation. To use this configuration, you must copy the file invoice.rtf located in Resources/Private/Templates; into fileadmin. This file contains markers ###tableName.fieldName### that will be replaced by their value for the current row. You may also change the configuration into templateRTF = EXT:sav_library_example6/Resources/Private/Templates/invoice.rtf; to use directly the template file.
• saveFileRTF = fileadmin/###tx_savlibraryexample6.name###.rtf;. This attribute defines the name under which the RTF file will be saved. Since a marker is used in this attribute, it will be replaced by its value for the current row. In this example, the value of the field name is Yolf, therefore, the file name will be Yolf.rtf.

Table of Contents 

The Guest Input Form (FORM) 

Click on FORM in the Forms section. As you can see, the form has a List view, a special view and a query.

The special view, named FORM_Update is used to generate the guest input form. The List view is used to validate the data in the administration mode. Now, let us analyze each view.

The View FORM_Update 

Click on FORM_Update in the Form views section.

The view is of type Special and of sub-type Form view. The `Item template` field defines the template. In our case, two <div> are used for having two columns in the form. The SAV Library provides some help to easily implement the view. $$$label[fiedname]$$$ will be replaced by the field title, depending on the localization, while ###field[fieldname]### will be replaced by the input item associated with the type of the field. The CSS classes field and label are defined in the default CSS of the SAV Library Plus extension. You may overload their properties in your CSS file. Finally, ###button[submit]### creates the submit button.

Now, we will analyse the configuration. Click on `SAV Example7 – Guest book`` in the section ``New tables``, select the ``FORM_Update` folder tab and click on message, for example.

As it can be seen, the configuration is simple since only three attributes are used:

• addEdit = 1; means that the field can be edited by the guest, that is it will be displayed in the edit mode for the defined type. For the above example, a textarea is displayed.
• required = 1; means that the guest will have to fill the field.
• checkedInUpdateformAdmin = 1; means that the field will be pre- checked for the validation in the Admin form as explained in the next section.

For example, with the above configuration and the provided CSS file, once installed, you should have the following result. Required fields appear with the \* character.

And, thanks to the localization markers $$$label[fieldname]$$$, if you change to the French language, you will get:

The View FORM_All 

When a Form view is used, information provided by the guest are not directly saved in the table fields. A temporary field, named _submitted_data_ is automatically added to the table. It used to keep the guest inputs until you have validated them. For that, the Form view includes an Admin mode in which you have to enter by means of an associated List view which will display the new inputs. Since we will use a filter which requests the email of the guest input, it will be used in the view to switch to the Admin mode.

Localization marker $$$adminTitle$$$ is used to the view title bar. Let us recall that the marker is defined in the file locallang.xlf in the Resources/Private/Language directory of the extension. The template is very simple and contains only the email field which is selected in the configuration.

Two attributes are associated with the field email:

• func = makeItemlink;, already seen in the previous examples, which creates the link associated to the field value.
• updateForm = 1; specifies that the updateform should be opened.

Once correctly installed, if a guest, e.g. paul.durand@example.com has left a new message, you should have the following output:

Now, by clicking on the link, you will enter in the Admin mode. As can be seen, the fields have a checkbox already checked. It is due to the property checkedInUpdateformAdmin = 1; set in the Update view. Only fields that are checked will be transferred to their respective place in the table when submitting the form.

The Query FORM_Query 

In order to get only the guest inputs that have not been checked and processed, a special WHERE clause has to be used.

As explained before, the guest entry is not directly saved in the table fields. Information are serialized and temporary saved in the field _submitted_data_. Therefore, to check that new entries are present, the WHERE clause checks a substring in the _submitted_data_ field. The substring is: extensionName_formName in lower case . When data are processed, the field _validated_ is automatically set. Thus, the WHERE clause will return new entries that have not been processed.

In our example, the extensionName is sav_library_example7 and the formName is FORM, thus the substring to fetch is: sav_library_example7_form.

The Guest Input List (LIST) 

Nothing very special here. The form LIST includes a conventional List view (LIST_all). Analyze the view, the query and the field configurations (use the Context Sensitive Help if necessary). Below are two useful comments.

addLeftIfNotNull = <strong>$$$label[comment]$$$</strong><br />;
cutIfNull = 1;

Field date 

This field has a special type Only shown in SAV form. It means that it will not be present in the table but you may use it as marker ###date### in forms. It has one attribute:

• alias = crdate; means that this field is an alias for the field crdate that already exists in the table (it is created by the Kickstarter).

Below is the screen shot obtained for the LIST form when the extension is correctly installed.

The teaser (TEASER) 

The form TEASER includes a conventional List view (TEASER_All). Analyze the view, the query and the field configurations (use the Context Sensitive Help if necessary). The only specific configuration concerns the field message. We want to have it cropped to 60 characters and have a more link right to the text to go to the page where the LIST form is.

• stdWrapValue =crop = 60\|...; defines a conventional TypoScript stdWrap property. You can add here full TypoScript syntax. Do not forget that the configuration field is ended by a semi-column, therefore if you need a semi-column in your TS, write it \\;.
• addRightIfNotNull = $$$more$$$; adds the label to the right hand site of the content if it is not null. The localization marker $$$more$$$ is used and will be replaced by its value in Resources/Private/Language/locallang.xlf.
• funcRight = makeLink; applies the internal function makeLink, which creates an internal link, to the right hand side part, that is to the more link.
• setUidRight = 123; defines the page uid associated with the link. The value 123 is just for example, you can either replace it by your page uid or overload it using the TypoScrit pageConfig as explained in the configuration section Changing the Field Configuration.

If the extension is correctly installed, you should get:

Installation 

1. Download the extension sav_library_example7 from the TER and install it.
2. Download the extension sav_filters from the TER and install it.
3. Download the extension sr_freecap from the TER and install it.

Guest Input 

• Create a page for the guest input.
• In this page, insert a plugin content. Select `SAV Example7 – Guest book``, select ``FORM`` in the ``General`` folder, then in the ``Input Controls`` folder, uncheck ``Allow authenticated FE users to input data`.

• In the same page, before the previous plugin , add a new plugin content. Select SAV Filters. Fill the fields as shown below. Replace your_email@example.com by a valid email. The value in Uid for the field cruser_id will be the default value for the cruser_id field of each record in the table tx_savlibrary_example7_guests. For example, put your frontend user uid. Provide a key which will be used to crypt the link. Finally provide a redirection page for errors ( this field is required ). When using captcha, you can set this field with the current page.

• Save and go to the page in the frontend. Answer to the captcha and submit.

• Fill the field with your email and submit.

• An information message is displayed and you should received an email with a personal link.

Click on the following link to access to the service
Guest input
This link is valid only for one request. 

The link is Your_page_title (Guest input is the page title used for the tutorial). Click on the link to access to the input form, fill the form and submit it.

Guest Input Validation 

• Create a frontend group, for example savlibrary_test. It will be use to protect the page and define the Admin group. Apply this group to you, that is to your frontend user record.
• Create a page for the guest input validation. Protect the page with the frontend group.
• Insert a plugin content. Select SAV Example7 – Guest book, select FORM in the General folder. In the Input Controls folder, uncheck input on form and add the frontend Group to the Allowed groups field.

• Save and go to the page in the frontend and click on the email associated with your last input.

List View 

• Insert a plugin content. Select SAV Example7 – Guest book, select LIST in the General folder. Set the field Max number of items to the number of items you want in the list (10 is the default). Uncheck Allow authenticated FE users to input data in the Input Controls folder. Save and go to the page in the frontend.

Teaser View 

• Insert a plugin content. Select SAV Example7 – Guest book, select TEASER in the General folder. Set the field Max number of items to the number of items you want in the teaser. Uncheck `Allow authenticated FE users to input data`` in the ``Input Controls` folder.

• If you have not changed the value of setUidRight, edit the page property. In the page TSConfig add:

  tx_savlibraryexample7.TEASER.listView.fields.message.setUidRight
  =  *uid_of_the_page_containing_the_list_form*

  Copied!
• Go to the page in the frontend.

Table of Contents 

The User Form (USER) 

In this example, it was chosen to design a very simple form consisting in the display of the user image field. The image is associated with a link to open the user form in the edit mode.

The Query USER_Query 

The query is used to filter the fe_users table with the authenticated user. This is easily done by using the marker ###user### in the WHERE clause of the query.

The Views USER_List and USER_Edit 

The template associated with these views is quite simple since the only field to display is image.

And to make it possible to generate the link to open the input view, only a few configuration attributes are required.

• func = makeItemLink; generates the link for the current item.
• edit = 1; opens the edit view instead of the default view (Single view).
• width = 50; and height = 50; define the size of the image.

Because there is no Single view associated with the user form, the default Edit view title bar must be changed, in particular the `save and show`` and the ``show button` must be removed. The example comes a directory Resources/Private/Partials which contains two directories TitleBars and Footers. They respectively contain a folder EditView which contain themselves a new default.html Fluid file. We will see later how to call these new Partials.

Finally, to override the default css, the example comes with a css file sav_library_example8.css in the Resources/Public/Css directory which contains the following instructions :

.sav_library_example8_user .savLibraryPlus .listView {width:62px;background-color:#ffffff;}
.sav_library_example8_user .savLibraryPlus .listView .titleBar {display:none;}
.sav_library_example8_user .savLibraryPlus .listView .items .item {border:none;background-color:#ffffff;}

Concerning the view USER_edit, each field with the tyep Only shown in SAV Form (ShowOnly fields) has the property updateShowOnlyField set to 1. By default in ShowOnly fields are not created nor can be updated. Setting this property to 1 overrides the default behavior.

The Administration Form (ADMIN) 

The administration form is used in the frontend to manage, give rights, export frontend users. It is based on a conventional query, List, Single and Edit views for which no specific configuration is needed. Just click on the different views and tabs to see how fields are grouped.

Installation 

The following installation is just an example for testing the extension.

• Download the extension sav_library_example8 from the TER and install it.
• Create a folder for the frontend users.
• In the folder, create a frontend group for regular users and a frontend group for admin users.
• In the folder, create a regular user and an admin user for the test.

• Create a test page for the USER form and another for the ADMIN form.

• In the USER page, insert the plugin and select the USER form.

• Click on the folder Input controls. Select `Allow authenticated FE users to input data`. Enter fe_users.uid in the Input Admin Field. Select No "new" button, No "edit" button, "No delete button and save.

• Edit the Page Properties and add the following configuration in the field Page TSconfig in the folder Resources. It will change the Partials root path to the Partials directory provided with this extension.

tx_savlibraryexample8.USER.editView.partialRootPath = EXT:sav_library_example8/Resources/Private/Partials

• Authenticate the user and go to the USER page. You should see either the user's image or a question mark image if no input was provided (default image).
• Click on the image link to open the edit view. As it can been seen, the new title bar has been taken into account and only Save and Close buttons are displayed.

• In the ADMIN page, insert the plugin, select the ADMIN form and include the user folder in the Record Storage Page field.

• Click on the folder Input controls. Select `Allow authenticated FE users to input data to allow the input. Add your administration group (here ``admin``) in Allowed group``. Select ``No new button` if you do not want to allow the creation of new users.

• Authenticate the administration user and go to the ADMIN page. The view displays the users'name, their email, their phone number and their groups. The behavior of the form is the same as in the previous examples. Click on the name to see the user's configuration. Use the edit icon to modify the fields.

Exporting Data to CSV Format 

Exporting data is possible for any form built with the SAV Library Generator. To allow this feature you simply have to add the following line in the field SAV Library Plus Configuration in the user configuration:

sav_library_example8_Export = *

In general, it is done in the Back End. However, our extension makes it possible to do it in the frontend for the user as shown below.

Now, close the view and verify that you obtain a new CSV icon in the ADMIN List view and click on it to obtain the export view.

The configuration can be used to save, load, delete an export configuration. Use the toogle button to display only selected fields or to display all fields.

XML and XSLT files can be used to export data to other formats (see next section).

Checkboxes are used to select the fields to be exported. If the first checkbox is selected, the raw data are displayed, that is the content of the field in the data base. If the second one is selected, a rendering is done. The field is displayed as it would have been in a Single view.

The Where clause field is used to filter the data to be exported. Let us note that if you double-click on a field name, it will be added in the Where clause field. It is useful to avoid mistakes.

The Order clause field is used to order the data to export.

Additional tables can be used for more complex export where you need to link data used by the extension to data in other tables. In that case do not forget to add a condition in the Where clause to join correctly the tables.

Export MM records can be set when your extension use MM tables and you want to export all data. In that case you may also need to add a Group by clause.

Include all fields can be used when you want to export fields like uid, pid, crdate, ... which are hidden by default. Click on the red CSV icon to include all the fields. Use the toogle button if you have previously restricted the display to selected fields.

Export field names can be selected when you want to have the field names as the first line in the CSV file.

Order of the fields can be used to change the order in which the fields are extracted. By default, it is the order in which the appear in the checkbox list from left to right. In the above example, without information in this field, fe_users.username comes first, then fe_users.usergroup is extracted, then fe_users.name and so on. Provide a list of fields separated by a semi-column (one field per line makes it simple to read) in the text area to change this order. Let us also note that you can put the same field several time, which is sometimes useful when you process directly the CSV file.

Fields configuration can be used to add a configuration for the field rendering. The syntax is the same as in the SAV Library Kickstarter but each configuration must start by the full field name. See after for an example.

Click on the red CSV icon to export your data. Below is the result obtained when the CSV file is imported in LibreOffice Calc.

As it can be seen, the user groups are displayed as a comma-separated list because the fields were exported in the raw mode. By selected, the second checkbox, it is displayed with the same rendering as in a single view.

Depending on the field type, HTML tags can be exported, which is the case with the usergroup field of the fe_users table. If you want to process these tags, use a stdWrapItem attribute for the field . For example, to remove them, add the following configuration in `Fields configuration` as shown below (see Changing the field configuration ).

Exporting Data to Other Formats 

The exporting form contains two fields XML file and XSLT file which enable the export to other formats.

The XML file field must be a XML file which will be used as a template. It may contain:

• field markers under the conventional format in the SAV Library Extension Generator, that is ###field_name###,
• localization markers under the conventional format in the SAV Library Extension Generator, that is $$$tag$$$ for a marker in the locallang.xlf file, $$$label[field_name]$$$ to obtain the label associated with a field,
• constant markers under the form $$$constant[tag]$$$.

The XML tag may contain special attributes:

• sav_type can be set to:

1. replaceAlways: the XML tag and its children will be processed for all exported rows,
2. replaceDistinct: the XML tag and its children will be processed each time the associated sav_id attribute changes in the rows,
3. cutIfEmpty: the XML tag and its children will be cut if the associated sav_id attribute is empty in the row,
4. cutIfNotEmpty: the XML tag and its children will be cut if the associated sav_id attribute is not empty in the row,
5. cutIfEqual, cutIfNotEqual, cutIfgreater, cutIfLower, cutIfgreaterEqual, cutIfLessEqual: the XML tag and its children will be cut if the associated sav_id attribute in the row is respectively equal to, not equal to, greater than, less than, greater than or equal to, lower than or equal to, a given value provided by the sav_value attribute.

• sav_id must be a field name,
• sav_value must be a value.

Let us illustrate this principle to generate a docbook article. If your are not familiar with docbook, please read https://www.oasis- open.org/docbook/documentation/reference/html/docbook.html and http://www.sagehill.net/docbookxsl/ . The former is the docbook definitive guide and the later the docbook xsl complete guide.

Assume that we want to produce the FE user list under the form of a table with four columns: the user image, his/her name, email and groups. It can be solved used the XML file to_docbook.xml, available in the Resources/Private/Files directory of this extension. As it can be seen, this file uses several markers and attributes.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article
  PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "https://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">

<article lang="en">
  <title>List of FE users</title>
  <informaltable>
    <tgroup cols="4" align="left" colsep="1" rowsep="1">
      <thead>
        <row>
          <entry align="center"></entry>
          <entry align="center">$$$label[fe_users.name]$$$</entry>
          <entry align="center">$$$label[fe_users.email]$$$</entry>
          <entry align="center">$$$label[fe_users.usergroup]$$$</entry>
        </row>
      </thead>
      <tbody>
        <row sav_type="replaceAlways">
          <entry align="center">
            <mediaobject sav_type="cutIfEmpty" sav_id="fe_users.image">
              <imageobject>
                <imagedata fileref="fileadmin###sys_file.identifier###" width="2cm" scalefit="1" />
              </imageobject>
            </mediaobject>
          </entry>
          <entry>###fe_users.name###</entry>
          <entry>###fe_users.email###</entry>
          <entry><itemizedlist spacing="compact">###fe_users.usergroup###</itemizedlist></entry>
        </row>
      </tbody>
    </tgroup>
  </informaltable>
</article>

In order to produce the XML file, the process is the same as for the CSV export. Each field marker have to be selected to be replaced and the template file has to be provided in the XML file field as shown in the following caption. The configuration was saved in `FE users (docbook)`.

In this example, the document is processed automatically, by calling for example the FOP docbook processor (https://xmlgraphics.apache.org/fop/), in the extension. In order to do so, an admin user must allow the use of the php exec function in the Advanced folder of the configuration of the extension as shown in the following caption.

A XSLT file (http://xmlfr.org/w3c/TR/xslt/) is used to process the resulting XML. Output can be transformed to virtually any file format. In this example, it transforms docbook XML file before the FOP processing.

The Exec field is filled with the following input in order to call FOP.

fop -xml ###FILE### -xsl c:/Program Files/fop/xsl/fo/docbook.xsl -pdf ###SITEPATH###/fileadmin/test.pdf

The tag ###FILE### will be replaced by the resulting file name. The xsl path for the file name docbook.xsl depends on your installation of the FOP processor.

The tag ###SITEPATH### will be replaced by your site path. Here, the generated file will be test.pdf in the fileadmin directory of the site. It leads to the following caption.

Using a Query for Exporting Data 

A query may be used instead of using the export view fields to select the data to be exported. In order to do so, the user TypoScript Config field or the group TypoScript Config must contain the following line :

sav_library_example8_ExportWithQuery = *

A new icon should be displayed in the export view.

Clicking on this icon toggle the export view to the query mode where a query can be entered. As it can be seen below, no field are displayed.

Save and click on the load icon to display the fields associated with the query.

Finally, select the fields, fill the configuration if any and click again on export icon to get the CSV file.

Table of Contents 

Edit View 

Two subforms are used to input the graph data. Even if another choice was possible for the field graph1, the use of a subform makes it possible to use similar queries for the graph.

• The subform graph1 is configured to allow the input of one item. It is used to input the number of sunny, cloudy and rainy day in the month.

• the subform graph2 is used to enter the minimal and maximal temperature for a given day. Note the field attributes used to add a delete button and up and down buttons in front of each item.

  addDelete = 1;
  addUpDown = 1;

  Copied!

Single View 

The type of the field graph is Graph. Its configuration includes the following properties.

cutLabel = 1;
graphTemplate = EXT:sav_library_example9/Resources/Private/Templates/Charts.xml;
allowQueries = 1;
tags = 
   marker#uidQueryGraph1 = 1,
   marker#uidQueryGraph2 = 2,
   marker#uidMainTable = ###uidMainTable###,
;

Analyze the graph template Charts.xml provided in the folder Resources/Private/Templates of the extension.

The markers marker#uidQueryGraph1 and marker#uidQueryGraph2 are used in the definition of the query manager. You could have to modify the value 1 and 2 as explained in the next section. The marker marker#uidMainTable takes the value of the current uid of the main table, i.e. tx_savlibraryexample9. This value is always available by means of the marker ###uidMainTable###.

<query id="graph1">
    <setQueryManager name="savcharts" uid="marker#uidQueryGraph1" uidMainTable="marker#uidMainTable" />
</query>
...
<query id="graph2">
    <setQueryManager name="savcharts" uid="marker#uidQueryGraph2" uidMainTable="marker#uidMainTable" />
</query>

Queries 

Add two Sav Charts queries in backend list mode. The following caption shows the result with queries inserted in the Data folder.

Fill the query Query Graph 1 as shown below.

The subforms used for the field graph1 and graph2 generates relations n:n. Therefoe, the FROM clause joins the tables tx_savlibraryexample9, tx_savlibraryexample9_graph1_mm and tx_savlibraryexample9_graph1.

tx_savlibraryexample9
INNER JOIN tx_savlibraryexample9_graph1_mm
    ON tx_savlibraryexample9.uid = tx_savlibraryexample9_graph1_mm.uid_local
INNER JOIN tx_savlibraryexample9_graph1
    ON tx_savlibraryexample9_graph1_mm.uid_foreign = tx_savlibraryexample9_graph1.uid
    

The WHERE clause retricts the records to the one used by the Single view. The marker ###uidMainTable### does the job.

tx_savlibraryexample9.uid = ###uidMainTable###

Fill the query Query Graph 2 by replacing respectively tx_savlibraryexample9_graph1 and tx_savlibraryexample9_graph1_mm by tx_savlibraryexample9_graph2 and tx_savlibraryexample9_graph2_mm.

plugin.tx_savlibraryexample9_pi1.Default.singleView.fields.graph.tags (
   marker#uidQueryGraph1 = 3, 
   marker#uidQueryGraph2 = 4, 
   marker#uidMainTable = ###uidMainTable###
)  

Enter data in the frontend as shown below.

Save, and go to the frontend.

Tables of Contents 

Positioning the Fields 

The positioning of the fields is very simple in the List view because you can define the template. For the Single and Edit views, the positioning can be obtained using the wrapItem property. This property has the same syntax and the same behaviour as the wrap property in TypoScript.

To perform the requested positioning, we will use <div> tags organized as follows:

The wrapping is done field by field. For example, the first field is image. It defines the beginning of the container <div> and the image <div> when the following property is used:

wrapItem = <div class="container"><div class="image"> | </div>;

• Analyze the wrapItem for all the fields, then open the file sav_library_example10.css in the Resources/Public/Css directory to analyze the configuration. As it can be seen, the labels associated with the field are not displayed thanks to the {display:none;} CSS configuration. Let us note that the same result could have been obtained using the cutLabel property in the Kickstarter (see for example the image and map fields).

Executing the Plugin 

Executing a plugin in the extension can simply be done by means of the tsObject and tsProperties properties. The tsObject is a content object in TypoScript, that is TEXT, FILE, CONTENT, ... Below is the configuration of the field map.

tsObject = EXTBASEPLUGIN;

The EXTBASEPLUGIN is used to execute the default action of the plugin Maps2. The extension settings are iported and modified. Let us note the use of the marker ###poi_uid### which provides the uid of the point of interest for the map.

tsProperties =
   extensionName = Maps2
   pluginName = Maps2

   settings < plugin.tx_maps2.settings
   settings {
      zoom = 18
      poiCollection = ###poi_uid###
      category =
      mapWidth = 100%
      mapHeight = 300
   }
;

showIf = 0 < ###poi_uid###;

The showIf property checks if the marker ###poi_uid### is positive. If true the map is displayed, otherwise it is cut as shown below.

Let us now explain how the marker ###poi_uid### is set. Let us have a look to the configuration of the field poi_uid whose type is Show Only.

The first configuration is to always cut the field, i.e. it will not be displayed because it is is just a working field.

cutIf = true;

The second configuration gets the uid by means of a CONTENT object. The marker ###uidMainTable### is always available. It is replaced by the uid of the current field in the main table.

tsObject = CONTENT;
tsProperties =
   table = tx_maps2_domain_model_poicollection
   select {
      join = tx_savlibraryexample10_poi_mm ON tx_maps2_domain_model_poicollection.uid = tx_savlibraryexample10_poi_mm.uid_foreign
      selectFields = tx_maps2_domain_model_poicollection.uid
      where = uid_local = ###uidMainTable###
   }
renderObj = TEXT
renderObj.field = uid
; 

The third configuration sets the field value in the marker poi_uid, i.e. the marker ###poi_uid### is now available.

renderFieldInMarker = poi_uid;

Downloading documents (sav_download) 

Screenshots 

Minutes of Meetings (sav_meetings) 

whereSelect=###group_list=sav_meetings###;

tx_savmeetings.Meetings.editView.fields.participants.whereSelect = ###group_list=testgroup###
tx_savmeetings.Meetings.editView.fields.tx_savmeetings_item.proposed_by.whereSelect = ###group_list=testgroup###

Screenshots