Jump to content
ryan

Map Marker Map

Recommended Posts

1 hour ago, PWaddict said:

@mel47 Remove "&callback=initMap" from src and it should be ok.

Oh... Don't know why but I was sure it didn't work if not. Thanks!

Share this post


Link to post
Share on other sites

Hum. Doesn't work all the time. I still have the error message "please add map.google.com script in your document head" even if it's there.

Does something else could interfere? Because in some pages it's works fine.

Share this post


Link to post
Share on other sites

@mel47 On my code I have it like this inside the head section and works perfect:

<script src="https://maps.googleapis.com/maps/api/js?key=<?= $modules->get("FieldtypeMapMarker")->get("googleApiKey") ?>"></script>

 

Share this post


Link to post
Share on other sites

Hi, is there the possibility to have on click to the mark a box with some information? 

Now when I click on the mark I get redirected to a page in the backend. At moment I render the maps in this way:

  <?php
    $map = $modules->get('MarkupGoogleMap');
    $places = $page->Dealer_Finder;
    echo $map->render($places, 'map_rp');
  ?>

I use this because I have a Maps field inside a Repeater Field and I need all mark in one map. All the information I render after the maps  in a loop, I will like show an a part of this info in a box that appears on click to the mark. How I can do this? 

Share this post


Link to post
Share on other sites
On 6/1/2017 at 11:45 PM, Arcturus said:

I'm having an issue in PW 3.0.62 where the module will only geocode an address when I manually click the checkmark between address and lat/lng off/on when editing the page within the admin. Based on what I've read here, it seems only the client-side geocoder is working?

Additional details:

  • I have both Google Maps and Google Places APIs working without issue on the front-end and have added my Maps key to the module's configuration
  • My MapMarker-based field, "map", has a MapMarker: Error geocoding address notification and I can't find any elaboration
  • Neither API has any issues with my address formatting/default address, with an example being 5 Bloor Street, Toronto, ON M4W 3T3
  • My addresses are mapping properly when I play with the checkbox (status goes from UNKNOWN to OK)
  • I can't trigger the geocoding via the API

Any ideas?

 

 

Same problem here, but playing with the checkbox doesn't work either.
Always getting "REQUEST DENIED" and i have absolutely no clue, why.

Any ideas?

  • Like 1

Share this post


Link to post
Share on other sites

Since Google introduced billing for Google Maps I get an error "This page can't load Google Maps correctly" on my maps. I have a working API key and enabled billing, do I need any changes in ProcessWire as well?

Share this post


Link to post
Share on other sites
On 8/6/2018 at 5:50 PM, BFD Calendar said:

Since Google introduced billing for Google Maps I get an error "This page can't load Google Maps correctly" on my maps. I have a working API key and enabled billing, do I need any changes in ProcessWire as well?

Had the same problem... now i switched to the Leaflet Map Version... and im very happy with it 😉 

 

Share this post


Link to post
Share on other sites

Thanks zoeck and Peter. Leaflet also uses Google, so I presume you'll run in the same problem sooner or later, no? For the Here maps, I assume it needs a bit of working under the hood of MapMarker to get it working?

In the mean time it turns out everything now works after 48 hours of patience with Google and my provider (OVH)....

Share this post


Link to post
Share on other sites
On 8/9/2018 at 5:53 AM, BFD Calendar said:

Thanks zoeck and Peter. Leaflet also uses Google, so I presume you'll run in the same problem sooner or later, no? For the Here maps, I assume it needs a bit of working under the hood of MapMarker to get it working?

In the mean time it turns out everything now works after 48 hours of patience with Google and my provider (OVH)....

So what was the fix for MapMarker? Where would we add the API key in PW?

Thanks!

  • Like 1

Share this post


Link to post
Share on other sites
On 8/20/2018 at 5:17 AM, biotech said:

So what was the fix for MapMarker? Where would we add the API key in PW?

Thanks!

In MapMarker's documentation there is a section about implementing the needed JavaScript file from Google:

 

Quote

### How to use

Add this somewhere before your closing `</head>` tag:
`````````
<script type='text/javascript' src='https://maps.googleapis.com/maps/api/js?sensor=false'></script>

Search for this snippet in your template and change the value of src like this:

 

Quote

Where XXXXXX is your API key. See the Hello World example here (lower part of the code example): https://developers.google.com/maps/documentation/javascript/tutorial

Share this post


Link to post
Share on other sites

Thanks Marcus!

I was looking through the module files thinking that we manually need to update files to hold the API key, turns out that our module was out of date as well.

Share this post


Link to post
Share on other sites
On 8/9/2018 at 8:53 AM, BFD Calendar said:

Thanks zoeck and Peter. Leaflet also uses Google, so I presume you'll run in the same problem sooner or later, no? For the Here maps, I assume it needs a bit of working under the hood of MapMarker to get it working?

In the mean time it turns out everything now works after 48 hours of patience with Google and my provider (OVH)....

As far as I know Leaflet use OpenStreetMap which is not google. With the new changes to google maps I'm sure more people will turn to OpenStreetMap so some day with the uptick in usage they may become a pay service as well but not yet.

I should also add I am converting all google maps over to leaflet. It has fewer styling options but looks good and works very well.

Share this post


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

As far as I know Leaflet use OpenStreetMap which is not google. With the new changes to google maps I'm sure more people will turn to OpenStreetMap so some day with the uptick in usage they may become a pay service as well but not yet.

I should also add I am converting all google maps over to leaflet. It has fewer styling options but looks good and works very well.

Well I have over 4500 pages with map references (https://www.birthfactdeathcalendar.net/places/), so converting them to anything else than MapMarker and/or Google should be something that can happen sort of 'all at once'.

Share this post


Link to post
Share on other sites

I use the a FieldtypeMapMarker inside of a repeater field.

Since the update of google api, the map don't display when i open a ne repeater.
I shows only after i save the page.

Is it a problem with the api, the field in combination with a repeater or with the configuration on my site?

Share this post


Link to post
Share on other sites
22 minutes ago, tires said:

I use the a FieldtypeMapMarker inside of a repeater field.

Since the update of google api, the map don't display when i open a ne repeater.
I shows only after i save the page.

Is it a problem with the api, the field in combination with a repeater or with the configuration on my site?

Hi tires,

I think this may be related to a problem I had earlier:

So, you might have to find a way (event, interval, ...) to trigger that init() when your maps becomes visible.

 

Share this post


Link to post
Share on other sites

Thanks for your answer bee8bit!

This code lines are allready in the latest version of the InputfieldMapMarker.js
Or do i have to change this part?

Share this post


Link to post
Share on other sites
On 9/5/2018 at 4:45 PM, tires said:

I use the a FieldtypeMapMarker inside of a repeater field.

Since the update of google api, the map don't display when i open a ne repeater.
I shows only after i save the page.

Is it a problem with the api, the field in combination with a repeater or with the configuration on my site? 

Any further ideas or solutions???

😟

Share this post


Link to post
Share on other sites

The way I was able to solve it, is you have to create 2 different api's. One for the front end, where you set restrictions to your domain name. And then another for this module where you set the restriction to your server's ip address. Also, make sure that geocoding api is enabled in google console.  Hope this helps.

 

 

  • Thanks 2

Share this post


Link to post
Share on other sites

Hi All,

So I am using the InputField MapMarker module to output some google maps onto my web pages. When adding them in the backend, all is well and there are no errors, however on the frontend of the site where I am printing it onto the page, I am getting an error saying "This page can't load Google Maps correctly". Example here: https://www.golfholidays.deence.com/destinations/golf-holidays-in-spain/suites-hotel-san-roque-club/

Looking in the console, is says about either a missing API key (which I have already added in the backend or me hitting my quota which I have raised to well above what is needed in my Google dashboard)

Any help would be appreciated,

Thanks!

Share this post


Link to post
Share on other sites

Fixed by swapping the google maps scripts in the head with this:

<script src="https://maps.googleapis.com/maps/api/js?key=<?= $modules->get("FieldtypeMapMarker")->get("googleApiKey") ?>"></script>

Share this post


Link to post
Share on other sites

Hi

I have a problem that I didn't have before (not sure when was "before" though...). However all last year' pages displayed a correct localization.

If I typed an address, it will not localized until I check/uncheck the geocode true/false. However, saving the page doesn't retain the "ok rooftop" result, and return to "request denied". After a couple of saving pages, I eventually get lat/long saved but the status is still "request denied".

Furthermore, I discovered I can't modify addresses on certain pages (those created by guest (form builder)). It may be related to my similar problem about image undeletable.

Under 3.0.123, both local and production. Google API is enabled for billing. Anyway, address with a previous correct localization are displayed fine.

Thanks!

Share this post


Link to post
Share on other sites

Have a look at your console in Chrome or Firefox. There should be more details telling you what the problem is.

I have had a similiar issue due to a missing setting in Google API Console. 

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...