EXT: WEC Map¶

Table of Contents¶

`Introduction <#__RefHeading__12808_1279719766>`_ `3 <#__RefHeading__12808_1279719766>`_

`A. Welcome <#__RefHeading__12810_1279719766>`_ `3 <#__RefHeading__12810_1279719766>`_

What is the Web-Empowered Church? 3

`B. About this Manual <#__RefHeading__12814_1279719766>`_ `3 <#__RefHeading__12814_1279719766>`_

`C. How to Use this Manual <#__RefHeading__12816_1279719766>`_ `3 <#__RefHeading__12816_1279719766>`_

`Overview <#__RefHeading__12818_1279719766>`_ `4 <#__RefHeading__12818_1279719766>`_

`A. What does it do? <#__RefHeading__12820_1279719766>`_ `4 <#__RefHeading__12820_1279719766>`_

`B. Screenshots <#__RefHeading__12822_1279719766>`_ `4 <#__RefHeading__12822_1279719766>`_

`Installation <#__RefHeading__12824_1279719766>`_ `5 <#__RefHeading__12824_1279719766>`_

`Step 1: Import and Install the wec_map Extension <#__RefHeading__12826_1279719766>`_ `6 <#__RefHeading__12826_1279719766>`_

`Step 2: Add the WEC Map Static Templates <#__RefHeading__12828_1279719766>`_ `6 <#__RefHeading__12828_1279719766>`_

`Step 3: Add the WEC Map Plugin to a Page <#__RefHeading__12830_1279719766>`_ `8 <#__RefHeading__12830_1279719766>`_

`Upgrade Instructions <#__RefHeading__12832_1279719766>`_ `9 <#__RefHeading__12832_1279719766>`_

`Configuration <#__RefHeading__12846_1279719766>`_ `9 <#__RefHeading__12846_1279719766>`_

`Configuring the WEC Simple Map Plugin <#__RefHeading__12848_1279719766>`_ `9 <#__RefHeading__12848_1279719766>`_

`Configuring the WEC Frontend User Map Plugin <#__RefHeading__12850_1279719766>`_ `13 <#__RefHeading__12850_1279719766>`_

`Configuring the WEC Table Map Plugin <#__RefHeading__12852_1279719766>`_ `15 <#__RefHeading__12852_1279719766>`_

`Advanced Configuration with TypoScript <#__RefHeading__12854_1279719766>`_ `17 <#__RefHeading__12854_1279719766>`_

Simple Map TypoScript Reference 19

FE User Map TypoScript Reference 21

Table Map TypoScript Reference 23

`Customizing the info bubble <#__RefHeading__12862_1279719766>`_ `26 <#__RefHeading__12862_1279719766>`_

`Customizing a Table map <#__RefHeading__4984_1827206915>`_ `27 <#__RefHeading__4984_1827206915>`_

`Customizing a PDF-view <#__RefHeading__12864_1279719766>`_ `28 <#__RefHeading__12864_1279719766>`_

`Troubleshooting <#__RefHeading__12866_1279719766>`_ `29 <#__RefHeading__12866_1279719766>`_

`Administration <#__RefHeading__12868_1279719766>`_ `29 <#__RefHeading__12868_1279719766>`_

WEC Map Admin Module 30

FE User Map Module 30

`Using the WEC Map API <#__RefHeading__12874_1279719766>`_ `32 <#__RefHeading__12874_1279719766>`_

`Create the Map Object <#__RefHeading__12876_1279719766>`_ `32 <#__RefHeading__12876_1279719766>`_

`Map Object Reference <#__RefHeading__12878_1279719766>`_ `32 <#__RefHeading__12878_1279719766>`_

`Marker Object Reference <#__RefHeading__12880_1279719766>`_ `33 <#__RefHeading__12880_1279719766>`_

`Create Markers <#__RefHeading__12882_1279719766>`_ `34 <#__RefHeading__12882_1279719766>`_

Available methods 34

Marker Manager 40

`Hooks <#__RefHeading__12888_1279719766>`_ `40 <#__RefHeading__12888_1279719766>`_

WEC Table Map Marker Hook 40

WEC Map API Center and Zoom Hook 41

`Drawing the Map <#__RefHeading__12894_1279719766>`_ `41 <#__RefHeading__12894_1279719766>`_

`Change Log <#__RefHeading__12896_1279719766>`_ `41 <#__RefHeading__12896_1279719766>`_

A. Welcome¶

Welcome to the adventure of doing ministry through technology!

This manual is written for those who are interested in using Web- Empowered Church (WEC) technology and enhancing their website through the use of the WEC Map extension. The WEC Maps extension has been designed to provide churches and ministries an opportunity to display maps on their website...maps to the church, maps to events, even maps that show how many members live in the surrounding towns.

B. About this Manual¶

This guide is organized into four main sections:

Overview: What the WEC Map extension does, how it works, and what you can expect from the rest of the manual.

Installation: How to install the WEC Map extension and how to get it running on your website.

Configuration: How to configure the WEC Map extension and plugins for maximum impact on your website.

Advanced: How to modify the extension through TypoScript and other advanced functions.

Please note: not all screenshots have been updated yet.

C. How to Use this Manual¶

✔ To help make sense of the material on the following pages, we’ve used a few icons in the margin to highlight certain information.

T |img-1| ip : Tips are bits of information that are good to know. They may offer shortcuts to save you time or even make your website better.

N |img-2| ote : These notes are similar to tips, but usually contain information you should pay attention to. It might be details about a step that a whole operation hinges on or it may highlight an essential sequence of tasks.

C |img-3| aution : These notes draw your attention to things that can interrupt your service or website if not done correctly. Some actions can be difficult to undo.

T |img-4| echnical Stuff : These notes will explain how stuff works. If you want to know why certain steps are necessary or are just looking for a fuller explanation, these notes should help answer your questions.

I |img-5| nternet Link : These links will guide you to a website page that will demonstrate How-To do something or link you to more advanced information on the http://webempoweredchurch.com or http://typo3.org websites.

A. What does it do?¶

The Web-Empowered Church Map Extension provides an interface for placing maps from Google on a TYPO3-based website. There are two actual plugins provided with the WEC Map extension.

The Simple Map Plugin allows you to show a single address, such as your church address, on a Google map. See Illustration 1. However, by adding TypoScript to configure the WEC Map extension, you can add multiple addresses and multiple markers (see Marker Manager ).

The Frontend Users Map Plugin allows you to show multiple locations on a map. These locations are drawn from a list of Frontend Users and can be limited to a particular Frontend Users Group. See Illustration 2. This provides you with the opportunity to map the location of off-site small groups, multiple site campuses, or even member addresses. A security option is available so that names and addresses can be hidden if desired. When the security option is enabled, only the city, state, and country for each user is located on the map to hide the specific locations of Frontend User addresses.

B. Screenshots¶

Illustration 1: Simple Map

Illustration 2: Frontend Users Map

Illustration 3: Table Map

Step 1: Import and Install the wec_map Extension¶

To import and install the WEC Map extension, you must be logged in to your website's TYPO3 Backend and have administrative privileges.

Full instructions for uploading and installing extensions can be found in the How-To located on the Web-Empowered Church website: http://webempoweredchurch.com/support/howtos/ . (Use wec_map in your repository search).

wec_map uses additional JavaScript-libraries that cannot be included because of license reasons. If you want to host these files on your own server, you can download them optionally. Go to the WEC Map Admin -module, select “Download JS-Files” and click on “Download”.

Go to the Extension Manager, select wec_map . Activate “Use downloaded JS-files from Google...”.

If you don't use this option, the files are includes from their original source.

Step 2: Add the WEC Map Static Templates¶

I

Illustration 4: Adding the WEC Map Static Template 1

n order for the WEC Map extension to display, the WEC Map Static Template should be added to the page template where the Map extension is installed. For most websites, this will mean adding the Static Template to the Root Page; however, if you have created a unique page template for the map page, you may need to add the Static Template there instead. Refer to Illustration 8. Using the Template Module ( 1 ), click on the page where the page template is located--typically, the Root page ( 2 ). In the far right drop-down box, select Info/Modify ( 3 ). Click the Click here to edit the whole template record link ( 4 ).

R

Illustration 5: Choose the Static Template/s

efer to Illustration 9. Click on the Includes tab ( 5 ). In the Include Static field, scroll down the Items list and select any or all of the Map's Static Templates: WEC Table Map, WEC Frontend User Map, and/or WEC Simple Map ( 6 ) depending on the plugin(s) you intend to use. Save and close the form.

Step 3: Add the WEC Map Plugin to a Page¶

The WEC Map extension can be added to any page as a standard Content Element . However, at this time there can only be one instance of the Map plugin on any single page. If you need to show multiple maps we suggest adding additional pages with one map per page.

To add the WEC Map plugin to a page:

Refer to Illustration 10. Using the Page Module ( 1 ), select the page from the page tree where you'd like to place the map (

Illustration 6: Adding the WEC Map Plugin to a Page

2 ). Add a Content Element in the Content Container of your choice (

3 ).

Tip: You can add the WEC Map plugin, or any Content Element to a Content Container by selecting the Create New Element icon These icons will appear wherever you are allowed to add content such as images, text, or additional plugins.

Illustration 7: Selecting the WEC Map Plugin

Refer to Illustration 11. Scroll down the content form and select which of the three WEC Map plugins you'd like to use ( 4 ).

This will complete the installation of the WEC Map plugin on your page. The WEC Map FlexForm that will appear corresponds to either the WEC Simple Map Configuration or the WEC Frontend User Map Configuration .

Configuring the WEC Simple Map Plugin¶

The WEC Simple Map plugin is used to display a single location on the map such as your church or ministry address. To configure the plugin, use the Page Module and select the page where you've installed the plugin. Then click the Edit Icon (the pencil) associated with the WEC Simple Map plugin. This will open the plugin's FlexForm.

T |img-1| ip: When working with a plugin, the General Tab contains a number of generic fields. it is generally helpful to write the plugin's name or some other descriptive title in the Header field ( 1 ). This makes it easier to select which plugin you want to edit when a page contains multiple Plugin Content Elements . To prevent the header from displaying on the page, change the Header Type to Hidden ( 2 ).

Refer to Illustration 12. Note that there are three Tabs in the Flexform. The first tab, labeled Address prompts you for a description of the address to be mapped, as well as the address

Illustration 8: Configuring the Plugin's General Tab

itself. It will also show the status of finding the coordinates for the address entered (geocoding) at the end.

R

Illustration 9: The Simple Map Display Tab

efer to Illustration 13. The second tab, labeled “Map Details,” requests display information about the map, such as the height and width.One of the enhanced features of the Map extension is that if you enable the Show Directions Tab , Frontend users will have the option to be given directions to and from the location shown on the map. In addition, if they are a registered Frontend user and have logged in, if you have enabled the Prefill Address from User Info , their address will be automatically applied to the directions fields and the user can immediately click for Directions To or From the mapped location.

Caution: In order for the marker balloon information to be visible, avoid setting the height value at less than 400 pixels.

Illustration 10: The Simple Map Controls Tab

Refer to Illustration 14. The third tab, labeled “Map Controls,” allows you to specify which map controls should be shown on the map. Options include the size of the map controls (pan and zoom) if any, whether an overview map is desired, whether a scale should be included, and the map type selection control (satellite, political, or a hybrid of the two). See Illustration 15 for a visual description of these controls.

After saving this form and viewing its

Illustration 11: Map Controls

page in the Frontend, a map will be generated similar to Illustration 1 , depending on the Map Controls you have chosen to display. Configuring the WEC Frontend User Map Plugin --------------------------------------------

The WEC Frontend User Map plugin is used to display a map of all users or all users belonging to one or more Frontend Users Groups. To open the plugin, use the Page Module and select the page where you've installed the plugin. Then click the Edit Icon (the pencil) associated with the WEC Frontend User Map plugin. This will open the plugin's FlexForm.

T |img-1| ip: When working with a plugin, it is generally helpful to write the plugin's name or a descriptive title in the Header field (under the General tab). This makes it easier to select which plugin you want to edit when a page contains multiple Plugin Content Elements . To prevent the header from displaying on the page, change the Header Type to Hidden .

Refer to Illustration 16.

Illustration 12: The Frontend User Map Details Tab

Note that there are two tabs The first tab, labeled “Map Details” prompts you for the following:

Width and Height: The default size of the Frontend map is 500px by 500px. You can change the map size to suit the look and feel of your website here. In order for the marker balloon information to be visible in the Frontend, avoid setting the height value below 400 pixels.

• S

  |img-21| **Illustration 13: Frontend Users Map With and Without Sensitive Geocoding**

  ensitive geocode (no address): Checking this box prevents the map markers from displaying at the precise location of the user address and hides the detailed address information. Instead, Frontend users are shown by city, state, and country; and multiple users in the same city are totaled. (See Illustration 17 for examples of each.)

• Initial Map Type: Specifies which map type to show initially. “Normal” will show the street map (default), Satellite will show satellite images, and Hybrid will show satellite images with streets overlayed.

• Show Written Directions: Displays an addition tab in the marker popup with two forms to get direction from or to the current location via maps.google.com. Directions are disabled if “Sensitive geocode” is enabled above, no matter the setting here.

• Show Radius Search: Displays a Search form that, when completed, will display all markers within a specified radius (10–250 miles) of a user-supplied address. The appropriate markers are listed in the sidebar. When clicked in the list, they open the marker.

• Show Marker Sidebar: Displays the usernames as links to the markers of those in the FE user groups that you've selected.

• Prefill Address from User Info: If directions are enabled, this will automatically fill in a logged in FE user's address information into the directions form.

• Filter by FE user group: This is the key component to the Frontend Users Map plugin. Select the Frontend User Group(s) you would like to include on your map. You may create custom Users and User Groups as necessary to display the locations of a multi-site campus, locations of local churches, small groups, etc. (For information on how to add Frontend Users, see www.webempoweredchurch.com/support/howtos/ ).

• Startingpoint: Select the pages/folders where FE user groups are stored. Typically, this would be the site's main Storage Folder, but you choose different or additional folders as desired.

Map Controls Tab. R

Illustration 14: Frontend User Map Controls Tab

efer to Illustration 18. The third tab, labeled “Map Controls,” allows you to specify which map controls should be shown on the map. Options include the size of the map controls (pan and zoom) if any, whether an overview map is desired, whether a scale should be included, and the map type selection control (satellite, political, or a hybrid of the two). See Illustration 15 for a visual description of these controls.

After saving this form and viewing its page in the Frontend, a map will be generated in a similar to Illustration 2, depending on the Map Controls you have chosen to display.

Configuring the WEC Table Map Plugin¶

The WEC Table Map plugin is used to display a map of all users or all users or locations associated with specified tables such as the Calendar Base locations table, etc. To open the plugin, use the Page Module and select the page where you've installed the plugin. Then click the Edit Icon (the pencil) associated with the WEC Table map plugin. This will open the plugin's FlexForm.

Tip: When wo rking with a plugin, it is generally helpful to write the plugin's name or a descriptive title in the Header field (under the General tab). This makes it easier to select which plugin you want to edit when a page contains multiple Plugin Content Elements . To prevent the header from displaying on the page, change the Header Type to Hidden .

Illustration 15: Configuring the Table Map's Address Tab

Refer to Illustration 19. Note that there are three tabs The first tab, labeled “Address” prompts you for the following:

• Tables to map data from: The items in this list are auto-generated from any extension that has the WEC Map extension enabled. Click on a table to highlight (select) it. Hold down the Control (Mac=Apple) key to make multiple table selections.
• KML to overlay: You can include KML files to customize markers. For an introduction to KML files, see Google's tutorial at http://code.google.com/apis/kml/documentation/kml_tut.html . Add your own KML files by uploading them using the Filelist module and then adding a WEC Map External Resource record to the Map page or a Storage Folder page using the List module and pointing the resource to the uploaded KML's url (fileadmin/images/myKMLfile.kml).
• Startingpoint: Select pages that contain the tables you want mapped by clicking on the file folder icon. For instance, if you want your calendar's location table to be included, select the page that contains the calendar's location records.
• Recursive: Select how many subpage-leves you want mapped.

Se

Illustration 16: Configuring the Table Map Details Tab

e Illustration 20.

Width and Height: The default size of the Frontend map is 500px by 500px. You can change the map size to suit the look and feel of your website here. In order for the marker balloon information to be visible in the Frontend, avoid setting the height value below 400 pixels.

• Initial Map Type: Specifies which map type to show initially. “Normal” will show the street map (default), Satellite will show satellite images, and Hybrid will show satellite images with streets overlayed.
• Show Written Directions: Displays an addition tab in the marker popup with two forms to get direction from or to the current location via maps.google.com. Directions are disabled if “Sensitive geocode” is enabled above, no matter the setting here.
• Show Radius Search: Displays a Search form that, when completed, will display all markers within a specified radius (10–250 miles) of a user-supplied address.
• Show Marker Sidebar: Displays the usernames as links to the markers of those in the FE user groups that you've selected.
• Prefill Address from User Info: If directions are enabled, this will automatically fill in a logged in FE user's address information into the directions form.

Map Controls Tab. Refer to Illustration 18. The third tab, labeled “Map Controls,” allows you to specify which map controls should be shown on the map. Options include the size of the map controls (pan and zoom) if any, whether an overview map is desired, whether a scale should be included, and the map type selection control (satellite, political, or a hybrid of the two). See Illustration 15 for a visual description of these controls.

After saving this form and viewing its page in the Frontend, a map will be generated in a similar to Illustration 3, depending on the Map Controls you have chosen to display.

Advanced Configuration with TypoScript¶

The WEC Map extension can be configured using standard TypoScript and FlexForms. Example TypoScript is provided below for both plugins . Note that for the WEC Simple Map, which is referred to as “tx_wecmap_pi1” in the TypoScript, you can either specify the address in parts or as one string. By using TypoScript to configure this plugin you can also set more than one marker to appear on the map. The WEC Frontend User Map extension is referred to as “tx_wecmap_pi2.”

plugin.tx_wecmap_pi1 {
        height = 500
        width = 500
        showDirections = 1
        prefillAddress = 0
        initialMapType = G_SATELLITE_MAP
        controls.mapControlSize = small
        controls.showOverviewMap = 1
        controls.showMapType = 1
        controls.showScale = 1
        markers.1 {
                                title = TS title
                                description = TS desc
                                street = 1234 Happy Place
                                city = Happy City
                                zip = 12345
                                state = HS
                                country = Happy Country
        }
        markers.2 {
                title = Another title
                description = Another description
                address = 1234 Another Happy Ave, Happy City, HS 12347, Happy Country
        }
        markers.3 {
                #add another marker here
        }
}

plugin.tx_wecmap_pi2 {
        height = 500
        width = 500
        showDirections = 1
        prefillAddress = 0
        initialMapType = G_HYBRID_MAP
        controls.mapControlSize = large
        controls.showOverviewMap = 1
        controls.showMapType = 1
        controls.showScale = 1
        userGroups = 2,3,5
        pid = 2,3,5
}

Customizing the info bubble¶

Customizing the info bubble of the maps is possible by using TypoScript. The relevant default configuration for the plugins looks as follows:

plugin.tx_wecmap_pi1.marker {
        title = COA
        title {
                10 = TEXT
                10.field = name
                10.wrap = <h1>|</h1>
        }
        description = COA
        description {
                10 = COA
                10 {
                        10 = TEXT
                        10.field = address
                        10.wrap = | <br/>

                        20 = TEXT
                        20.field = city
                        20.wrap = |,

                        30 = TEXT
                        30.field = zone
                        30.wrap = | &nbsp;

                        40 = TEXT
                        40.field = zip
                }
                10.wrap = <p>|</p>

                20 = TEXT
                20.field = phone
                20.wrap = <p>|</p>
        }
}

Changing the content of the info bubble is now only a matter of adding, removing, or changing the content objects. For example, to add the image of a user and the web address to the info bubble of the WEC FE User Map plugin, add the following snippet to the plugin's TS setup:

plugin.tx_wecmap_pi2.marker.description.10 {
  50 = IMAGE
  50.file.import = uploads/tx_srfeuserregister/
  50.file.import.override.field = image
  60 = TEXT
  60.field = www
}

Customizing a Table map¶

Configure the infobubble for your record of your DB-table tx_myext (DB-fields mytitle and mydesc) with TypoScript:

plugin.tx_wecmap_pi3.flexformTables.tx_myext {

//  where = some SQL conditions
//  limit = 10

  icon {
    iconID       = myIconID
    imagepath    = fileadmin/myicon.png
    shadowpath   = fileadmin/myshadow.png
    width        = 16
    height       = 16
    shadowWidth  = 25
    shadowHeight = 25
    anchorX      = 0
    anchorY      = 0
    infoAnchorX  = 5
    infoAnchorY  = 1
  }

  title = COA
  title {
    10 = TEXT
    10.field = mytitle
    10.wrap = <h4> | </h4>
  }

  description = COA
  description.10 {
    10 = TEXT
    10.field = mydesc
  }
}

Suppose your record for your DB-table tx_myext contains the fields mylat/mylong for the coordinates your $TCA to map your DB-fields looks like this:

$TCA['tx_myext']['ctrl']['EXT']['wec_map'] = array (
    'isMappable' => 1,
    'latlongFields' => array (
            'lat' => 'mylat',
            'long' => 'mylong',
    ),
);

If you want to display a map in the DB editing tx_myext-records you have to setup the following lines:

$geocodeTCA = array (
    'tx_wecmap_geocode' => array (
            'exclude' => 1,
            'label' => 'LLL:EXT:wec_map/locallang_db.xml:berecord_geocodelabel',
            'config' => array(
                    'type' => 'user',
                    'userFunc' => 'tx_wecmap_backend->checkLatLongStatus',
            'params' => array (
              'latlongFields' => array(
                    'lat' => 'mylat',
                    'long' => 'mylong',
              ),
            ),
            ),
    ),
);

t3lib_extMgm::addTCAcolumns('tx_myext', $geocodeTCA, 1);
$TCA['tx_myext']['interface']['showRecordFieldList'] .= ',tx_wecmap_geocode';
t3lib_extMgm::addToAllTCAtypes('tx_myext', 'tx_wecmap_geocode', '1', 'after:mylat');

$mapTCA = array (
    'tx_wecmap_map' => array (
            'exclude' => 1,
            'label' => 'LLL:EXT:wec_map/locallang_db.xml:berecord_maplabel',
            'config' => array (
                    'type' => 'user',
                    'userFunc' => 'tx_wecmap_backend->drawLatLongMap',
            'params' => array (
              'latlongFields' => array(
                    'lat' => 'mylat',
                    'long' => 'mylong',
              ),
            ),
            ),
    ),
);

t3lib_extMgm::addTCAcolumns('tx_myext', $mapTCA, 1);
$TCA['tx_myext']['interface']['showRecordFieldList'] .= ',tx_wecmap_map';
t3lib_extMgm::addToAllTCAtypes('tx_myext', 'tx_wecmap_map', '1', 'after:tx_wecmap_geocode');

Illustration 17: Editing a BE-record

In the BE you can either edit the coordinates by the numeric input fields or by simply dragging the marker to the correct position.

Customizing a PDF-view¶

If you are using a PDF-view of your page the wec_map-plugins have to be switched to static-mode as extensions like pdf_generator2 aren't able to execute the JavaScripts of wec_map. You can achieve this automatically by using the following TypoScript:

# special handling for PDF-generation
[globalVar = GP:type={$extension.pdf_generator2.typeNum}]

   # switch wec_map to static maps
   plugin.tx_wecmap_pi1.static {
      enabled = 1
      mode = force
   }
   plugin.tx_wecmap_pi2.static < plugin.tx_wecmap_pi1.static
   plugin.tx_wecmap_pi3.static < plugin.tx_wecmap_pi1.static
[global]

Responsive Design¶

For a responsive web-design add the following CSS-rule to your stylesheet:

.tx-wecmap-map {
    width: 100% !important;
}

Integration into EXT:cal¶

The calendar cal can display wec_map right out of the box.

Enable the use of wec_map in cal's constant editor or set the TypoScript constant plugin.tx_cal_controller.view.location.showMap = 1

Add markers ###MODULE__LOCATIONLOADER### and ###LOCATION### in yourevent_model.tmpl, if you're using an own HTML-template.

Adapt module_locationloader.tmpl for your needs, if you're using an own HTML-template. ###MAP### will be replaced by the wec_map.

To display the map in any other view than the location-view use the following TypoScript:

view.{view}.{object}.showMap = 1

and all the map settings too:
view.{view}.{object}.map {
        # Map configuration goes here
}

So to get it working in an event view you should copy the TS to:

view.event.event.showMap = 1
view.event.event.map {
        # Map configuration goes here
}

Troubleshooting¶

In Internet Explorer 7 (IE7), when using the FE User Map plugin in the Backend, occasionally a slow server connection will cause an error when adding a new Frontend User in your Storage Folder.

Internet Explorer cannot open the site http://www.yoursite.com/typo3/alt_mainOperation aborted.

To work around this issue, open the Ext Manager Module , and ensure you can view Loaded extensions . Scroll down to the WEC Map extension and click on the WEC Map link (the words). Uncheck the Enable map in FE user records and then click the Update button .

Some users who have large numbers of Frontend User records may discover that many of their users do not receive geocoding from Google. This issue may be caused because of your host server's firewall that interprets multiple geocoding requests and replies from Google.com as a Denial of Service Attack.

To work around this issue, contact your host and ask them to whitelist google.com for your domain.

Sometimes the marker bubbles appear to be empty or appear to be missing either a title or a description. The reason for that is the font color used for headlines and body text across the whole website. If either is set to white font color, it will also render the headlines and/or body text white, making the marker bubbles appear empty. To fix it, make sure you change the CSS style for the map element fonts ; it uses the class “tx-wecmap-map”, so you could add the following to your CSS styles file:

.tx-wecmap-map {color: black;}
.tx-wecmap-map p {color: black;}

The Typo3-internal XHTML-cleaning messes up the generated JavaScript. Please disable xhtml-cleaning:

config.xhtml_cleaning= 0

If you are using a script-compressor like scriptmerger you must exclude the wec_map JavaScript-files from being merged:

plugin.tx_scriptmerger {javascript { enable = 1 merge.ignore = markermanager.js,infobubble.js,wecmap.js}}

Administration¶

Nested within the Subsection Tools Directory, there are two Backend Modules associated with the WEC Map extension.

Create the Map Object¶

The first step in using the WEC Map API is to create a map object. To do that, include the Google Maps class in your code and create an instance of it, passing the API key and the map's height and width as parameters. If the API Key was set through the WEC Map Admin, the value can be left blank.

include_once(t3lib_extMgm::extPath('wec_map').'map_service/google/class.tx_wecmap_map_google.php');
$className = t3lib_div::makeInstanceClassName("tx_wecmap_map_google");
$map = new $className($apiKey, $width, $height);

Map Object Reference¶

addMarkerIcon

$iconData = array(
  'iconID'       => 'default',
  'imagepath'    => 'typo3conf/ext/wec_map/images/mm_20_red.png',
  'shadowpath'   => 'typo3conf/ext/wec_map/images/mm_20_shadow.png',
  'width'        => 12,
  'height'       => 20,
  'shadowWidth'  => 22,
  'shadowHeight' => 20,
  'anchorX'      => 6,
  'anchorY'      => 20,
  'infoAnchorX'  => 5,
  'infoAnchorY'  => 1
);

addKML

setRadius

setCenter

setCenterByAddress

showInfoOnLoad

setMaxAutoZoom

enableStatic

Marker Object Reference¶

Create Markers¶

Hooks¶

Drawing the Map¶

Rendering of the map is simple. Just call the drawMap() method on the Map objectand it will return the HTML and Javascript necessary to display the map within a Frontend Plugin or Backend Module:

$output = $map->drawMap();

Change Log¶

See CHANGELOG file in the extension directory.

EXT: WEC Map - 41Modified 02/2013