Jump to content
Mats

Module: Leaflet Map

Recommended Posts

@mr-fan if you are still having the problem from 

with geocoding from your custom fields, maybe my modified InputfieldLeafletMapMarker.js gist can help. I have a custom button in the form that triggers the geocoding, defined on line 48 and a fucntion from line 135 that takes values from custom fields, concats them and does the geocoding.

  • Like 3

Share this post


Link to post
Share on other sites

Thanks i will test asap.

Thanks to netcarver - great addition!

Share this post


Link to post
Share on other sites

I tried this on localhost with a new project. I getting errors in the backend and the map space is white.

Propbably because I am running the backend in https:

http://cdn.leafletjs.com/leaflet-0.7.3/leaflet.css - Works

https://cdn.leafletjs.com/leaflet-0.7.3/leaflet.css - Works not (Firefox security - Invalid certificate)

They advise a different CDN on their homepage, that's maybe why:

Quote

Using a Hosted Version of Leaflet

The latest stable Leaflet release is hosted on a CDN — to start using it straight away, place this in the head of your HTML code:


<link rel="stylesheet" href="https://npmcdn.com/leaflet@0.7.7/dist/leaflet.css" />
<script src="https://npmcdn.com/leaflet@0.7.7/dist/leaflet.js"></script>

or


<link rel="stylesheet" href="https://npmcdn.com/leaflet@1.0.0-rc.2/dist/leaflet.css" />
<script src="https://npmcdn.com/leaflet@1.0.0-rc.2/dist/leaflet.js"></script>

 

Share this post


Link to post
Share on other sites

@ceberlin Could you describe a little more about which version you are trying - Mats', gebeer's or the one I posted? I did have some trouble initially with getting the Leaflet related files in the right place. Having a script blocker running also broke things for me - once I enabled all JS on my local site things started working a lot better.

@Beluga I haven't tried that version - yet. Can't speak for Mats or gebeer. See below.

Share this post


Link to post
Share on other sites

@ceberlin Great to hear that. I've switched my master branch over to Leaflet 0.7.7 from the npmcdn links you posted above. Could you try out the files from the master branch?

Share this post


Link to post
Share on other sites

Thanks for this awesome module!!!

Question: is it possible to remove loading the FontAwesome CSS from the LeafletMapHeaderLines (fe. at the options)? I use FontAwesome on a website and this will lead to that it will be loaded twice.

Best regards

Share this post


Link to post
Share on other sites

@Juergen If you pull the latest version of my master branch you'll be able to exclude the FontAwesome css file by doing the following:

<?php echo $map->getLeafletMapHeaderLines(false); ?>

Edited to add: Actually, you can just replace your copy of MarkupLeafletMap.module with the new one from the repository.

  • Like 2

Share this post


Link to post
Share on other sites
15 hours ago, netcarver said:

I've switched my master branch over to Leaflet 0.7.7 from the npmcdn links you posted above. Could you try out the files from the master branch?

@netcarver Now works well with the standard setup here. Does not work with the HERE map series (I think to remember the v100rc2 beta does).

  • Like 2

Share this post


Link to post
Share on other sites
On 1.8.2016 at 6:05 PM, gebeer said:

I have a custom button in the form that triggers the geocoding, defined on line 48 and a fucntion from line 135 that takes values from custom fields, concats them and does the geocoding.

It would be great to add this to the module with the opportunity to select if you want to use it or not (in the field settings).

Share this post


Link to post
Share on other sites

This may seem simplistic, but how do I make a map where existing fields on the pages define the marker settings? In other words, rather than creating separate new fields on the page template for marker_icon and marker_color (and then laboriously having to fill them in each time), how I can use an existing field, and then merely provide some code denoting the corresponding changes I would like to the marker options. 

For example, for a travel site, each page has a "category" field (sleep, eat, see), and I would like that field to automatically determine the marker color and icon (anything with a category=sleep has marker_color = orange and marker_icon = bed, that sort of thing). 

I got this working on individual pages with "if" statements, but can't seem to get this working within the array needed to populate a map drawing from lots of pages.

Thanks!

Share this post


Link to post
Share on other sites
5 hours ago, Reid Bramblett said:

For example, for a travel site, each page has a "category" field (sleep, eat, see), and I would like that field to automatically determine the marker color and icon (anything with a category=sleep has marker_color = orange and marker_icon = bed, that sort of thing). 

Hi Reid,

Give this a shot. It's a template file that should do what you want if you are using my fork of the Leaflet module.

<!DOCTYPE html><?php

// Create our Leaflet map object. We do it here, before the header output, so we can use it to generate includes in the
// header itself.
$map = $modules->get('MarkupLeafletMap');

?>
<html lang="en">
    <head>
        <meta http-equiv="content-type" content="text/html; charset=utf-8" />
        <title><?php echo $page->title; ?></title>
        <link rel="stylesheet" type="text/css" href="<?php echo $config->urls->templates?>styles/main.css" />
        <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"></script>
        <?php echo $map->getLeafletMapHeaderLines(); ?>
    </head>
    <body>
        <h1><?php echo $page->title; ?></h1>
<?php

            // Extract the pages that will be turned into markers on the map
            $items = $pages->find("<YOUR SELECTOR HERE>"); // Update as needed


            // Setup the options for our map
            $map_options = array(
                // This routine formats the marker icon that gets used on the map.
                'markerFormatter' => function ($page, $marker_options) {
                    switch ($page->category) {   // Update with the fieldname you wish to check as needed
                        // For sleep category markers
                        case 'sleep' :
                            $marker_options['icon'] = 'bed';
                            $marker_options['markerColor'] = 'orange';
                            break;

                        // Add other cases as needed

                        // Here's the default marker setup
                        default :
                            $marker_options['icon'] = 'cutlery';
                            $marker_options['markerColor'] = 'blue';
                            break;
                    }

                    return $marker_options;
                }
            );

            // Generate the HTML and JS that will render the map with a marker for each page in the $items page array
            echo $map->render($items, '<YOUR MAP MARKER FIELDNAME HERE>', $map_options); // Update as needed
        ?>
    </body>
</html>

Please be aware that the icon colours you can choose from are pretty limited. Look at the 'markerColor' row in the table here for your options.

Hope that helps.

Share this post


Link to post
Share on other sites

Beauty, Netcarver. Just the ticket.

(And I had already resigned myself to working with leaflet's limited color palette to approximate the color scheme I'm using on the site.)

Thanks so much for this. Does in a few lines of code what used to take me ages to create by hand. Loving it.

Share this post


Link to post
Share on other sites

@Reid Bramblett

Glad that worked out for you.

@Mats

Thanks for pulling our changes back into your repository - great!  I made a few little tweaks to my repo since you did the merge; any chance of getting them pulled over to your repo as well?

>PS Nice change to your avatar! I like the look of those T-shirts :)

  • Like 3

Share this post


Link to post
Share on other sites

@netcarver Repo is updated. 

Thats's my favourite shirt! :) Thanks for setting up the store. 

  • Like 1

Share this post


Link to post
Share on other sites

Hey guys!
I have a problem with this. When I put the  <?php echo $map->getLeafletMapHeaderLines(); ?> in the header of my template a get a

Error: Call to a member function getLeafletMapHeaderLines() on a non-object (line 34 of /www/htdocs/w00dd152/projekte/fabricius/site/templates/_header.php) 

I have checkt the permissons on the module files, everything is on 777. I also pressed the reload button (as suggested) on the module page in PW but still no luck. Iam running PW 3.0.30 devns

Share this post


Link to post
Share on other sites

thx! I just figured this out, when reading the documentation, I must have missed it.

 

Share this post


Link to post
Share on other sites

is there a trick, when using this with a repeater for multible markers in PW 3?
Here is my code, but thats not working:
 

<?php
$lage = wire('pages')->get("/lage/");
      $items = $lage->map_repeater; 
echo $map->render($items, 'map'); 
                 ?>

Also in the backend, the Address field is not clickable, when I use the Map Field in a Repeater 

Edit: It seems that the files for the module are not loading. I get an error in the console that the files are not loading.

Share this post


Link to post
Share on other sites

@jploch I've never used this in a repeater setup and I'm unsure of your field/template structure from that snippet. How have you actually structured things? What's the field called that holds the map markers?

Regarding the backend, the address is normally a read-only field that is set either by clicking on the magnifying glass in the top-right corner of the map and entering a description or by simply dragging the marker around. Have you tried moving the marker or using the search feature? If they don't work, it is possible there is a problem with some of the JS not loading properly. Please could you launch you browser dev tools and see if any of the JS assets are not loading.

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-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 bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...