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.
Route¶
Author: | Kasper Skårhøj |
---|---|
Created: | 2002-11-01T00:32:00 |
Changed by: | dirk |
Changed: | 2014-10-01T22:34:31 |
Classification: | route |
Description: | Publish your routes with Google Maps or OpenStreetMap. Routes have points of interest (POI). You can categorise and filter both: routes and POI. Address data can geocoded automatically. |
Keywords: | forDevelopers, forIntegrators, route, Google Maps, OpenStreetMap |
Author: | Dirk Wildt, Die Netzmacher |
Email: | http://wildt.at.die-netzmacher.de |
Website: | http://die-netzmacher.de |
Language: | en |
extKey: route
Route¶
TYPO3 with GoogleMaps and OpenStreetMap
Publish your routes with Google Maps or OpenStreetMap. Routes have points of interest (POI). You can categorise and filter both: routes and POI. Address data can geocoded automatically.
Version: 6.0.0, 2014-10-01
Extension Key: route
Language: en
Keywords: forDevelopers, forIntegrators, route, Google Maps, OpenStreetMap
Copyright 2013-2014, Dirk Wildt, Die Netzmacher, <http://wildt.at.die- netzmacher.de>
This document is published under the Open Content License available from http://www.opencontent.org/opl.shtml The content of this document is related to TYPO3 - a GNU/GPL CMS/Framework available from www.typo3.org
Table of Contents¶
Import the official Route Sample 13
Import the official Route Sample 20
SEO – Search Engine Optimisation 22
DRS – Development Reporting System 29
TypoScript Template "Route [1+] dev support" 30
My marker are visible, my paths not. Why? 34
One ore more icons are missing in the map. Why? 34
There isn't any answer. What can I do? 34
AWO Bezirksverband Mittelrhein 36
Screenshots¶
Frontend¶
Routes with GoogleMaps¶
A single Route with Google Maps¶
See: http://typo3-route.de/pfad/historische-und-politische-tour- durch-berlin/
A single route with Open Street Map¶
See: http://typo3-route.de/openstreetmap/pfad/typo3-fahnen-an-tuerme- und-tore-haengen/
Introduction¶
What does Route do?¶
- Route displays routes – paths with marker (POI) – in both interactive
maps:
- Google Maps and
- OpenStreetMap.
- You can categorise and filter both:
- paths and
- marker.
- Route supports
- list views,
- map views and
- single views.
- Route supports a GPX format:
- You can generate the geodata of your route with GPX devices or online with GPX services.
- You can upload a GPX file, Route will convert the data into the needed geocodes.
- Route is calculating the geocoding of any address automatically (by the Google Geocoding API)
- Route is based on BrowserMaps: the map module of the Browser – TYPO3 without PHP.
- Route is improved for the responsive framework Foundation. You can use the framework ready-to-use.
- You can import the official Route sample – ready-to-use.
What do you need?¶
The TYPO3 extensions
Route
Browser – TYPO3 without PHP – from version 6.0
If you are like to install Route stand-alone, you need too:
Organiser Template
Experience with TYPO3
Non supported features¶
Some properties of images aren't supported by the base exension Browser – TYPO3 without PHP from version 6.0.0. This is a matter of TypoScript. If you are familiar with TypoScript you can change the behaviour of each property.
- "In text, left" is handled as "Beside Text, Left"
- "In text, right" is handled as "Beside Text, Right"
- This properties aren't handled:
- "Display as Rows"
- "Caption Alignment"
- "Enlarge on click", "Links (one per line, one link per image)"
- "Border", "Quality and Type", "Effect", "Graphical Frames"
Quick Installation¶
Create a page for publishing your routes
Add the TypoScript template of this extension
Create a folder for the route data
Add the official Route sample by a SQL import and by copying files (recommended)
Or add Browser plugins, route data and files manually.
Manual Installation¶
Extensions¶
Install and enable the extensions
- Browser – TYPO3 without PHP (browser)
:sup:`0
<#sdfootnote1sym>`_ . - Organiser - Template (baseorg)
:sup:`0
<#sdfootnote2sym>`_ – if you like Route stand-alone. - Route (route)
:sup:`0
<#sdfootnote3sym>`_ - SEO Dynamic Tag 2 (seo_dynamic_tag)
:sup:`0
<#sdfootnote4sym>`_ - if you like Search Engine Optimisation (SEO).
Page and Folder¶
Page Route¶
Add a page "Route".
Folder Route data¶
Please add a folder "data".
Your page tree should look like in the illustration below.
By the way: Page tree ids and icons¶
Route icon¶
If you like the Route icon in the page tree, please configure your page route
Modul Web > List
Page tree Select the page route
Edit area Edit the page properties
tab [Appearance]
area "Use as Container", field "Contains Plugin": [Route]
Ids and other icons¶
If you like the page ids within the page tree and some other individual icons, please refer to and install
TSconfig Pages and Users by extManager (tsconf) http://typo3.org/extensions/repository/view/tsconf
TypoScript Template¶
Add a TypoScript template to your page "Route".
Configure:
[General]
- Template Title: "page_route_001" (if the id of the template is 1)
- Constants(copy and paste the TypoScript snippet below, move the page
id 37 to the page id of your Route page)
:sup:`0
<#sdfootnote5sym>`_
// Enable Seo Dynamic Tag 2 for the page route and route records
plugin.tx_seodynamictag.condition.single.begin = globalVar = GP:tx_browser_pi1|routeUid > 0] && [globalVar = TSFE:id = 37
// Enable Seo Dynamic Tag 2 for the page route and marker records
[globalVar = GP:tx_browser_pi1|markerUid > 0]
plugin.tx_seodynamictag.condition.single.begin = globalVar = GP:tx_browser_pi1|markerUid > 0] && [globalVar = TSFE:id = 37
[global]
- [Options] <- is needed for a stand-alone installation only
- Clear: [x] Constants, [X] Setup
- Rootlevel: [X]
- [Includes]
- CSS Styled Content (css_styled_content)
:sup:`0
<#sdfootnote6sym>`_ - Browser [-] Foundation Framework (browser)
:sup:`0
<#sdfootnote7sym>`_ - Organiser Template (baseorg)
:sup:`0
<#sdfootnote8sym>`_ - Browser [1] (browser)
- Route [1] (route)
- CSS Styled Content (css_styled_content)
Import the official Route Sample¶
It is recommended to import the official Route sample. You save a lot of time:
- you don't need to add a lot of stuff manually
- you don't need to configure anything
Please follow the section "Import the official Route Sample" on page 20 below.
Three Browser Plugins¶
TIP: You don't need to install and configure these plugins, if you're following the section "Import the official Route Sample" on page 20 below.
You need to install the Browser plugin three times. No, I'm not kidding... just install the same plugin three times. Each with an individual configuration.
Tasks of each plugin¶
Each plugin has its own task:
- Plugin 1 displays the map in the list view and in the single view
- Plugin 2 displays the path data in text form in the list view and in the single view
- Plugin 3 displays the marker (POI) data in text form in the single view only.
The content of the plugins will displayed or hidden depending of what to show:
Display routes (list view)
- Plugin 1: map with routes – paths and marker (POI)
- Plugin 2: text with paths data
Display one route (single view)
- Plugin 1: map with the selected route – path and marker (POI)
- Plugin 2: text with the path data
Display one marker (POI) (single view)
Plugin 3: map with the marker and text with the marker data
Add the plugins¶
Add three Browser plugins to your page "Route":
[Routes: map]
[Routes: text]
[Marker (POI): map and text (single view only)
[Routes: map]¶
Please set:
[General]
* Header: "[Routes: map]"
* Header > Layout: [Don't display any header]
[Plugin]
* [General]
* Views: [Configured]
* [x] Display only views, which are linked with the current template
* Views: Selected Items: [47676: Route (map only)]
* Views: piVars (parameters in the URL) from foreign plugins: [Handle it]
* Control the plugin: by URL parameters: [enabled]
* Control the plugin: Hide this plugin, if one of ...: "tx_browser_pi1[markerUid]"
* [List View]
* Display Navigation: [ ] Index Browser, [ ] Page Browser
* Search: [Configured]
* Search: Form [ ] Display the form
* [Single View]
* Singe View: [disabled]
* Record Browser: [disabled]
* [Templating]
* HTML: [Browser: Main (browser)]
* [jQuery & AJAX]
* AJAX: [disabled]
[Behaviour]
* Record Storage Page: [Folder with the route data]
* Recursive: [Infinite]
[Routes: text]¶
Please set:
[General]
* Header: "[Routes: text]"
* Header > Layout: [Don't display any header]
[Plugin]
* [General]
* Views: [Configured]
* [x] Display only views, which are linked with the current template
* Views: Selected Items: [47677: Route (text only)]
* Views: piVars (parameters in the URL) from foreign plugins: [Handle it]
* Control the plugin: by URL parameters: [enabled]
* Control the plugin: Hide this plugin, if one of ...: "tx_browser_pi1[markerUid]"
* [List View]
* Display Navigation: [ ] Index Browser, [ ] Page Browser
* Search: [Configured]
* Search: Form [ ] Display the form
* [Single View]
* Record Browser: [disabled]
* [Templating]
* HTML: [Browser: Main (browser)]
* [jQuery & AJAX]
* AJAX: [disabled]
* [Social Media]
* Social Bookmarks: [enabled (I'm using my own HTML template)]
* Bookmarks in list views: "tx_route_path.title"
* Bookmarks in list views Selected Items: Some items of your choice
* Bookmarks in single views: "tx_route_path.title"
* Bookmarks in single views Selected Items: Some items of your choice
[Behaviour]
* Record Storage Page: [Folder with the route data]
* Recursive: [Infinite]
[Marker (POI): map and text (single view only)]¶
Please set:
[General]
* Header: "[Marker (POI): map and text (single view only)]"
* Header > Layout: [Don't display any header]
[Plugin]
* [General]
* Views: [Configured]
* [x] Display only views, which are linked with the current template
* Views: Selected Items: [47677: Route (text only)]
* Views: piVars (parameters in the URL) from foreign plugins: [Handle it]
* Control the plugin: by URL parameters: [enabled]
* Control the plugin: Display this plugin only, if ...: "tx_browser_pi1[markerUid]"
* [List View]
* Display Navigation: [ ] Index Browser, [ ] Page Browser
* Search: [Configured]
* Search: Form [ ] Display the form
* [Single View]
* Record Browser: [disabled]
* [Templating]
* HTML: [Browser: Main (browser)]
* [jQuery & AJAX]
* AJAX: [disabled]
* [Social Media]
* Social Bookmarks: [enabled (I'm using my own HTML template)]
* Bookmarks in list views: "tx_route_marker.title"
* Bookmarks in list views Selected Items: Some items of your choice
* Bookmarks in single views: "tx_route_marker.title"
* Bookmarks in single views Selected Items: Some items of your choice
[Behaviour]
* Record Storage Page: [Folder with the route data]
* Recursive: [Infinite]
Result in the frontend¶
You will receive an empty world map because of missing data.
Data¶
TIP: You don't need to add data manually, if you're following the section "Import the official Route Sample" on page 20 below.
Please insert some sample data.
This order is recommended:
Add categories for your routes and marker (POI)
Add marker (POI)
Add routes
Marker (POI)¶
A marker (POI) needs a latitude and a longitude.
If you add an address, latitude and a longitude will generated automatically. See details at the section "Geocoding" on page 21 below.
Routes¶
A route needs GPX data. You can create this data supported by openrouteservice.org. See details at the section "Get the GPX Data" on page 31 below.
Result in the frontend¶
The result in the frontend depend on your data.
This would be the result with the data of the official Route sample:
Configuration¶
If you like to configure Route for your needs, please use the Constant Editor.
Refer to the categories
- BROWSERMAPS - ...
- ROUTE - ...
See section "Constant Editor" on page 25 below.
Import the official Route Sample¶
Preconditions¶
You must have
- added the page Route and the folder Data – see Page and Folder on page 12 above
- added a TypoScript template – see TypoScript Template on page 13 above
Plugins and Data¶
You can use the sample data of the extension.
Plugins and all Route data will imported.
Be aware: ALL FORMER ROUTE DATA WILL REMOVED!
And sorry: the content of the sample data is in German language only.
Text data:
- Download the file ext_tables_static+adt.sql from:
- Open the sql file with a text editor.
- Replace the pid for the page Route with the uid of the page Route. In the example above the uid is 37.Move '%pidpage%' to '37' – there should be 3 matches.
- Replace the pid for the folder Data with the uid of the folder Data. In the example above the uid is 57.Move '%pidfolder%' to '57' – there should be 17 matches.
- Insert the data with PhpMyAdmin into the tables of your database.
Plugins won't removed, but ALL FORMER ROUTE DATA WILL REMOVED!
- Select your database
- Select [Import]
- Browse for your file (here: ext_tables_static+adt.sql)
- Import the data: [OK]
Files¶
FTP¶
If you have access to your server by FTP only, please follow this steps:
Download the file images.zip from:
Unzip the file.
Upload the content of the folder – it contains images only – to
uploads/tx_route/
SSH¶
If you have access to your server by SSH, you can use these bash commands
www-data:~/uploads/tx_route$ cp ../../typo3conf/ext/route/res/sample/data/images.zip .
www-data:~/uploads/tx_route$ unzip images.zip
www-data:~/uploads/tx_route$ rm images.zip
www-data:~/uploads/tx_route$ mv images/* .
www-data:~/uploads/tx_route$ rmdir images
Features¶
Gallery¶
A click on an image in the single view opens a responsive image gallery.
If you like to use the image gallery, you only have to need to include the static template "Browser [-] Foundation Framework (browser)".
The gallery is part of the responsive framework Foundation. See "Framework Foundation" on page 22 below.
Geocoding¶
Enable geocoding¶
You enable geocoding – the auto update of latitudes and longitudes – in the extension manager.
See
- Category: GEOCODING
- Property: Enabled
at section "Constant Editor" on page 25 below.
The Google API licence¶
If geocoding is enabled, latitude and longitude will updated automatically by the Google API. If you are using the Google API, you have to publish your address data with Google Maps. The free use of the API is limited. For details please refer to the FAQ of the Google API at http://developers.google.com/maps/faq
Maybe this extension doesn't match the requirements of the Google API licence.
Updates by the scheduler¶
If you import data, you can update the geocode of all records by the scheduler.
See details in the manual of BrowserMaps – the map module of the TYPO3-Browser – at
- HTTP: http://typo3.org/extensions/repository/view/browser_tut_map_en
- PDF: http://typo3-browser.de/typo3conf/ext/browser_tut_map_en/doc/ manual.pdf
Look for "scheduler".
GPX file upload¶
You can upload GPX files. See section "Get the GPX Data" on page 31 below.
Mobile¶
You can optimize the map for touch-screens. This allows
- to pan the map with touch gestures on the screen – "touchstart", "touchmove", "touchend" sequences.
- to zoom in with double taps, and to zoom out with two-finger single taps.
This feature is under construction.
Privacy¶
Routes is using interactive maps from the map providers GoogleMaps and OpenStreetMap.
The maps are the background only, your data – paths and marker (POI) – will layed over this background.
This is the cause, why any address data isn't send to the map provider.
Exception¶
If you are using the automatic geocoding, your address data will send to Google (the Google API).
Responsive but the map¶
Framework Foundation¶
Route and the subjacent Browser – TYPO3 without PHP – supports the
responsive framework Foundation :sup:`0
<#sdfootnote9sym>`_ . This
enables a responsive HTML code.
If you like to use this recommended feature, you have to need to include the static template "Browser [-] Foundation Framework (browser)" only. A running jquery library is obligated.
Then test Route with different display sizes.
You can adapt the responsive configuration to your needs. TypoScript enables it. You have to look for the HTML classes "columns" and "rows".
But the map¶
The map isn't responsive. There is some support for touch screens. See "Mobile" on page 21 above.
Sample data¶
Route is provided with sample data. Install the sample and you will save a lot of time!See "Import the official Route Sample" on page 20 above.
SEO Dynamic Tag 2¶
Route is using SEO Dynamic Tag 2 for Search Engine Optimisation. SEO Dynamic Tag 2 supports the canonical tag among other SEO features. You have to configure four lines TypoScript. See section "TypoScript Template" on page 13 above.
SEO – Search Engine Optimisation¶
Route is optimised for search engines. You can configure so called speaking paths and serahc engine optimisation. See section "Real URL" and "SEO Dynamic Tag 2" above.
Live¶
awo-mittelrhein.de¶
natourismus-st.de¶
http://www.natourismus-st.de/die-natourismus-routen/seenroute/karte/
typo3-route.de¶
See section "Screenshots" on page 3 above and on http://typo3-route.de
Reference¶
It is recommended to configure Route by the Constant Editor only and not by the TypoScript Object Browser directly.
Constant Editor¶
BrowserMaps¶
You are controlling BrowserMaps with
Category [BROWSERMAPS – ...]
BrowserMaps – the map module of the TYPO3-Browser – has its own manual. See
Browser Templates¶
Route uses TypoScript templates delivered by the Browser – TYPO3 without PHP. If you like to investigate the configuration, please refer to
Category [BROWSER - TEMPLATES – ...]
Route¶
All properties have the prefix plugin.tx_route.
Example: images.list.position is plugin.tx_route.images.list.position.
IMAGES¶
TIP: If a property hasn't any effect, please refer to the Category [BROWSER - TEMPLATES – LIST - IMAGES ...]
Property
images.list.position
Type
integer
Description
Position in list view.
Possible values:
- 17: In text right.
- 18: In text left.
- 25: Right beside the text.
- 26: Left beside the text.
Default
18
Property
images.list.maxHeight
Type
integer/string
Description
Max height of images in list views
Default
60c
Property
images.list.maxWidth
Type
integer/string
Description
Max width of images in list views
Default
100
Property
images.map.position
Type
integer/string
Description
Position in pop ups
Possible values:
- default: above center
- 1: above right
- 2: above left
- 8: below center
- 9: below right
- 10: below left
- 17: In text right
- 18: In text left
- 25: Right beside the text
- 26: Left beside the text.
Default
26
Property
images.map.maxHeight
Type
integer/string
Description
Max height of images in the pop up of the map
Default
60c
Property
images.map.maxWidth
Type
integer/string
Description
Max width of images in the pop up of the map
Default
60
PATH¶
Property
path.css
Type
string
Description
Path to the CSS file
Default: EXT:route/files/html/css/route.css
Default
see description
Property
path.uploadfolder
Type
string
Description
Path to the upload folder with an ending slash
Deafult: uploads/tx_route/
Default
see description
Setup¶
The TypoScript of Route is configured by the Browser – TYPO3 without PHP – in principle.
If you like to change any behaviour, you have to configure
plugin.tx_browser_pi1.views {
list {
47676 {
...
}
47677 {
...
}
47678 {
...
}
}
single {
47676 {
...
}
47677 {
...
}
47678 {
...
}
}
}
To save code, Route delivers configuration templates at
plugin.tx_route {
map {
...
}
sql {
...
}
}
If you like to configure the map, please refer to the manual of the Browser Map Module – BrowserMaps – at
Restrictions¶
Paths¶
A path must categorised once¶
A path must linked with one category exactly. This is a restriction, because a path is filtered by its category.
If a path hasn't any category
- any path won't displayed in the map
- the map will be empty
Each path must have an unique category¶
It isn't possible to manage more than one path by a filter in the map proper, if more than one path is using the same category.
If more than one path has the same category, and you filter a route by this category, you will get unproper results:
- path will hidden or enabled proper
- but the category icons won't hidden proper.
Example¶
You have the paths:
history, justice, sport
You have the path categories:
city, mountain, sea
Proper relations would be:
- path: history -> category: city
- path: sport -> category: sea
Unproper relations would be
- path: history -> category: city
- path: sport -> category: city
Each path should have its own marker (POI)¶
A Marker (POI) could not filtered proper, if the marker is used by more than one path.
If you hide a path, the marker (POI) of the path will hidden too.
If you need a marker (POI) twice – like a central station – it is recommended to add your marker (POI) twice into your backend table. See "Workflow" below.
Example¶
You have the paths:
history, justice, sport
You have the marker (POI):
Berlin, Moscow, Washington
Proper relations would be:
- path: history -> marker (POI): Berlin, Moscow
- path: sport -> marker (POI): Washington
Unproper relations would be
- path: history -> marker (POI): Berlin, Moscow, Washington
- path: sport -> marker (POI): Washington
Workflow¶
You can avoid this unwanted effect.
If you need the marker (POI) Washington twice, please add Washington twice to your marker (POI) table like
- Washington (history)
- Washington (sport)
Marker (POI)¶
A marker (POI) must linked with one category at least¶
A marker (POI) must linked with one category at least. If not, you will get an error prompt.
A marker (POI) must have a latitude and a longitude¶
A marker (POI) must have a latitude and a longitude :sup:`0
<#sdfootnote10sym>`_ .
The marker (POI) will not displayed, if
- latitude = 0 and longitude = 0
- or latitude = '' and longitude = ''
If you have a marker (POI) located at latitude = 0 and longitude = 0 and you like to display it, please configure
Module: Web > Template
Page tree: Your page, which contains the Browser plugins (in the example above "Route [37]")
Edit area: [Constant Editor]
Category: [BROWSERMAPS – CONTROLLING*]
Property: Empty coordinates?
Categories¶
Categories should have three icons:
- the 1st one for the legend in the form
- the 2nd one for the icon in the map in the list view
- the 3rd one for the icon in the map in the single view
If you like to work with one icon or two icons only, please configure
Module: Web > Template
Page tree: Your page, which contains the Browser plugins (in the example above "Route [37]")
Edit area: [Constant Editor]
Category: [BROWSERMAPS – ICONS]
Properties:* Position of legend icon* Position of map icon (list view)* Position of map icon (single view)* Position of text icon
Icons¶
See "Categories" above.
Debugging¶
If you have any unexpected result, you can inspect Route supported by the DRS – the Development Reporting System – in the TYPO3 backend.
DRS – Development Reporting System¶
Inspect work-flow and errors¶
The DRS – Development Reporting System – enables you
- to follow the work-flow of Route,
- to inspect alternate configuration possibilities,
- to inspect unproper configuration and
- it prompts warnings and errors
Enabling the DRS¶
Module: Admin Tools > Extension Manager
Edit Area: Select the Browser (!) extension
Tab [Configuration]
Category: [Debugging]
DRS – Development Reporting System: [BrowserMaps]
[Update]
The DRS report¶
Precondition
You need the extension
Extension Development Evaluator (extdeveval)
Report
Module: Admin Tools > Development Log
Edit Area: the report
TypoScript Template "Route [1+] dev support"¶
This template will display in the list view 47676 some values for
- tx_route_path
- tx_route_path_cat
- tx_route_marker
- tx_route_marker_cat
Please include this template additonally.
This values are for development only.
Get the GPX Data¶
If you don't want to generate the needed geo data – a list of lon-lat- pairs – manually, you can generate a GPX data file online and upload it to Route.
Workflow¶
Online service¶
You can generate the optional GPX file online at
You can collect the needed GPX data by mouse clicks.
The service is without any fee.
Download¶
Insert the address of the starting point
Set the starting point
Insert the address of the ending point
Set the ending point
Calculate the path
Download the GPX file
Upload¶
Upload the downloaded GPX file
Save the form
Route will convert the GPX data to the needed geodata and insert it into the field [Geodata].If the field contains data, this data will overwrote.
You will get a success prompt
XML structure¶
If you like to upload an optional GPX file, the file needs this XML structure:
track
track segment
track point with attributes
- lon
- lat
Example:
<?xml version="1.0" encoding="UTF-8"?>
<gpx>
<trk>
<trkseg>
<trkpt lon="13.380236" lat="52.516422"/>
...
<trkpt lon="13.3789391" lat="52.513531"/>
</trkseg>
</trk>
</gpx>
This structure is supported by http://openrouteservice.org/
What's new?¶
6.0¶
Responsve Image Gallery¶
[6.0.0]
A click on an image in the single view opens a responsvie image gallery. See "Gallery" on page 21 above.
Responsive Framework Foundation ready-to-use¶
[6.0.0]
All Route templates are improved for the responsive framework
Foundation :sup:`0
<#sdfootnote11sym>`_ . See "Framework
Foundation" on page 22 above.
Search Engine Optimisation¶
[6.0.0]
You can optimise
- Route meta tags and
- Route URL
for search engines. See
- "Real URL" on page 22 above and
- "SEO Dynamic Tag 2" on page 22 above.
1.2¶
Backend: evaluation of relations¶
[1.1.5]
If an editor saves a route record (path, marker (POI) and category), the Browser – TYPO3 without PHP – evaluates the relations. If there is an unproper relation, the editor will get a prompt.
You need the Browser – TYPO3 without PHP – from version 4.8.x.
Backend: search fields¶
[1.1.5]
All tables got the needed configuration (TCA) for search fields. The search is possible for all tables now in backend forms.
CSS: class for form labels¶
[1.1.5]
The category table got a new field. See [Category] > field: CSS class for the the label tag in the map form.
If you don't want to display a certain category in the form of the map, you can add the css class "nodisplay" fo example. You have to configure .nodisplay in you css stylesheet of course.
CSS: icons get a pointer by default¶
[1.1.4]
The marker icon and the path icon get a pointer by default.
FAQ¶
My Map is empty. Why?¶
Please check, if your paths match the requirements. See section "Paths" on page 27 above.
My marker are visible, my paths not. Why?¶
Maybe you are using OpenLayers moduls with an unproper order. OSM.Routes must be the first element!
Please check the Constant Editor
- Category [BROWSERMAPS – OPENLAYERS]
- Properties
- Map +Routes modules
- Map +Routes modules (debugging)
One ore more icons are missing in the map. Why?¶
Please check
- If your categories have a proper latitude and longitude.See section "A marker (POI) must have a latitude and a longitude" on page 28 above.
- If your categories have enough icons.See section"Icons" on page 28 above.
There isn't any answer. What can I do?¶
Route is based on BrowserMaps – the map module of the TYPO3-Browser. BrowserMaps has its own manual. See
- HTTP: http://typo3.org/extensions/repository/view/browser_tut_map_en
- PDF: http://typo3-browser.de/typo3conf/ext/browser_tut_map_en/doc/ manual.pdf
Route has forum. You are welcome to post any question. See "Forum" on page 38 below.
Updates¶
From < 6.0¶
Include the static template again.
Include the Browser template Foundation.
The list of included templates should be look like:
- CSS Styled Content (css_styled_content)
- Browser [-] Foundation Framework (browser)
:sup:`0
<#sdfootnote12sym>`_ - Browser [1] (browser)
- Route [1] (route)
Credits¶
AWO Bezirksverband Mittelrhein¶
The German Arbeiterwohlfahrt (AWO) Bezirksverband Mittelrhein has contracted a part of automatic geocoding and optimization for touch- screens.
Made in Nature¶
The German TYPO3 agency Made in Nature has contracted
- a part of the initial release
- a part of the upgrade for TYPO3 6.2
See
Further Information¶
TYPO3 forge¶
Get the latest developer version at
Other extensions published by Die Netzmacher¶
- +AOE Linkhandler Configurator: Configure the AOE linkhandler supported by userinterfaces. Out-of-the-box templates for cal, org, tt_news and tt_products. Don't edit page TSconfig any longer. http://typo3.org/extensions/repository/view/linkhandlerconf/
- autositemap: A smart site-map optimised for the footer. It groups menus in columns. Great menus will get two columns. Configuration is based on TypoScript HMENU. http://typo3.org/extensions/repository/view/autositemap/
- Browser – TYPO3 without PHP. Develop your TYPO3 extension 8 times faster! You need one line TypoScript for a result list with a search form, a record browser and an index browser. Images are wrapped self-acting. SEO, Search Engine Optimization, is integrated. http://typo3.org/extensions/repository/view/browser/
- Caddy – the TYPO3 shopping cart. You can use it for your own needs. You need a database with products or any other items only. You can install Caddy out of the box with one mouse click – see Quick Shop below. http://typo3.org/extensions/repository/view/caddy/
- Deal! – TYPO3 Quick Shop interface for the marketplace ebay. Manage all items with TYPO3 and publish it on ebay. Amazon is under construction. http://typo3.org/extensions/repository/view/deal/
- Flip it! offers lovely and smooth page flip transitions. It enables you to run over pages in PDF documents like in a real magazine. It is based on flash. Flipt it! can convert PDF documents to swf files automatically. http://typo3.org/extensions/repository/view/flipit/
- Green Cars (Grüne Autos) - Database optimized for ecological cars. It is a case study and demonstrates, how to get a complex database with the browser (see above) in three hours only. http://typo3.org/extensions/repository/view/green_cars/
- Jobmarket is a catalogue with job offers. Views, the a-z-browser, the page-browser, the search, social bookmarks and a lot of other stuff can configured by the Browser plugin with the mouse. Job Market hasn't any PHP code, it should be easy to adapt it to your needs. http://typo3.org/extensions/repository/view/job_market/
- Majordomo: For subcribing to and unsubscribing from a majordomo mailing list. http://typo3.org/extensions/repository/view/majordomo/
- Organiser – TYPO3 for the lobby and the organisers. Handle news, events, staff, headquarters, locations, workshops and a calendar with one extension. Sell online tickets! Install the Organiser with one mouse click! http://typo3-organiser.de/
- Quick Shop – the fastest shop in the history of TYPO3. Install it with one mouse click! Quick Shop is based on the browser (see above) and powermail. http://typo3-quick-shop.de/
- PDF Controller: Easy to install. Add to your HTML page the PDF-controller-button. Link from the button to the controller. Adjust the controller by mouseclicks. The PDF Controller supports CSS 3. http://typo3-pdfcontroller.de/
- Radial Search (Umkreissuche) – Enable the browsing through your data by geo location. 'Your data must have a latitude and a longitude. Address data can geocoded automatically by the Browser - TYPO3 without PHP. http://typo3.org/extensions/repository/view/radialsearch/
- Route – Publish your routes with GoogleMaps or OpenStreetMap. Routes have points of interest (POI). You can categorise and filter both: routes and POI. Address data can geocoded automatically. http://typo3.org/extensions/repository/view/route/
- seo_dynamic_tag: Search Engine Optimization for the title tag, the canonical tag and the meta tags author, description and keywords. Configuration by a user interface. http://typo3.org/extensions/repository/view/seo_dynamic_tag/
- TSconfig Pages and Users by extManager (extkey: tsconf): Configure the the eight most commonly used TSconfig porperties with the mouse - like page tree uids, activated extended view, activated clipboard, ... http://typo3.org/extensions/repository/view/tsconf/
Illustration Index¶
Illustration 1: Route list view with google maps 3
Illustration 2: Route single view with google maps 4
Illustration 3: Route single view with open street maps 5
Illustration 4: TYPO3 Route with records for paths, marker and categories 6
Illustration 5: TYPO3 Route record with the images tab 7
Illustration 6: Upload your GPX data! TYPO3 Route will update the geodata field automatically. 8
Illustration 7: TYPO3 Route calculate the geocoding of your address automatically. 9
Illustration 8: Route pages 12
Illustration 9: Result in the frontend 18
Illustration 10: Result in the frontend with the sample data 19
Illustration 11: Enabling the Development Reporting System 29
Illustration 12: The DRS report enables you to follow the work-flow of Route 30
Illustration 13: OpenRouteService.org 31
Illustration 14: Upload GPX file 32
Illustration 15: Upload GPX file 32
Change Log¶
6.0.0 Major Feature * #61939: Make TypoScript clear: Different files instead of one file* static removed: Mind manual update!* #61911: Upgrade TYPO3 6.2* Integration of 4.x-Extensions fixed for 6.2* cps_tcatree Feature * #61998: Template for SEO Dynamic Tag 2* #61937: Links depending on record type: record, page, noType, urlSee #61938 at Browser Improvement * #i0009: Corporate Design Bugfix * #61926: ###MAP### marker in html template is moved from inner ###LISTBODY### to outer###LISTBODY###(See browser ChangeLog too)* #52544: mysql_real_escape_string(): Can't connect to local MySQL serverSolved. See: #61520
1.2.5 Improvement * #i0008: manual: three plugins
1.2.4 Improvement * #i0007: Description of the extension with link to the manual
1.2.3 Bugfix * #i0006: Bugfix manual
1.2.1 Improvement * #52899: Properties name and category must have a different value
1.1.5 Features * #54575: Evaluate Backend tables route* #54550: TCA search fields* #54548: CSS class for form lables Improvements * #i0005: showUid in single views removed (because showUid has an effect in list views only)
1.1.4 Improvements * #53204: bodytext fields in select query* #53205: CSS: marker icon and route icon should get a pointer in every case
1.1.2 Improvements * #i0004: Update Manual
1.1.1 Features * #i0003: Sample data
1.1.0 Features * #51644: Automatic geocoding* #i0002: Sample GPX data
1.0.0: Initial release
0 See: http://typo3.org/extensions/repository/view/browser from version 6.0. Browser Manual is required.
0 See: http://typo3.org/extensions/repository/view/baseorg from version 6.0. Automaketemplate is required.
0 See: http://typo3.org/extensions/repository/view/route from version 6.0
0 See: http://typo3.org/extensions/repository/view/seo_dynamic_tag
0 You don't need to configure constants, if you aren't using Seo Dynamic Tag 2
0 CSS Styled Content: in case of a stand-alone installation
0 Browser Foundation Framework: is needed only, if you like to use a responsive Route installation.
0 Organiser Template: in case of a stand-alone installation
0 Latitude and longitude will generated automatically, if you add an address
0 If yolu like to use the responsive framework Foundation.
41