DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
Administrator manual¶
Target group: Administrators
Installation¶
Import the extension from TER (TYPO3 Extension Repository) like any other extension. Create some pages as shown below.
On the pages Single, Searchform, Autocompleter, Result and Route insert the suitable plugin of the extension. On page Result insert the plugin SearchResult.
On page Feusersmap or on your root page insert Typoscript Include static (from extension) feusersmap. With the constant editor insert the desired settings of the extension like Google maps options, your page ID’s, jQuery options, path to templates etc. Traffic layer and bicycling layer could not be set both at the same time!
You have to get a 2 Google API keys. Name one GoogleBrowserKey and one as GoogleServerKey (for geocoding) from here https://console.developers.google.com and insert them in the constants editor. After fetching the keys you have to activate the Google Maps JavaScript API and the Google Maps Geocoding API. When everything is working (geocoding and map display) you can restrict the browser key with http url and the server key with ip address of the webserver to prevent illegal use of the keys.
The data of the locations and categories is stored in page Data. Insert in the constant editor the correct “Default storage PID” of the locations.
Inserting data¶
If you have supplied the fe_users with correct data for address, city and country, the plugin fetches the coordinates automatically from Google. You can insert your own values for latitude and longitude fields with the TYPO3 list module.
If you don’t insert the icons, the extension uses default icons for the POI’s.
When everything is done you can start a search in frontend.
Reference¶
plugin.tx_feusersmap.view¶
templateRootPath¶
Property
templateRootPath
Data type
string
Description
path to templates
Default
EXT:feusersmap/Resources/Private/Templates/
partialRootPath¶
Property
partialRootPath
Data type
string
Description
path to partials
Default
EXT:feusersmap/Resources/Private/Partials/
layoutRootPath¶
Property
layoutRootPath
Data type
string
Description
path to layouts
Default
EXT:feusersmap/Resources/Private/Layouts/
plugin.tx_feusersmap.settings¶
googleBrowserApiKey¶
Property
Google Browser API Key
Data type
string
Description
Google Browser API key, get one here https://console.developers.google.com
Default
googleServerApiKey¶
Property
Google Server API Key
Data type
string
Description
The Google Server API key is used for geocoding, get one here https://console.developers.google.com
Default
enableTrafficLayer¶
Property
enableTrafficLayer
Data type
boolean
Description
Enables the traffic layer in the map
Default
enableBicyclingLayer¶
Property
enableBicyclingLayer
Data type
boolean
Description
Enables the bicycling layer in the map. Only traffic- or bicyling layer are shown, not both together!
Default
enableStreetView¶
Property
enableStreetView
Data type
boolean
Description
Enables the streetview in the map.
Default
resultPageId¶
Property
resultPageId
Data type
int
Description
Id of the result page, especially when used with ajax search or search form insert the plugin search on the page with this id. Do not use the plugin singleView on this page.
Default
routePageId¶
Property
routePageId
Data type
int
Description
Id of the route page
Default
singleViewUid¶
Property
singleViewUid
Data type
int
Description
Uid of the location record to be shown with the single view plugin
Default
1
singleViewPageId¶
Property
singleViewPageId
Data type
int
Description
Id of single view page
Default
resultLimit¶
Property
resultLimit
Data type
int
Description
Limit the result to n records
Default
300
enableMarkerAnimation¶
Property
enableMarkerAnimation
Data type
int
Description
If set to 1, markers are dropped down to the map
Default
0
enableMarkerClusterer¶
Property
enableMarkerClusterer
Data type
int
Description
If set to 1, markers clusterer are shown (clustered POI’s), especially in ajaxsearch plugin
Default
0
initialMapCoordinates¶
Property
initialMapCoordintes
Data type
string
Description
Initial map coordinates [latitude,longitude]
Default
48,8
defaultZoomLevel¶
Property
defaultZoomLevel
Data type
string
Description
Default zoom level, leave empty for map autozoom, values empty, 1-17
Default
Known problems¶
The extension uses heavily the $(‘….’)-function of jQuery. So, make sure the $-function is available and you do not use the noConflict-mode.
With TYPO3 7.6 there is an issue with templateRootPath.
You can use this Typoscript on the page where the plugin is inserted:
- plugin.tx_feusersmap {
- view {
- templateRootPaths {
- 1 = fileadmin/includes/ext/feusersmap/Resources/Private/Templates/
}
}
}
with TYPO3 7.x, use¶
AjaxSearch¶
Set the Default Storage Pid of the locations in the constant editor.
FAQ¶
Custom templates and files
You can use your own template and CSS file or other jQuery library - just go to the TYPO3 constants editor and change the values for your needs.