Jump to content
ryan

Map Marker Map

Recommended Posts


foreach($ides as $id) {

    echo $pages->get($id);

}

Share this post


Link to post
Share on other sites

You have a list of page ids in the right order direct from the db query, so this should work...

$r=$db->query('SELECT pages_id, ('.$user_location->lng.'-lng)*('.$user_location->lng.'-lng) + ('.$user_location->lat.'-lat)*('.$user_location->lat.'-lat) AS "distance" FROM field_map_location ORDER BY distance');

while($row=$r->fetch_row()){
$loc = $pages->get(row[0]);
echo $loc->id;
}

(Untested and written in browser)

<edit>Soma beat me to it. Again.</edit>

Edited by DaveP

Share this post


Link to post
Share on other sites

uses:

$results=$pages->getById($ides) ;

muches faster!! then get() ones.by one and in.right orders they will.be

  • Like 2

Share this post


Link to post
Share on other sites

I knew it but just wanted to leave some room for improvement so you guys also have something to write.

  • Like 3

Share this post


Link to post
Share on other sites

If you need to retrieve a bunch of pages by ID, then getById() is much better than a foreach with get() simply because getById() does its primary work with one query, whereas get() does at least one query per call. But getById is also one of those things that most people will probably never use (it's largely an internal use thing). As a result, it probably just belongs in the 'advanced' API section. 

Share this post


Link to post
Share on other sites

hi forum!!

i have a problem to output the map it works great in admin when i put the adress marker moves to corect position, but i cant view map in frontend, i use

<?php  echo $page->map;  ?>

but the output is the adress name, not the map.

thank you!

Share this post


Link to post
Share on other sites

Hi Basil,

The module will only output the map data - like the street address and lon / lat values. You will need to add the javascript map code in your template. It's not so hard with google maps - you can read more about how to do this in an earlier post :

http://processwire.com/talk/topic/690-map-marker-fieldtype/page-3#entry31486

Share this post


Link to post
Share on other sites

While this module is being discussed again, has anyone managed to get it to load a default location when first opened (before doing a search).

Currently when you first open the field you see a gray empty map until you do a search. I would like to it to load to a default zoom level and location. For example I am just adding locations in Basel, so I want it to already show Basel, and then the user can just drag and drop the pin to the correct location (without having to do a search). Would be a nicer user experience.

Share this post


Link to post
Share on other sites

thank you Michael i read this but i am so confused that i dont know how to do it, what i try is this:

// //ON THE HEADER I ADD:///      
<style type="text/css">
      html { height: 100% }
      body { height: 100%; margin: 0; padding: 0 }
      #map-canvas { height: 100% }
    </style>
        <script src="https://maps.googleapis.com/maps/api/js?v=3.exp&sensor=false"></script>

 </head>

//// ON THE BODY I ADD: /////
<div class="span4">
       function initialize() {
        var mapOptions = {
          center: new google.maps.LatLng(<?php echo $page->map->address ?>, <?php echo $page->map->lat ?>, <?php echo $page->map->lng ?>,),
          zoom: 8,
          mapTypeId: google.maps.MapTypeId.ROADMAP
        };
        var map = new google.maps.Map(document.getElementById("map-canvas"),
            mapOptions);
      }
      google.maps.event.addDomListener(window, 'load', initialize);
    </script>
</div>

but output is nothing, you see some mistake?

Share this post


Link to post
Share on other sites

maybe you are missing the opening script tag? I can see </script> but not <script> - try adding this after the div class=span4

Share this post


Link to post
Share on other sites

thank you for your help Michael.

no iam sory is there but missed from copy paste here:

<div class="span4">			
			    <script type="text/javascript">
      function initialize() {
        var mapOptions = {
          center: new google.maps.LatLng(<?php echo $page->map->address ?>, <?php echo $page->map->lat ?>, <?php echo $page->map->lng ?>,), 
          zoom: 8,
          mapTypeId: google.maps.MapTypeId.ROADMAP
        };
        var map = new google.maps.Map(document.getElementById("map-canvas"),
            mapOptions);
      }
      google.maps.event.addDomListener(window, 'load', initialize);
    </script>
		</div>

i cant find wats wrong

Share this post


Link to post
Share on other sites

@Basil

Open your javascript console and check for errors.

In your posted code there's one comma too much:

<?php echo $page->map->lng ?>, /*remove this comma*/

Cheers

Share this post


Link to post
Share on other sites

thank you Wanze.. and Michael..

not working i cant see whats wrong

//// IN HEAD I USE/////
     <style type="text/css">
      #map-canvas { height: 100% }
    </style>
    <script type="text/javascript"
      src="https://maps.googleapis.com/maps/api/js?key=HERE IS MY KEY BUT I DELETE FOR SHOW &sensor=true">
    </script>


////// IN BODY IUSE //////
<div id="map-canvas">
     <script type="text/javascript">
      function initialize() {
        var mapOptions = {
          center: new google.maps.LatLng(<?php echo $page->map->lat ?>, <?php echo $page->map->lng ?>),
          zoom: 8,
          mapTypeId: google.maps.MapTypeId.ROADMAP
        };
        var map = new google.maps.Map(document.getElementById("map-canvas"),
            mapOptions);
      }
      google.maps.event.addDomListener(window, 'load', initialize);
    </script>
</div>

Share this post


Link to post
Share on other sites

No problem. Can't help anymore, you should open the javascript console and reload the page.

The console will report if there are any js errors. If you don't know how to fix please post the error message.

Share this post


Link to post
Share on other sites

Dont you need to put the script outside after the div?

  • Like 1

Share this post


Link to post
Share on other sites

I have found in a new 2.3 install that if this Module is present and the site is on a live host (not MAMP) then accessing a page that uses a field of type Map produces this error

2013-04-24 18:25:32	guest	http://example.com/contact/	Error: 	Call to a member function loadPageField() on a non-object (line 651 of /var/www/vhosts/example.com/wire/core/Page.php)

My quick fix is to not use this Module but I would love to solve this so I could proceed and use it in this case and in future.

I am going to do some checking on version numbers locally and on the server and will edit this post/post again but in the meantime if any uber-clever PW friends know why this might be happening I would be very interested as I really wanted to use the Module. Thanks a lot in advance friends, cheers, -Alan

Edit: The server version of PHP is 5.3.5 and I can set my local MAMP version as low as 5.2.17 and the error is still happening on the server and not happening on the local MAMP setup.

Share this post


Link to post
Share on other sites

Alan,

I'm running that Map module on a new 2.3 install and it's working fine. My PHP on MAMP (where it originated) is 5.4.10 and the live server runs 5.3.13 and still no problem.

Cheers

Marty

Share this post


Link to post
Share on other sites

Thanks Marty, yes this is a weird one, I ran out of time last night but I am going to get to the bottom of this one, when I go to login I am also seeing

SESSION : FIELDTYPE 'FIELDTYPEMAPMARKER' DOES NOT EXIST
FIELD : FIELDTYPE 'FIELDTYPEMAPMARKER' DOES NOT EXIST

and there is another thread here about config.php fingerprints or keys created on one server used on another. So I also need to investigate that and perhaps they are related.

Edit: OK well those two were obvious (I need more coffee) the PW install still had a field type of MAP, removed the field and restored the local DB to remote and now the remote does not report the error.

Now to return to trying to figure out why my good hosting seems to cough if there is a field of type MAP...

Edited by alanfluff

Share this post


Link to post
Share on other sites

To see what I could learn about this error I installed a vanilla PW 2.3 directly on the hosting rather than locally and exporting.

So far this method has worked and exporting back to local still works and exporting local back to hosting still works.

Now gradually making the test site more like the site that had the problem (adding modules etc) to see where (if) it trips up.

One thing I have learnt, if I install a Module then export the db and sync files (local to hosting or visa versa) then login on the place I exported to then although I am running with a set of files for all modules and a db that was running with all modules until I actually visit Modules in the PW admin and click check for new Modules (which reports none new are found) the new modules are not listed as installed in Modules Manager. I did not expect this behaviour and don't quite understand it but I will follow this procedure as a work-around (but maybe this is expect behaviour?).

Edit: Perhaps the above behaviour is because I am not copying cache and session folders with the rest of the site when I upload?

Edited by alanfluff

Share this post


Link to post
Share on other sites

Double check that all of your module files in /site/modules/ are getting copied over. I've experienced a similar error on occasion when I copy over a site, but forget that some of my stuff in site/modules/ was actually symlinks to a shared modules directory… and the modules didn't get copied over to the server. 

Also, if you aren't copying over the /cache/ and /session/ folders, then at least make sure that you at least re-create these folders on the server and make sure they are writable. 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Ryan, there will be some slack time soon when I am definitely going to be following up on this so I understand it.

It's very helpful to know about session and cache, I will just copy them all in future I think, I can't even recall why I set them to excluded in my FTP client.

Share this post


Link to post
Share on other sites

I've just pushed some fairly major updates to this module for version 2.0.0: 

  • Add zoom to the data managed by this module. It can be accessed from your field in the same way as address, lat and lng, i.e. $page->map->zoom. It will remember your zoom level setting from the page editor, and it can be used for generating your own maps. 
  • The map settings are now configurable in the field settings (input tab). This includes the starting/default location for the map, map height, default zoom level and map type. 
  • Removed some annoying behaviors from the geocoder. The client-side (javascript) and server-side geocoders no longer try to complete with each other.
  • InputfieldMapMarker is now responsive so that it's input organization is just as usable at mobile resolution. 
  • Addition of a new related Markup module: MarkupGoogleMap. This provides an easy way for you to generate maps with the data managed by FieldtypeMapMarker:
$map = $modules->get('MarkupGoogleMap'); 

// output a map with one marker
echo $map->render($page, 'map'); 

// or output a map with a bunch of markers:
$items = $pages->find("template=something"); 
echo $map-render($items, 'map'); 

This is just a basic usage example. For all options see the README

post-2-0-53342700-1376686680_thumb.png

post-2-0-69616600-1376686687_thumb.png

  • Like 6

Share this post


Link to post
Share on other sites

I don't know why, but this module doesn't work.

It installs right but then when i'm creating new field with type "MapMarker" it isn't creating. It says that 


  • Table 'database.field_googlemap' doesn't exist

I've tried to find SQL in installing function that creates field table. Is it right that "getDatabaseSchema" function is for create new field?

Help me please! :)

Running 2.3.0

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...