Login / Status
developer.Resource
Home . Documentation . Document Library . Extension Manuals
Sponsors
hosted by punkt.deTYPO3 and Open Source MagazineAOE Media

4.8. Administration

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

WEC Map Admin Module

Illustration 21: WEC Map Admin Module

Illustration 21: WEC Map Admin Module

See Illustration 21. The WEC Map Admin Module (1) includes three tools in the dropdown list (2):

  1. Geocode Admin: Displays a list of cached (stored) addresses with their longitude and latitude. Using the pencil icon, the latitude and longitude values can be changed manually. You can also use the Trashcan icon next to each entry to delete the entry completely. If there is a need, it will be automatically regenerated the next time the latitude and longitude is needed for a map. These coordinates come from Google or other geocoding services and are stored locally to decrease the display time of the map. A search box at the top allows the list of caches to be filtered by keyword and the record table can now be sorted by clicking on the table headers.

  2. Batch Geocode: Manually initiates processing of assigning latitude and longitude to any records that support geocoding, including website users. This feature is particularly helpful when there are a significant number of users to process and the WEC Map extension was recently installed. You do not need to run the batch geocode because the WEC Map extension will automatically lookup any needed addresses, but using this feature will avoid long delays in the map display caused by many new geocode lookups. If you have over 100 addresses that must be geocoded, then the processing could take several minutes, but once an address is processed it will not need to be geocoded again unless the address changes.

  3. API Key Settings: Allows you to insert a Google Map API Key directly into the extension to allow global access based on domain. This is useful if you are running a site with different domains. Once you have set API keys for each of your domains, the extension will automatically use the right one depending on the domain the user is visiting or logged in from.

FE User Map Module

Illustration 22: FE User Map Module

See Illustration 22. The FE User Map Module (1) shows a detailed map of all the Frontend Users and is an example of how to use the API in backend development. It works very similar to the Frontend User Map plugin. Zooming in on a user and toggling the information bubble will display the address information for that user along with a link to edit the record directly (2).