What does it do? 

maps2 is an extension for TYPO3 CMS. It can render you a map based on Google Maps and/or OpenStreetMap. If you want, you can create Markers, Routes, Area and Radius overlays. Assign these overlays to categories to build a map, with all points based on selected category.

Screenshots 

See maps2 in action.

Point 

Radius 

Area 

Route 

Composer mode 

If your TYPO3 installation uses Composer, install the latest release of this extension through:

composer require jweiland/maps2

If you are not using the latest version, you need to add a version constraint, for example:

composer require jweiland/maps2:"^9.3"

Legacy mode 

If you are working with a TYPO3 installation that does not use Composer, install the extension in the Extension Manager:

• Navigate to Admin Tools > Extensions > Get Extensions.
• Click on Update now
• Search for maps2
• Click Import and install on the side of the extension entry

and activate it:

• Navigate to Admin Tools > Extensions > Installed Extensions
• Search for maps2
• Activate the extension by clicking on the Activate button in the

A/D column

Next step

Please edit ExtensionManager configuration of maps2 to decide, if you will use Google Maps or OpenStreetMap as your default rendering service: extensionmanager.

Minimal Example 

• Include static template Maps2 Default (maps2)
• include one of these static templates Maps2 for Google Maps (maps2) or Maps2 for Open Street Map (maps2)

Update these properties in TypoScript Constant Editor:

plugin.tx_maps2 {
  persistence {
    # We prefer to set a Storage PID where the maps2 records are located
    storagePid = 4
  }
  settings {
    # If you're using Google Maps you have to set an API key to allow loading the map in frontend
    googleMapsJavaScriptApiKey = ABC123...
  }
}

Tab: Basic 

settings.infoWindowContentTemplatePath = EXT:my_ext/Resources/Private/Extensions/Maps2/InfoWindowContent.html

Tab: Gm 

Tab: Osm 

Tab: Design 

Maps2: Show map 

Maps2: Search Radius 

Maps2: City Map 

view 

persistence 

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 

<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>

_LOCAL_LANG 

As an integrator you can override each language key with TypoScript. For frontend maps2 uses this file:

EXT:maps2/Resources/Private/Language/locallang.xlf

Example: plugin.tx_maps2._LOCAL_LANG.de.listMyEvents = Zeige meine Veranstaltungen

Create the records 

Before any maps2 record can be shown in the frontend those need to be created.

1. Create a new sysfolder. (Of course you can also use an existing sysfolder).
2. Switch to List module
3. Use the icon in the topbar "Create new record" and search for "Maps2" and its record "Marking".
4. Click on "Marking" to create a new maps2 record.
5. Give it a title (required)
6. Choose a type of record you want to create. This will reload the form to show further fields especially for this record type. Alternative you can click on one of these type images to switch the type.
7. After reload you should see some more tabs now. Click on tab "Map"
8. Field "Address" is required, but you can not fill it. Please use the search field at top of map to search for an address and press <Return>. If an address was found, we will automatically fill the required address field in a formatted representation of the searched address.

Add a plugin to a page 

A plugin is used to render a defined selection of records in the frontend. Follow this steps to add a plugin to a page:

Global fields 

Additional fields for Point 

Additional fields for Area 

Additional fields for Route 

Additional fields for Radius 

Working with type "Point" 

First of all search for an address.

To fine tune the position you can click somewhere on the map or drag'n drop the marker to your preferred location.

Working with type "Area" 

First of all search for an address.

With left click somewhere on the map you can create new points on the map. You need at least 3 clicks to see the fill color of the area. Use right click to remove a point.

Route 

First of all search for an address.

With left click somewhere on the map you can create new points on the map. Use right click to remove a point.

Radius 

First of all search for an address.

Click somewhere on the map or drag'n drop the center of the radius to move the marker around. You can resize the radius via drag'n drop with one of the points at the border.

Google Cloud Platform 

1. If you don't have a Google Account you have to register as a new User.
2. Open Google Maps at Google Cloud Platform.

3. Click the button Get started which will open the Enable Google Maps Platform Guide

   

4. Activate the Checkboxes for Maps and Places. Actually we don't have support for Routes, so keep them deactivated.

5. Click on Continue

   

6. Open Selectbox Select or create project and choose + Create a new project (give it a cool name) or choose one of your previously created projects.
7. Click Next

8. If you already have assigned your billing information to your Google Account, you now can assign them to your new project. Else you have to create new billing information first.

   Important

   Google needs these billing information to be sure, that you're not a robot. That's not a joke, that's google.

9. After assigning your billing information to your project, you will get the information that some APIs have automatically activated for your project.

   

10. Click Next. It will need some seconds until all needed APIs were activated.
11. You will get a Done-Message from where you can copy your new API Key and yes: As mentioned in this dialog-box you should improve your app's security and restrict the key's usage. If you don't do so, everyone else can use your API Key and may generate costs over your billing information. So please: follow the link to API Console to configure API security.
12. You will find a new entry from today with the glorious unique name API key. Please edit this entry to assign it a better name and configure security settings.
13. Give it a better Name like: Secure Map API for my project X
14. Set security settings to: IP-Address (Webserver, Cronjobs etc.) and enter the IP-Address of your server. Do not activate HTTP link as maps2 can retrieve GEO location which will never match any configured HTTP links.
15. Copy your API Key and paste it into the both API fields in Extension Configuration of maps2.

Do you want it more safe? 

In the section above we told you to assign your servers IP-Address to your new API Key, right? Ok. What happens, if you're on a shared hosting system? Every customer on the same server can use your API Key for its own website. Hmm, bad. Please visit the API Console again and create a second API Key. Give it a cool name, but that time you set security settings to HTTP-link and assign all of your domains to this security setting.

Copy API Key with HTTP-link to field JavaScript API Key in Extension Configuration of maps2.

Copy API Key with IP-Address security to field Geocoding API Key in Extension Configuration of maps2.

Do you want it super safe? 

Visit API Console again and go to your billing information

Configure some Budgets to prevent unwanted credits at your credit card.

Example Configuration 

routeEnhancers:
  Maps2Plugin:
    type: Extbase
    extension: Maps2
    plugin: Maps2
    routes:
      -
        routePath: '/poi/{method}'
        _controller: 'Ajax::process'
    defaultController: 'PoiCollection::show'
    aspects:
      method:
        type: StaticValueMapper
        map:
          renderInfoWindowContent: 'renderInfoWindowContent'

Upgrade to Version 11.0.0 

This version is not TYPO3 11 compatible!

Updating TYPO3 extensions with help of class.ext_update.php is deprecated since TYPO3 11.0 and was removed with TYPO3 12.0. So, if you upgrade from a very old maps2 version you should upgrade maps2 to at lease version 10.* and execute the upgrade wizard in extensionmanager first.

Upgrade to Version 10.0.9 

Somewhere in October 2023 the usage of addresses as path segment in OpenStreetMap Geocoding URIs has been deprecated/removed. Please execute the UpgradeWizard to activate the new parameter based OSM Geocoding URI. This UpgradeWizard will only update that value, if it is the original old URI. Any modified URIs will be kept untouched.

Upgrade to Version 10.0.0 

We have added a new Option defaultMapType to Extension Settings of maps2. Please check, if this value matches your needs and can be found in LocalConfiguration.php.

Table tx_maps2_domain_model_poi has been removed. All POIs will be stored in table tx_maps2_domain_model_poicollection now. Please execute UpgradeWizard to migrate existing POI records.

Extension Setting and TypoScript setting allowMapTemplatePath was completely removed. We have added a new ControllerAction called OverlayAction, so please overwrite FluidTemplate Overlay.html instead.

All widgets are removed, as TYPO3 11 does not support ViewHelper widgets anymore. We have moved the widget into its own Partial. Please add path to maps2 partial as follows:

plugin.tx_myext {
  view {
    partialRootPaths {
      ...
      5 = EXT:maps2/Resources/Private/Partials/
    }
  }
}

We have added a new FlashMessage queue identifier extbase.flashmessages.maps2 for non-controller FlashMessages like in GeoCodeService. Please update your fluid templates and add both ViewHelpers:

<f:flashMessages />
<f:flashMessages queueIdentifier="extbase.flashmessages.maps2" />

We have changed FlexForm sheet sDEFAULT for Plugins searchwithinradius and citymap to sDEF. Please execute UpgradeWizard to move related values to new sheet and remove duplicates.

Only valid for developers:

As we have loaded Extbase ConfigurationManager within Middleware before TSFE it may switch to the BackendConfigurationManager which is completely wrong. To prevent that we have moved MapService::getMapProvider to MapHelper:getMapProvider and deprecated MapService::getMapProvider. Please adopt that in your extension.

JavaScript files GoogleMaps2.js and OpenStreetMap2.js have changed. Please update your JavaScript accordingly, if you have overwritten our files.

Update to Version 9.3.4 

We have moved all constructor arguments into inject-methods in MapProviderRequestService. We have moved all constructor arguments into inject-methods in AjaxController. So please clear all cache after update. Please use "Flush Cache" in Installtool for TYPO3 10.* to update DI cache.

Upgrade to Version 9.0.0 

As Maps2 is TYPO3 10 compatible now we have removed TYPO3 8 compatibility. Please install an old version of maps2, if you still need TYPO3 8 compatibility. On GitHub we have created a new Branch called TYPO3_8-7.

We have removed Maps2Registry Cache from TYPO3 CachingFramework. So you can remove the Maps2Registry Caching Tables from DB. The cached Maps2Registry configuration will now be saved in typo3conf/Maps2/Registry.json. In case of Composer it will be stored in config/Maps2/Registry.json.

As a normal user you only need to clear the caches. If you make use of the Maps2Registry API, please check, if the new json configuration file was created. Further it would be good to check, if the tx_maps2_uid columns still exists in DB.

Upgrade to Version 8.0.0 

As a normal user you can update to this version without any problems.

We have changed the SignalSlot preIsRecordAllowedToCreatePoiCollection. It does not allow returning $isValid as 4th parameter anymore. As $isValid is a reference now, please change it directly and prevent your SignalSlot to return anything.

There is no Debug Output of Map Provider response in Backend anymore, if request fails. We have added more detailed error messages instead. As a Dev, you can access all Messages of Client and GeoCodeService directly.

Upgrade to Version 7.0.0 

As a normal user you can update to this version without any problems.

As an extension developer who has modified maps2 you should read following lines:

We have removed ModifyMarker class. --> Please update lat, lng and radius fields in BE form with JS directly.

We have removed modifyMarkerInDb function in our Map Provider JS files for BE modules. --> Please update lat, lng and radius fields in BE form with JS directly.

We have removed AjaxController. --> As it was not used since months, it was not used anymore.

We have removed all extbase usage from all Ajax classes and have rewritten them completely with Doctrine. --> Please check your extension and check if an update is needed.

Update to Version 6.1.0 

As mouseScrollWheelZoom is not available for all map providers you have to execute the Update Wizard to move this Option in FlexForm from Google Maps sheet to MapOptions sheet.

Upgrade to Version 6.0.0 

The current CacheIdentifier for InfoWindowContent is not save for multilingual environments. That way we have removed cacheIdentifier property from all Cache ViewHelpers and added the new property poiCollection. It helps us to build a more unique CacheIdentifier with GeneralUtility::stdAuthCode()

You have to update all of your templates where our Cache ViewHelpers are used. In most cases only InfoWindowContent.html has to be modified. Please remove cacheIdentifier from all Cache ViewHelpers and add poiCollection instead:

Before: <m:cache.setCache cacheIdentifier="htmlCode{poiCollection.uid}" data="{content -> f:format.raw()}" /> After: <m:cache.setCache data="{content -> f:format.raw()}" poiCollection="{poiCollection}" />

Please you are interested into Cache ViewHelper properties, please have a look into our updated Documentation.

Update to Version 5.1.0 

We have removed the hard-coded map provider settings from VH Widgets and added these to TS-Template. So please check your maps2 output and/or individual JS, if our Widget VHs are still working for you.

If you don't make use of our Widget ViewHelpers there should be no problem with this update.

Upgrade to Version 5.0.0 

We have added an Open Street Map Implementation. To differ between them we have added two new static templates. One for Google Maps and one for Open Street Map. You have to keep the Default static template, but you have to add one of the other static templates.

There is a new Option called mapProvider in ExtensionManager. Please set the mapProvider and default mapProvider to your needs.

We have moved some Google Maps fields in FlexForm to another sheet. To prevent duplicates in DB please execute Update Wizard in Installtool.

We have removed automatic registering tx_maps2_uid column for tt_address. Please take a look into the example of Maps2 Registry to see how it works.

As we have removed our API class GoogleMapsService completely you now have to use the API methods in MapService and GeoCodeService instead.

getPositionsByAddress returns an ObjectStorage containing Position objects instead of RadiusResult objects now. getFirstFoundPositionByAddress return an object of type Position now.

Upgrade to Version 4.0.0 

We have added some new fields to maps2. So please go into Extensionmanager and open the configuration. Please check, if everything matches your needs and safe the configuration.

You have to clear the system cache, because of new fields in TCA.

We have renamed the field marker_icon from table sys_category into maps2_marker_icons and switched to FAL related images. Please execute Update script in Extensionmanager for maps2 to migrate your old images.

We have moved all JavaScript Code from page.includeJSFooter to page.includeJSFooterlibs, so now you have better options to override or append our/your custom JavaScript in TypoScript.

All methods of MapService have been migrated into GoogleMapsService. GeocodeUtility have been deleted. Please use getPositionsByAddress or getFirstFoundPositionByAddress of GoogleMapsService.

Upgrade to Version 3.0.0 

We have removed TYPO3 6.2 compatibility completely.

In f.e. germany it is not allowed to send the users ip address without his confirmation. That's why we have added a new extension management configuration which can output a little form, where the user can accept sending his information to third party servers like Google to display the maps. This new feature touches nearly all methods, so, if you have extended maps2, please pre-check the new widget templates and actions. Maybe it's good to have a look into the new GoogleMapsService class.

Update to Version 2.5.0 

With version 2.5.0 we have solved a camelcase problem of the cache table. It was renamed from cf_maps2_cachedHtml to cf_maps2_cachedhtml. Please delete the old tables cf_maps2_cachedHtml and cf_maps2_cachedHtml_tags, deactivate maps2 in extension manager and activate it again.

Upgrade to Version 2.0.0 

Version 2.0.0 needs a Google Maps JavaScript ApiKey which has to be inserted in maps2 configuration of Extensionmanager (for BE usage) and in constants section of your TypoScript-Template (for FE usage). That's why you have to insert the static template Maps2 (maps2) in your TypoScript Template now.

Furthermore we have updated the FlexForm of maps2 and removed the option for SwitchableControllerActions. With version 2.1.2 we have added an Update-Wizard in Extensionmanager which can do that job for you. In prior versions you have to remove that setting of each plugin in tt_content record field pi_flexform on your own.

Changing paths of the template 

You should never edit the original templates of an extension as those changes will vanish if you upgrade the extension. As any extbase based extension, you can find the templates in the directory Resources/Private/.

If you want to change a template, copy the desired files to the directory where you store the templates. This should be a directory in your SitePackage extension. Multiple fallbacks can be defined which makes it far easier to customize the templates.

plugin.tx_maps2 {
  view {
    templateRootPaths >
    templateRootPaths {
      0 = EXT:maps2/Resources/Private/Templates/
      1 = EXT:site_package/Resources/Private/Extensions/Maps2/Templates/
    }
    partialRootPaths >
    partialRootPaths {
      0 = EXT:maps2/Resources/Private/Partials/
      1 = EXT:site_package/Resources/Private/Extensions/Maps2/Partials/
    }
    layoutRootPaths >
    layoutRootPaths {
      0 = EXT:maps2/Resources/Private/Layouts/
      1 = EXT:site_package/Resources/Private/Extensions/Maps2/Templates/Layouts/
    }
  }
}

plugin.tx_maps2 {
  view {
    templateRootPath = EXT:site_package/Resources/Private/Extensions/Maps2/Templates/
    partialRootPath = EXT:site_package/Resources/Private/Extensions/Maps2/Partials/
    layoutRootPath = EXT:site_package/Resources/Private/Extensions/Maps2/Layouts/
  }
}

All ViewHelpers 

Examples 

<div id="maps2" data-override="{override -> maps2:convertToJson()}"></div>

Examples 

<f:if condition="{m:isRequestToMapProviderAllowed()}">
  <f:then>
    ...do something to show the map or what ever you want...
  </f:then>
  <f:else>
    ...show overlay or add a message what user should do to see the map...
  </f:else>
</f:if>

Examples 

<a href="{m:requestUriForOverlay()}">
  Link to current page. Map will be shown somewhere on that page.
</a>

<a href="{m:requestUriForOverlay(ttContentUid: ttContentUid)}">
  Link to current page and scroll to content element with map.
</a>

General properties 

• Name

  Name:

  Type

  Type: :Description: Description: :Default value: Default value:

• Name

   

  Type

  string

  Description

  Delimiter

  Default value

  ,

Examples 

<f:for each="{poiCollection.address -> maps2:trimExplode()}" as="address" iteration="iterator">
  ..do something with {address}
</f:for>

General properties 

Examples 

{maps2:cache.getCache(poiCollection: poiCollection)}

General properties 

Examples 

<f:if condition="{maps2:cache.hasCache(poiCollection: poiCollection)}">
  <f:then>
  </f:then>
  <f:else>
  </f:else>
</f:if>

General properties 

Examples 

{maps2:cache.setCache(poiCollection: poiCollection, data: '{content->f:format.raw()}')}

Methods 

Example 

Here we have a working example out of our extension events2:

// create new map-record and set it in relation
$position = $this->googleMapsService->getFirstFoundPositionByAddress($this->getAddress($eventLocation));
if ($position instanceof Position) {
    $tsConfig = $this->getTsConfig($eventLocation);
    $this->googleMapsService->assignPoiCollectionToForeignRecord(
        $this->googleMapsService->createNewPoiCollection(
            (int)$tsConfig['pid'],
            $position,
            array(
                'title' => $eventLocation['location']
            )
        ),
        $eventLocation,
        'tx_events2_domain_model_location',
        'tx_maps2_uid'
    );
}

Example for tt_address 

<?php
if (!defined('TYPO3')) {
    die('Access denied.');
}

call_user_func(function() {
    if (\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::isLoaded('maps2')) {
        \JWeiland\Maps2\Tca\Maps2Registry::getInstance()->add(
            'tt_address',
            'tt_address',
            [
                'addressColumns' => ['address', 'zip', 'city'],
                'countryColumn' => 'country',
                'synchronizeColumns' => [
                    [
                        'foreignColumnName' => 'name',
                        'poiCollectionColumnName' => 'title'
                    ]
                ]
            ]
        );
    }
});

PoiCollection 

Add static TS template Maps2 Default (maps2) and one of the Maps2 for Google Maps (maps2) or Maps2 for Open Street Map (maps2) templates to the page where your extension/plugin belongs to, as far as not already done in root page.

In case of Maps2 for Google Maps (maps2)please check, if following TS constant is set:

plugin.tx_maps2.view.googleMapsJavaScriptApiKey

Add a further entry for maps2 to partialRootPaths configuration of your extension, so that fluid can find our new partials:

plugin.tx_myext.view.partialRootPaths {
    0 = EXT:my_ext/Resources/Private/Partials/
    1 = EXT:maps2/Resources/Private/Partials/
}

Replace old maps2:widget.poiCollection ViewHelper in templates of your extension:

<maps2:widget.poiCollection poiCollection="{location.txMaps2Uid}" override="{settings: {mapWidth: '100%', mapHeight: '300', zoom: '14'}}" />

with following html:

<f:render partial="Maps2/PoiCollection"
          section="showMap"
          arguments="{poiCollection: location.txMaps2Uid, override: {settings: {mapWidth: '100%', mapHeight: '300', zoom: '14'}}}" />

EditPoiCollection 

Add static TS template Maps2 Default (maps2) and one of the Maps2 for Google Maps (maps2) or Maps2 for Open Street Map (maps2) templates to the page where your extension/plugin belongs to, as far as not already done in root page.

In case of Maps2 for Google Maps (maps2)please check, if following TS constant is set:

plugin.tx_maps2.view.googleMapsJavaScriptApiKey

Add a further entry for maps2 to partialRootPaths configuration of your extension, so that fluid can find our new partials:

plugin.tx_myext.view.partialRootPaths {
    0 = EXT:my_ext/Resources/Private/Partials/
    1 = EXT:maps2/Resources/Private/Partials/
}

Replace old maps2:widget.editPoiCollection ViewHelper in templates of your extension:

<maps2:widget.editPoi property="txMaps2Uid"
                      title="{company.company}"
                      poiCollection="{company.txMaps2Uid}"
                      override="{settings: {mapWidth: '100%', mapHeight: '300'}}" />

with following html:

<f:render partial="Maps2/EditPoiCollection"
          section="editMap"
          arguments="{poiCollection: company.txMaps2Uid, property: 'txMaps2Uid', title: company.company, override: {settings: {mapWidth: '100%', mapHeight: '300', zoom: '14'}}}" />

DB compatibility 

In most cases EXT:maps2 uses the QueryBuilder to query data, but in case of Plugin maps2_searchwithinradius we need to execute a native MySQL query without QueryBuilder to find the related POIs. In that special case MySQL/MariaDB is mandatory.

Consent Tools 

If you want to use external consent tools you should deactivate both options explicitAllowMapProviderRequests and explicitAllowMapProviderRequestsBySessionOnly in extension manager.

<div id="maps2-{data.uid}"
     class="maps2"
     data-name="maps2"
     data-environment="{environment -> maps2:convertToJson()}"
     data-pois="{poiCollections -> maps2:convertToJson()}"></div>

{
    name: 'maps2',
    default: false,
    title: 'Google Maps/Open Street Map',
    // contextualConsentOnly: true,
    optOut: false,
    required: false,
    purposes: ['analytics'],
},

let manager = klaro.getManager();
manager.watch({
    update: function(manager, eventType, data) {
        if (
            eventType === 'saveConsents'
            && data.consents.maps2 === true
        ) {
            window.location.reload();
        }
    }
});

Version 11.0.10 

• Fixed issue with extracting OpenStreetMap house number

Version 11.0.9 

• Create fake TYPO3_REQUEST in CLI mode

Version 11.0.8 

• Check for TYPO3_REQUEST, before accessing it

Version 11.0.7 

• Set addQueryString to "untrusted" in RequestUriForOverlay VH

Version 11.0.6 

• Set addQueryString back to "true". "untrusted" comes in with TYPO3 12 first

Version 11.0.5 

• Set addQueryString to "untrusted" in RequestUriForOverlay VH

Version 11.0.4 

• BUGFIX: Show overlay for all maps2 plugins if activated
• BUGFIX: Prevent core storing in BE form, when hitting ENTER on OSM search
• TASK: Test on MariaDB 10.11
• TASK: Rename LICENSE.md to LICENSE

Version 11.0.3 

• BUGFIX: Implement better extend function for JavaScript

Version 11.0.2 

• BUGFIX: Do not store FlashMessages in BE session in CLI context

Version 11.0.1 

• BUGFIX: Use correct TypoScript syntax for settings.mapTypeId

Version 11.0.0 

• BUGFIX: Show info window content for TYPO3 instances where FE/pageNotFoundOnCHashError is active
• DOCU: Add section about routing configuration

Version 10.0.10 

• BUGFIX: Repair OSM UpgradeWizard for TYPO3 10

Version 10.0.9 

• BUGFIX: Exclude external Google Maps JS script from concatenation
• BUGFIX: Update to new OSM Geocode URI. Please execute UpgradeWizard
• DOCU: Set indents to 4 spaces

Version 10.0.8 

• BUGFIX: To allow h* tags in info_window_content we have moved preview as fieldWizard below RTE

Version 10.0.5 

• BUGFIX: Create new Overlay Partial, so it can be used from foreign extensions
• TASK: Deprecate getRequestUri() in PoiCollectionController
• FEATURE: Add new RequestUriForOverlay ViewHelper
• FEATURE: Add new IsRequestToMapProviderAllowed ViewHelper
• TASK: Add FETCH_ASSOC to all fetch() methods to prevent deprecation logs
• BUGFIX: Catch JsonException if Maps2Registry config is empty

Version 10.0.4 

• BUGFIX: A reload bypasses consent

Version 10.0.3 

• BUGFIX: Better implementation for category selector

Version 10.0.2 

• Apply isset to $dataHandler->substNEWwithIDs[$uid] before accessing record UID

Version 10.0.1 

• Check for existence of poi table before loading UpgradeWizard

Version 10.0.0 

• Remove TYPO3 9 compatibility
• Add TYPO3 11 compatibility
• Removed tx_maps2_domain_model_poi table (Please execute UpgradeWizard)
• Update Documentation (Adopt TYPO3 Doc Styleguide)
• Move MapService::getMapProvider to MapHelper:getMapProvider
• Remove MapProviderOverlayRequestHandler
• Implement new uncached ControllerAction to show Overlay
• Replace PoiCollection and EditPoiCollection Widget
• Add new setting: overlay.link.addSection
• Category selection in FE works for area, route and radius, too.
• Add SettingsHelper to get streamlined settings
• Add extbase.flashmessages.maps2 queue identifier for non-controller FlashMessages
• Rename sDEFAULT to sDEF in FlexForm
• Change frontend behaviour for multiple categories

Version 9.3.10 

• BUGFIX: Show InfoWindowContent in translated language

Version 9.3.9 

• BUGFIX: Add all GET-params to requestUri. Needed for AllowMap template

Version 9.3.8 

• Set address column as readonly
• Add further description for TCA columns

Version 9.3.7 

• Replace plain SQL query with SchemaManager to be PostgreSQL compatible

Version 9.3.6 

• Update TS condition for requireCHashArgumentForActionArguments
• [BUGFIX] Re-Implement OverlayRequestHandler

Version 9.3.5 

• Update old TS condition for requireCHashArgumentForActionArguments

Version 9.3.4 

• Repair AJAX calls on POI click

Version 9.3.3 

• Use RequestBuilder instead of ConfigurationManager to retrieve extKey

Version 9.3.2 

• Add title parameter to EditPoi VH

Version 9.3.1 

• Bugfix: Remove strict types from ReadOnly Input text element to be in sync with class from core

Version 9.2.1 

• Bugfix: Fallback to "footway", if "road" was not found in OSM response

Version 9.2.0 

• Feature: Add all related foreign records to PoiCollection
• Feature: New SignalSlot to modify related foreign records before adding them to PoiCollection

Version 9.1.0 

• Feature: Allow Info Window for all Map Types

Version 9.0.1 

• Replace "var" with "let" in OpenStreetMap Module JS
• Use same scheme from current request for MapTiles in OpenStreetMap Module JS

Version 9.0.0 

• First version which is compatible with TYPO3 10.
• Removed TYPO3 8.7 compatibility
• Replace Extbase @validate annotations
• Replace Extbase @lazy and @cascade Annotations
• Remove old Form Elements for TYPO3 8.7
• Make use of new ExtensionConfiguration class
• Reduce ext_tables.sql to business columns only
• Use Symfony expressions in TypoScript
• Add strict types where possible
• Adopt UnitTests

Version 8.0.1 

• Restructured GoogleMapsModule JS file to be more compatible with requireJS

Version 8.0.0 

• SignalSlot preIsRecordAllowedToCreatePoiCollectionCatch does not allow returning $isValid as 4th parameter anymore
• Add Message Handling to Map Provider Clients.

Version 7.1.5 

• Catch Exception for TYPO3 8 in ArrayUtility of sysext core.

Version 7.1.4 

• Check FlexForm for each entry before processing them in UpgradeWizard

Version 7.1.3 

• Set previous RenderingContext in edit POI Widget to have access to ViewHelperVariableContainer

Version 7.1.2 

• Do not build Request of foreign extensions, to check, if map should be shown or not.

Version 7.1.1 

• As references can not be passed to call_user_func in SignalSlot Dispatcher, we have to use the SlotReturn value to get new value of isValid.

Version 7.1.0 

• Add possibility to pre-filter records with help of Maps2Registry API before attaching a PoiCollection record
• Add possibility to pre-filter records with help of a SignalSlot before attaching a PoiCollection record
• Update Documentation

Version 7.0.0 

• Remove AjaxController. There is no need anymore after switch to AjaxDispatcher.
• Remove ModifyMarker Ajax Request, as we update position fields in BE form directly.
• Remove all extbase classes from Ajax Calls and switch over to Doctrine
• Update Documentation

Version 6.1.0 

• Option mouseScrollWheelZoom is now available for Google Maps and OpenStreetMap
• All FlashMessages are now created by MessageHelper
• All FlashMessages are now stored in Session

Version 6.0.0 

• Breaking: Removed cacheIdentifier property from all Cache ViewHelpers
• Bugfix: Create better multilingual CacheIdentifier for InfoWindow content.
• Feature: New CacheService to manage CacheIdentifiers and CacheTags
• Task: Remove CacheEntry after storing of PoiCollection in Backend with help of "flushByTag" instead of "remove"
• Update Documentation of Cache ViewHelpers
• Bugfix: Clear InfoWindowContent Cache for our own records, too.

Version 5.3.1 

• Bugfix: Wrong HTML id in AllowMapForm as {data} was not assigned in MapService
• Task: Remove mapHeight und mapWidth from AllowMapForm template

Version 5.3.0 

• Task: Update address in PoiCollection if necessary
• Feature: In AddressHelper you can now check a formatted address against foreignLocationRecord
• Bugfix: Clear Maps2 HTML Cache after a PoiCollection was saved.

Version 5.2.10 

• Bugfix: Repair checkForUpdate in Flexform migration class
• Bugfix: Store FlashMessages in Session for BE context

Version 5.2.9 

• Bugfix again: Do not try to update empty pi_flexform columns in Wizard

Version 5.2.8 

• Bugfix: Do not try to update empty pi_flexform columns in Wizard

Version 5.2.7 

• Bugfix: Add extKey to getConfiguration() settings of maps2 only

Version 5.2.6 

• Documentation: Repair links to Cache VHs and Widget VHs in Documentation

Version 5.2.5 

• Documentation: Better explaination of using Maps2Registry
• Bugfix: Better check to prevent loading session again

Version 5.2.4 

• UniTest: Update secure of slack notification in Travis
• Bugfix: Fill cruser_id with be_user ID if set, else with 0

Version 5.2.3 

• Bugfix: Add compatibility for UpdateWizard in TYPO3 8 and 9

Version 5.2.2 

• Bugfix: Remove quotes from geocode uri
• Bugfix: Disable compression for js files with get parameters
• Bugfix: Re-check, if maps2 cache is initializable in Maps2Registry

Version 5.2.1 

• Bugfix: Correct wrong geocode URIs in ext_conf_template

Version 5.2.0 

• Feature: Show all PoiCollections of a StorageFolder
• Feature: Force set zoom level
• Feature: Add possibility to change Geocode API URI of map providers

Version 5.1.0 

• Make use of initializeArguments in VH Widgets
• Add plugin defaults to TS-Templates
• Correct merging of settings in VH Widgets

Version 5.0.3 

• Repair zoom level settings for OSM

Version 5.0.0 

• Rewritten documentation
• Add new ext_icon as SVG
• Add OpenStreetMap Implementation
• Update various translations
• Add placeholders to style settings in TCA
• Add mapProvider to switch between GM and OSM in Backend
• Add static templates for GM and OSM
• Remove automatic maps2 registry for tt_address

Version 4.3.5 

• Set default of relation columns to 0. strict_type.

Version 4.3.4 

• Check against NULL before unserialize ExtConf

Version 4.3.3 

• Replace deprecated placeIdOnly with setFields in Google Maps JS

Version 4.3.2 

• Implement better record icons

Writing Issues 

• If you find a problem in the extension, please write an issue.
• If you can fix the problem yourself, please submit a pull request. In this case, it is not necessary to create an issue first.

Submitting a Pull Request 

• Please adhere to TYPO3 Coding Guidelines
• For commit messages, please follow the TYPO3 Commit Message Rules

Please see the general GitHub documentation for more information, for example Creating a pull request