..  include:: /Includes.rst.txt


..  _extensionSettings:

==================
Extension Settings
==================

Some general settings for events2 can be configured in `Admin Tools` -> `Settings`.

The settings are divided into several tabs and described here in detail:

Tab: Basic
==========

poiCollectionPid
----------------

Default: 0

Only valid, if you have installed EXT:maps2.

While creating location records events2 catches the address and automatically creates a maps2 record
for you. Use this option to define a storage PID, where these records should be stored.

rootUid
-------

Default: 0

If you have many sys_category records with huge trees in your TYPO3 project, it may make sense to
reduce the category trees in events2 plugins to a parent category UID (root UID).

..  tip::

    Using TCA option `rootUid` for trees is deprecated since TYPO3 11. `events2` will take care
    of that and updates the new option `startingPoints` automatically for you, if you set this
    option here.

recurringPast
-------------

Default: 3

Our events2 works within a timeframe. This means, that you have to set an earliest start (in months) for generated
day records in past. A value of 3 means 3 months in past. Older events will not be shown in frontend anymore, but are
still visible by Google Search.

recurringFuture
---------------

Default: 6

Our events2 works within a timeframe. This means, that you have to set a latest end (in months) for generated
day records in future. A value of 6 means 6 months in future. Events above 6 month in future will not be shown
in frontend.

defaultCountry
--------------

Default: empty

While creating location records we also create a record for EXT:maps2 while saving.
If you're only working for one specific country while creating/editing locations
in backend, it may be helpful to set country property with this default country. So you only need
to add street and city to find a POI. If you need POIs from all over the world, please keep this field empty.

xmlImportValidatorPath
----------------------

Default: EXT:events2/Resources/Public/XmlImportValidator.xsd

If you use our XML importer we will validate your XML structure against a XSD file. So, if you use name-Tag for
categories the import will fail, because XSD knows that only a title-Tag is valid.

By default organizer, location and categories are mandatory while import. If you set organizer and/or
location as non-mandatory in Extension Setting this has no effect to the importer. Please make a copy of
our XSD file and add the modifications you need and set new file path into this variable.

You can prefix the path with EXT:

organizerIsRequired
-------------------

Default: false

If you want, you can set column *Organizers* as required. That way an editor has to fill this column.

locationIsRequired
------------------

Default: false

If you want, you can set column *Location* as required. That way an editor has to fill this column.

categoryIsRequired
------------------

Default: false

If you want, you can set column *Categories* as required. That way an editor has to fill this column.

pathSegmentType
---------------

Default: Do nothing (Internal: empty)

events2 works with path segments to help you building much more readable URLs with new RouteEnhancers. But what should
happen, if there are duplicates while executing the PathSegmentUpdateWizard or a frontend user creates a new event?

Info: This setting does not effect new events generated within TYPO3 Backend, as we do not have any UID while storing
the event!

**Do nothing (default)**
The column `path_segment` will not be touched by events2. Use the SignalSlot in `createAction` and implement
generation of `path_segment` on your own. But if you return an empty value events2 will throw an exception.

**RealUrl**
`path_segment` will be filled with an incremented value of event title. If there are 3 events called `swimming` it
will result in `swimming`, `swimming-1`, `swimming-2`

**Incl. UID**
Column `path_segment` will be filled with a combination of event title and uid like: `star-wars-77`


Tab: Email
==========

emailFromAddress
----------------

Default: empty (use value from INSTALL_TOOL)

With events2 you can give your website visitors the possibility to create new
events. These created records will be hidden by default. Add an email address
of the sender, if a new record was created over the frontend.

emailFromName
-------------

Default: empty (use value from INSTALL_TOOL)

With events2 you can give your website visitors the possibility to create new
events. These created records will be hidden by default. Add a name
of the sender, if a new record was created over the frontend.

emailToAddress
--------------

Default: empty

With events2 you can give your website visitors the possibility to create new
events. These created records will be hidden by default. Add an email address
of the receiver, if a new record was created over the frontend.

emailToName
-----------

Default: empty

With events2 you can give your website visitors the possibility to create new
events. These created records will be hidden by default. Add a name
of the receiver, if a new record was created over the frontend.