Jump to content
Mats

Module: Leaflet Map

Recommended Posts

This is a Leaflet version of Ryans Google Maps marker module.

@Github

  • Like 15

Share this post


Link to post
Share on other sites

Thanks again for the port to leaflet! I prefer OSM over google maps and have been using it for quite some time. Leaflet is very powerful and opens up many possibilities.

I forked Mats' module and added support for leaflet-providers so we can choose different map tile providers (see my post here). It is still a work in progress but seems stable. Once it is ready for production I'll make a pull request.

Mats, do you think we should use leaflet-providers as standard or offer the user a choice whether they want to use it or not?

Next up I will add an icon field and support for Leaflet.awesome-markers.

  • Like 8

Share this post


Link to post
Share on other sites

I think the providers can be a part of the module as long as one can choose from others providers like Mapbox.

Awesome markers support will be awesome!  :)

Share this post


Link to post
Share on other sites

I think the providers can be a part of the module as long as one can choose from others providers like Mapbox.

I agree. Added all available providers to the select dropdown and have set OpenStreetMap.Mapnik as default.

Will post the next days with update on awesome icons...

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for the heads-up!

Since it's a beta i will wait until it's more stable and Marker cluster plug in is compatible with the new version.

Share this post


Link to post
Share on other sites

I just discovered that if I have a Leaflet Map marker field in a template, but leave the lat and long empty in a page, CKEditor text field will not display its toolbar. Must be some JS meltdown.

I left the lat and long empty, because I am populating the map with an array of markers.

It is no problem after I discovered this (just added lat & long values to make it work), but it was quite frustrating at first :)

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the report Beluga. I'll look into it.

Share this post


Link to post
Share on other sites

I notice that this module isn't in the module directory anymore, however I downloaded and installed it a few months ago so I'm using an old version for now. I have a page displaying a map, pulling in multiple locations from child pages and displaying as markers. That all works fine, but I'm wondering if it's possible to change what's included in the marker popup. Currently it just displays the child page title, I'd also like it to include a body field if it has content.

Share this post


Link to post
Share on other sites

@houseofdeadleg

At the moment only the title is supported. You would need to change some code in the module:

https://github.com/madebymats/FieldtypeLeafletMapMarker/blob/master/MarkupLeafletMap.module#L115 -> add another line

'markerBodyField' => 'body',

https://github.com/madebymats/FieldtypeLeafletMapMarker/blob/master/MarkupLeafletMap.module#L192 -> add another line

$body = $options['markerBodyField'] ? $page->get($options['markerBodyField']) : ''; 

https://github.com/madebymats/FieldtypeLeafletMapMarker/blob/master/MarkupLeafletMap.module#L193 -> change line 193 to

$out .= "$id.addMarker($marker->lat, $marker->lng, '$url', '$title', '$body'); ";

https://github.com/madebymats/FieldtypeLeafletMapMarker/blob/master/MarkupLeafletMap.js#L65 -> change line 65 to

this.addMarker = function(lat, lng, url, title, body) {

https://github.com/madebymats/FieldtypeLeafletMapMarker/blob/master/MarkupLeafletMap.js#L98 -> change line 98 to

marker.bindPopup("<b><a href='" + marker.linkURL + "'>" + title + "</a></b><br>" + body);

Then in the template where you render the map, you need to include the markerBodyField in the options that you pass to the render function, e.g.

$options = array();
$options["markerTitleField"] = $page->title;
$options["markerBodyField"] = ($page->body) ? $page->body : "";
// ... more options
$map = $modules->get('MarkupLeafletMap'); 
echo $map->render($items, 'map', $options);

I have not tested this but it should work. Please report back here.

  • Like 3

Share this post


Link to post
Share on other sites

Looking again at my above implementation for additional content in the marker popup feels a bit hacky because the content of the popup is being constructed in MarkupLeafletMap.js

I think the cleaner and proper way of doing it would be to construct the HTML that goes into the popup on the template file level and then pass it to the map render function.

Something like this:

$options = array();
$options["markerPopupContent"] = "<b><a href='{$page->url}'>{$page->title}</a></b>{$page->body}";
// ... more options
$map = $modules->get('MarkupLeafletMap'); 
echo $map->render($items, 'map', $options);

Hope to get your opinion on this. I would then implement the code into my fork of this module.

  • Like 3

Share this post


Link to post
Share on other sites

Been having a play with this using your suggestions above. The first way shows the map and markers, but no content in the markers (and no console errors), the second way the map doesn't show but looking in the code generated all the copy os there but showing an error (SyntaxError: unterminated string literal).

Share this post


Link to post
Share on other sites

@houseofdeadleg

sorry, I don't have the capacity to look into this thoroughly at the moment. I'll try and implement it like described in #11 within the next few weeks.

The unterminated string literal error often happens when strings with line breaks are used in JS variables. So we might need to account for that in the $options["markerPopupContent"] string when passing it to the javascript. Try using

$options["markerPopupContent"] = json_encode("<b><a href='{$page->url}'>{$page->title}</a></b>{$page->body}");

Share this post


Link to post
Share on other sites

When trying to add a new field with this fieldtype I get the following error:

[RED] DB connect error 2006 - MySQL server has gone away
[GREEN] Geocode OK APPROXIMATE: 'Decatur, Georgia'
[GREEN] Geocoded your default address. Please hit save once again to commit the new default latitude and longitude.

after that in the admin it only states The process returned no content.

Any idea how to fix this? Using 3.0.18…

Share this post


Link to post
Share on other sites

Seems to be at database problem. I can't duplicate the issue on my set up (also on 3.0.18).

Can you add other field types without the db issue?

Share this post


Link to post
Share on other sites

When trying to add a new field with this fieldtype I get the following error:

[RED] DB connect error 2006 - MySQL server has gone away
[GREEN] Geocode OK APPROXIMATE: 'Decatur, Georgia'
[GREEN] Geocoded your default address. Please hit save once again to commit the new default latitude and longitude.

after that in the admin it only states The process returned no content.

Any idea how to fix this? Using 3.0.18…

Can you please try that again to see if you continue to get this message?

Share this post


Link to post
Share on other sites

I've a little problem to fix...

I've some fields that provide a complete address and i wanna use a MapMarker field with your module to generate the lat/long of this address entry...so i use a hook to change $page->mapfield->address but this don't work since the generating is triggert by the additional search field on the map....so how could i execute the generation of lat/long?

example hook:

/**
 * change address of the mapmarker field on save
 */
$pages->addHookAfter('saveReady', null, 'addEntry');
function addEntry(HookEvent $event) {
	$page = $event->arguments[0];
	if($page->template != 'eintrag' ) return; //for this template only
	//change the "standort" map marker with the adress data
	$page->standort->address = $page->strasse.' '.$page->hausnummer.', '.$page->PLZ.' '.$page->ort;
}

the address is saved in the mapmarker field right for example: "Examplestreet 5, 123456 Examplevillage"

but like described no generation of lat/long on save from the address field...

Version is 2.0.7 from github

Best regards mr-fan

Share this post


Link to post
Share on other sites

Hi,

i use the MarkupGoogleCalendar module to display events pulled from a google calendar. I would like to display labels for these events on a map. The locations are available as addresses, not as lon/lat pairs.

Is there a way to pass the needed data to the Leaflet module?

Thanks! Ondra

Share this post


Link to post
Share on other sites

I think you are looking for this:

$page->your_mapfield->address

Share this post


Link to post
Share on other sites

@Mats @gebeer Thanks to a job I just finished for @dab I have been actively taking your work forward. I have a fork of the project here that...

005.png

I based my work on gebeer's extension of your repo Mats, so I have issued a pull request to gebeer - but I'd like to get these changes into your repo if possible as then we can revert to your repo as the master codebase and, hopefully, have the latest goodies straight from the PW module directory.

It's now very easy to add fields to the marker pages that let you customise their appearance. Below I have added an Options field, a FieldtypeFontIconPicker and a Text field to control the marker visuals via the added callback.

012.png

If anyone want's to try it out, here is the link to the zip file.

  • Like 13

Share this post


Link to post
Share on other sites

@netcarver A fantastic job, very quickly completed. Nice work :-) !

Share this post


Link to post
Share on other sites

@Mats That would be great - thank you!

Once you pull the changes can I suggest you bump the version number of FieldtypeLeafletMapMarker.

Share this post


Link to post
Share on other sites
On 16/03/2016 at 4:40 AM, gebeer said:

@houseofdeadleg

sorry, I don't have the capacity to look into this thoroughly at the moment. I'll try and implement it like described in #11 within the next few weeks.

The unterminated string literal error often happens when strings with line breaks are used in JS variables. So we might need to account for that in the $options["markerPopupContent"] string when passing it to the javascript. Try using


$options["markerPopupContent"] = json_encode("<b><a href='{$page->url}'>{$page->title}</a></b>{$page->body}");

@houseofdeadleg Gebeer was on the right track when he posted the above. The error is due to the use of single quotes - I ran across it as part of the work I posted about above. If you still want to try the approach gebeer introduced then give this a shot...

$options = array();
$safe_title = str_replace("'", "\'", $page->title);
$safe_title = str_replace("\n", "<br />", $safe_title);
$safe_body  = str_replace("'", "\\'", $page->body);
$safe_body  = str_replace("\n", "<br />", $safe_body);
$options["markerPopupContent"] = "<b><a href=\"{$page->url}\">$safe_title</a></b>$safe_body";
// ... more options
$map = $modules->get('MarkupLeafletMap'); 
echo $map->render($items, 'map', $options);

We have to make sure that no un-escaped single quotes appear in anything we generate that gets inserted via the JS on the page. That also means we have to use escaped double quotes around the link's href attribute. We also have to prevent newline characters getting through that are part of any field - I do that as shown above rather than use the nl2br() method as nl2br prefixes all newlines with <br/> but does not remove the newlines.

Hope that helps!

Edited to add: Forgot to say, with the new version of the module you can just do this...

<?php
$map = $modules->get('MarkupLeafletMap'); 
$options = array(
    'popupFormatter' => function($page) {
        return $page->body;
    }
);
echo $map->render($items, 'your-marker-field-name', $options);
?>

That will append the page body content to the popup window. It also takes care of escaping single quotes and converting newlines into HTML breaks.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...