Gmaps (Google Maps) Fieldtype

Introduction

Gmaps Fieldtype has been deprecated in favor of the Maps module. See https://addons.reinos.nl/maps-fieldtype

The official FieldType extension for the Gmaps module. Simply modify your Map from within your entry.

title

Documentation versions

Installation

Prerequisites

Make sure your system meets the minimum requirements:

Installation Instructions

  1. Upload ee2/system/third_party/gmaps_ft to system/expressionengine/third_party/
  2. Upload ee2/system/themes/third_party/gmaps_ft to themes/third_party/
  3. Install the module in Add-Ons → Modules

Update instructions

  1. Backup the Files and the Database
  2. Remove all the old Gmaps Fieldtype files (both system and themes)
  3. Place the new files in the right folders
  4. Navigatie to the module page and hit the update trigger button

EE support

As of version 3.0.0 of EE, Gmaps for EE2 will not be extended with new features, but only with bugfixes. The EE2 Docs can be found here

License

For every paid addon you need to validate your license in order to activate the module.

On a local environment, like *.dev *.local *.localhost *.test the license is valid for testing and building a new or existing sites. For every other domain, you need to have a valid license.

Process of validating

Once installed, you will asked to enter your license key. When you entered a valid license you can hit the "Save license" button. This will start validating your license and will redirect you to addons.reinos.nl to login into your account. You can also register a new account in this process.

Control panel overview

Once logged in, you are asked to use your current account or to login with another one.

Control panel overview

Using the current logged in account, the server will check all info related to your license and once valid, it will redirect you back to your site where you see either a success message or an error message.

Control panel overview

License field

This module is using a license field to check if the license for the module is valid or not. On addons.reinos.nl you can check your license and add your valid domains.

Control panel overview

In the Module CP you can enter then your license Control panel overview

When you enter a wrong license, the module will not work and it shows you an warning Control panel overview

Invalid license

Sometimes it happens that the license system says you have an invalid license. When this happens, make sure you have entered your domain url in your account, next to your license on addons.reinos.nl.

If this will not fix your license problem, please contact us on https://addons.reinos.nl/support

Migration tool

With the migration tool, you can convert you data from the old "Google Maps for ExpressionEngine" to the "Gmaps Fieldtype".

important: before starting, make sure you make a backup of your old data, in case of failure.

The Gmaps Field

Once Gmaps FT is installed, you can add a Gmaps field to the Publish page by following these steps:

Publish page overview

When the custom field is created, you can see the Gmaps FT in action on the publish field

title

From here you can start adding markers, customize markers, search addresses and customize the map settings.

Editing Maps setting

To modify the settings for the Map, you can click in the top right on the 'map settings' button.

title

Search an address

To search an address, you can enter an address in the search form. If there is any result, they will be show below the form. From here you can add the address also to the map by clicking the plus sign.
The Reverse Geocode latlng option can be used to disable reverse geocoding on Latlng coordinates. This can be handy when you have an exact latlng, that does not match any streetname, city etc...

title

Refresh the map

In some situations you mess up your map and you want to reset it. With the refresh map button, you can refresh your map to the saved version.

Reset the map

To simply reset/remove all your data on your map, just click the reset map button

Adding Markers (and others)

To add a marker, simply right click on the map. Now there will be a menu appear, where you can click on 'Add marker'.

title

Edit Markers (and others)

When you added some markers to your map, you can edit the markers by clicking on the edit icon in the top. Please notice that when you hover on the marker button in the top, the marker on the map will bounce so you can see which marker you are editing.

title

Removing markers (and others)

To remove the marker, you can click in the top on the delete icon. Or you can right click on a marker in the gmaps.

Field Tag

To show your created map, you can put your custom field tag inside a {exp:channel:entries} loop. This will show your map that you created from within the CP.

{your_custom_field}

To modify the map (like the map style or anything else) you can use the power of the Gmaps module. Simply extend your tag with some params from the {exp:gmaps:map} method

{your_custom_field width="100%"}

Please make sure you add the {exp:gmaps:init} to your template to include the necessary files

Tag params

The following tags are filled in from the entry self; map_type map_types latlng marker:icon:url marker:title

Tag Variable

Below are the Tag Variables. Those Variables can be used in the tag described above

marker:n:latlng

Show the latlng of one marker.

{your_custom_field:marker:n:latlng}

marker:latlng

Show all latlng positions with pipeline`s

{your_custom_field:marker:latlng}

marker:n:title

Show the title for one marker

{your_custom_field:marker:n:title}

marker:title

Show all titles with pipeline`s

{your_custom_field:marker:title}

marker:n:icon

Show one icon

{your_custom_field:marker:n:icon}

marker:icon

Show all icons with pipeline`s

{your_custom_field:marker:icon}

route:from

Show the from latlng for use in the route function

{your_custom_field:route:from}

route:stops

Show the stops latlng for use in the route function

{your_custom_field:route:stops}

route:to

Show the to latlng for use in the route function

{your_custom_field:route:to}

has:markers

Variable that check if there is any marker set

{gmaps_field_extension:has:markers}

markers

Loop over the Markers

{gmaps_field_extension:markers}...{/gmaps_field_extension:markers}

markers:add_marker

Generate a {gmaps:add_marker} code from the gmaps module. Place this inside a {exp:gmaps:map}....{/exp:gmaps:map} to the same marker to a front-end map.

{gmaps_field_extension:markers}{add_marker}{/gmaps_field_extension:markers}

1

markers:lat

The lat of the marker

{gmaps_field_extension:markers}{lat}{/gmaps_field_extension:markers}

markers:lng

The lng of the marker

{gmaps_field_extension:markers}{lng}{/gmaps_field_extension:markers}

markers:title

The title of the marker

{gmaps_field_extension:markers}{title}{/gmaps_field_extension:markers}

markers:icon

The icon of the marker

{gmaps_field_extension:markers}{icon}{/gmaps_field_extension:markers}

markers:content

The content of the infowindow

{gmaps_field_extension:markers}{content}{/gmaps_field_extension:markers}

markers:count

Holds the current number, started from 1

{gmaps_field_extension:markers}{count}{/gmaps_field_extension:markers}

markers:abs_count

Holds the current number, started from 0

{gmaps_field_extension:markers}{abs_count}{/gmaps_field_extension:markers}

markers:total_results

Show the total numbers of markers

{gmaps_field_extension:markers}{total_results}{/gmaps_field_extension:markers}

polyline:n:from

Get the from latlng form the n polyline

{gmaps_field_extension:polyline:1:from}

polyline:n:stops

Get the stops (latlng pipline seperated) from the n polyline to convert it to the route method

{gmaps_field_extension:polyline:1:stops}

polyline:n:to

Get the to latlng form the n polyline

{gmaps_field_extension:polyline:1:to}

polyline[OPTIONAL:N]

Loop over the polyline positions, where N is the number of the polyline created.

{gmapsfieldtype:polyline[OPTIONAL:1]}
    {stroke_color}
    {stroke_opacity}
    {stroke_weight}
    {path}
        {lat}, {lng}
    {/path}
{/gmapsfieldtype:polyline[OPTIONAL:1]}

polygon[OPTIONAL:N]

Loop over the polygons, where N is the number of the polygon created.

{gmapsfieldtype:polygon[OPTIONAL:1]}
    {stroke_color}
    {stroke_opacity}
    {stroke_weight}
    {fill_color}
    {fill_opacity}
    {path}
        {lat}, {lng}
    {/path}
{/gmapsfieldtype:polygon[OPTIONAL:1]}

circle[OPTIONAL:N]

Loop over the circles, where N is the number of the circle created.

{gmapsfieldtype:circle[OPTIONAL:1]}
    {stroke_color}
    {stroke_opacity}
    {stroke_weight}
    {fill_color}
    {fill_opacity}
    {lat}
    {lng}
    {radius}
{/gmapsfieldtype:circle[OPTIONAL:1]}

rectangle[OPTIONAL:N]

Loop over the circles, where N is the number of the circle created.

{gmapsfieldtype:rectangle[OPTIONAL:1]}
    {stroke_color}
    {stroke_opacity}
    {stroke_weight}
    {fill_color}
    {fill_opacity}
    {bounds}
        {lng}
        {lng}
    {/bounds}
{/gmapsfieldtype:rectangle[OPTIONAL:1]}

map

Get all map variables

{gmapsfieldtype:map}
    {map_types}
    {map_type}
    {zoom_level}
    {scroll_wheel}
    {zoom_control}
    {zoom_control_style}
    {zoom_control_position}
    {pan_control}
    {pan_control_position}
    {map_type_control}
    {map_type_control_style}
    {map_type_control_position}
    {street_view_control}
    {street_view_control_position}
    {google_overlay_html}
    {google_overlay_position}
    {center}
{/gmapsfieldtype:map}

Channel Form

The Gmaps Fieldtype is fully compatible with Channel Form

EE2

for EE2 users, include this snippet to make the channel form work

$('#[ID-OF-YOUR-CHANNEL-FORM] input[type="submit"]').click(function(){
    $('.gmap_holder').each(function(){
        EE_GMAPS_FT.save_settings($(this));
    });
});

Limit Access

You can set for different functions the access level based on the membergroup on the field setting page.

Access

Supported

The Fieldtype supports the following modules and extension

Content Elements

{exp:gmaps:init}

{exp:channel:entries entry_id="1" dynamic="no"}
    {ce_field}
        {gmaps_fieldtype}
               {value}
        {/gmaps_fieldtype}
    {/ce_field}
{/exp:channel:entries}

Webservice

The Gmaps Fieldtype supports all methods of the Entry API.

To import a new data map via the Entry API, you have to use the following data structure.

array('gmaps_field' => array(
    'markers' => array(
        array(
            'lat' =>'52.3909176',
            'lng' =>'6.049638',
            'title' => 'test',
            'icon' => null
        )
    ),
    'map' => array(
        'map_type' => 'roadmap',
        'map_types' => array(
            'hybrid',
            'roadmap',
            'satellite',
            'terrain'
        )
    ),
    'polylines' => array(),
    'polygons' => array(),

));

Extra params bug

At the moment it is not possible to use enters in your custom field like below;

{custom_field
   param1=""
   param2=""
   param3=""
}

Instead of that you have to use it the following way;

{custom_field param1="" param2="" param3=""}

See also http://expressionengine.stackexchange.com/questions/10726/custom-field-with-params-and-enters or https://support.ellislab.com/bugs/detail/19434

Hooks

gmaps_fieldtype_save_data

(added in v3.0.8)

 ee()->extensions->call('gmaps_fieldtype_save_data', $data, $entry_id, $field_id);

Changelog

4.1.5 (05-08-202020)

4.1.4 (05-11-2018)

4.1.3 (09-06-2018)

4.1.2 (20-04-2018)

4.1.1 (11-04-2018)

4.1.0 (09-04-2018)

*Note: you need to add your license key and license email from addons.reinos.nl in order to validate your license and add a valid domain url in your license field on addons.reinos.nl/profile/licenses or the module will not work on a live site. Also make sure you have read the license section in the documentation

4.0.1 (02-04-2018)

4.0.0 (04-12-2017)

3.4.6 (01-11-2017)

3.4.5 (16-08-2017)

3.4.4 (26-07-2017)

3.4.3 (02-06-2017)

3.4.2 (30-05-2017)

3.4.1 (07-04-2017)

3.4.0 (27-03-2017)

3.3.0 (18-01-2017)

3.2.0 (23-11-2016)

3.1.1 (11-11-2016)

3.1.0 (04-04-2016)

3.0.10 (25-08-2016)

3.0.9 (11-08-2016)

3.0.8 (01-08-2016)

3.0.7 (14-07-2016)

3.0.6 (11-07-2016)

3.0.5 (20-06-2016)

3.0.3 (06-06-2016)

3.0.2

3.0.1

3.0.0

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.3

2.0.2

2.0.1

2.0

1.8

1.7

1.6.3

1.6.2

1.6.1

1.6

1.5.2

1.5.1

1.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4

1.3

1.2.3

1.2.2

1.2.1

1.2

1.1.1

1.1

1.0