TypoScript
All following TypoScript configuration consists in plugin.
Hint
We prefer using the Site Settings to configure maps2 since TYPO3 13.
view
templateRootPaths
Default: EXT:
Example: plugin.
You can override our Templates with your own SitePackage extension.
partialRootPaths
Default: EXT:
Example: plugin.
You can override our Partials with your own SitePackage extension.
layoutsRootPaths
Default: EXT:
Example: plugin.
You can override our Layouts with your own SitePackage extension. We prefer to change this value in TS Constants.
persistence
storagePid
Default: empty
Example: plugin.
Set this value to a Storage Folder where you have stored the event records.
Important
If you have stored Organizers and Locations in another Storage Folder, you have to add theses PIDs here, too.
Tip
If you use creation of events over frontend plugin, new records will be stored in first PID found in storagePid. To store record in other storage PIDs you need following configuration
plugin.tx_maps2.persistence.classes.JWeiland\maps2\Domain\Model\Event.newRecordStoragePid = 34
plugin.tx_maps2.persistence.classes.JWeiland\maps2\Domain\Model\Location.newRecordStoragePid = 543
settings
overlay.link.addSection
Default: 1
Example: plugin.
Append URI section to link of button in consent template. Useful to jump directly to the content element record with maps2 plugin.
With option set to 1: [currentURI]/mapProviderRequestsAllowedForMaps2=1#c123
With option set to 0: [currentURI]/mapProviderRequestsAllowedForMaps2=1
infoWindowContentTemplatePath
Example: plugin.
Here you can define your own Fluid-Template for these little PopUps of Markers.
Since maps2 9.2.0 you have access to all related foreign records of your
PoiCollection in Template.
Use: <f:
As such a PoiCollection can be assigned to multiple different tables like tt_address, news, what ever, you can differ between the foreign records with f.e.:
<f:groupedFor each="{poiCollection.foreignRecords}" as="groupedForeignRecords" groupBy="jwMaps2TableName" groupKey="tableName">
<div>Table: {tableName}</div>
<ul>
<f:for each="{groupedForeignRecords}" as="foreignRecord">
<li>PoiCollection URL: {foreignRecord.url}</li>
</f:for>
</ul>
</f:groupedFor>
jw and jw are two special keys we have added to each foreign record.
infoWindow.image.width
Default: 150c
Example: plugin.
Set the maximum width of images within the InfoWindow PopUp
infoWindow.image.height
Default: 150c
Example: plugin.
Set the maximum height of images within the InfoWindow PopUp
markerClusterer.enable
Available for Google Maps and OpenStreetMap
Default: 0
Example: plugin.
This value is configurable through the site setting
maps2. ("Enable Marker Clusterer") of site set
Maps2 - Default Set.
If you work with a lot of poi collection records you can activate the marker clusterer. The marker clusterer will merge multiple nearby poi collections to 1 icon showing the amount of contained records. The markers separate as the visitor zooms in.
For Google Maps the library Marker is used. For OpenStreetMap the
official Leaflet plugin
Leaflet.markercluster
is used. With OpenStreetMap only point markers are clustered. Areas, routes and
radius records are always shown as they are. While editing a marker in
frontend, clustering is not used.
This TypoScript value is the source of truth. It also applies to maps which are rendered by foreign extensions through the maps2 Fluid partials.
Hint
Editors can override this value per content element in the "Map Options" tab of the maps2 plugin. See markerClusterer.override.
markerClusterer.imagePath
Only available for Google Maps
Default: EXT:
Example: plugin.
If you don't like the icons of Marker Clusterer you can choose a different path for your own images.
markerClusterer.styleSheet
Only available for OpenStreetMap
Default: EXT:
Example: plugin.
Leaflet.markercluster does not work with images like the Google Maps
MarkerClusterer. The cluster icons are HTML elements which are styled by CSS
classes marker-, marker- (less than 10 markers),
marker- (less than 100 markers) and marker-.
By default, maps2 loads the default theme Marker of
Leaflet.markercluster. If you don't like the cluster icons, copy that file to
your site package, adapt it (colors, sizes, background images, ...) and set
the path to your own file here. If you clear this value, no theme stylesheet
will be loaded at all and you can style these CSS classes within the
stylesheets of your site package.
The required base stylesheet Marker (animations) is always loaded,
if marker clustering is enabled.
_LOCAL_LANG
As an integrator you can override each language key with TypoScript. For frontend maps2 uses this file:
EXT:
Example: plugin.