Jump to content
ryan

Map Marker Map

Recommended Posts

1 hour ago, bernhard said:

yes, it is: https://www.google.com/search?q=change google map colours

should be very easy using their readymade styles: https://snazzymaps.com/

Yeah I know it's possible. I've already did on a map without using this module. I should be more specific.

On a map without using this module I used this js to change the colors:

var styles = [
  {
    "stylers": [
      { "hue": "#c1d72e" }
    ]
  }
];

So the proper question is how can I apply the above code on a map using this module? 

Share this post


Link to post
Share on other sites

just don't use the modules render() method and write the code on your own. you should know how to do that as you say you already did it without the module ;)

you have all the necessary field data in these variables:

echo $page->map->address;   // outputs the address you entered
echo $page->map->lat;       // outputs the latitude
echo $page->map->lng;       // outputs the longitude
echo $page->map->zoom;      // outputs the zoom level

you can also just copy the generated markup of your render method and then adjust the necessary (parts of your) scripts.

Share this post


Link to post
Share on other sites
2 hours ago, bernhard said:

just don't use the modules render() method and write the code on your own. you should know how to do that as you say you already did it without the module ;)

you have all the necessary field data in these variables:


echo $page->map->address;   // outputs the address you entered
echo $page->map->lat;       // outputs the latitude
echo $page->map->lng;       // outputs the longitude
echo $page->map->zoom;      // outputs the zoom level

you can also just copy the generated markup of your render method and then adjust the necessary (parts of your) scripts.

I've copied my code from an older website I've created a map with changed colors without using the module and it doesn't even load the map on the website I'm currently developing. It's driving me crazy...

window.onload = function () {

			var latlng = new google.maps.LatLng(12.3456789, 12.3456789);

			var styles = [
  {
    "stylers": [
      { "hue": "#c1d72e" }
    ]
  }
];

			var myOptions = {
				zoom: 17,
				center: latlng,
				mapTypeId: google.maps.MapTypeId.ROADMAP,
				disableDefaultUI: true,
				styles: styles
			};

			map = new google.maps.Map(document.getElementById('map'), myOptions);
			
			var myCenter = new google.maps.LatLng(12.3456789, 12.3456789);
    var myIcon = new google.maps.MarkerImage(
    "https://chart.googleapis.com/chart?chst=d_map_pin_letter&chld=%E2%80%A2|c1d72e",
    new google.maps.Size(24,30),
    new google.maps.Point(0,0),
    new google.maps.Point(12,23)
    );
 
 
    var marker = new google.maps.Marker({position: myCenter, icon: myIcon, map: map});

On the 2nd method you proposed I don't know how to apply the code to change the color.

If anyone managed to change the colors with this module PLEASE let me know how you dit it. Thanks.

Share this post


Link to post
Share on other sites

i would suggest doing the following:

  • create a new template file for your page that holds the map data with exactly the code from the google example (javascript + html): https://developers.google.com/maps/documentation/javascript/examples/map-simple?hl=de
  • change nothing but your api-key.
  • when you view this page you should see the same map as on the google docs page.
  • replace the fixed values for lat/lng/zoom by those saved in your processwire site. see my example above ($page->map->lat...)
  • view your page, it should show the map at the position that you specified in your backend
  • change your style by adding the styles options (see code below)
  • view your page, you should see the new style
  • if everything works, try to implement your map in your original template file
var map;
function initMap() {
  map = new google.maps.Map(document.getElementById('map'), {
    center: {lat: -34.397, lng: 150.644},
    zoom: 8, // add comma here
    styles: [
  {
    "stylers": [
      { "hue": "#c1d72e" }
    ]
  }
]
  });
}

 

  • Like 3

Share this post


Link to post
Share on other sites
14 hours ago, bernhard said:

i would suggest doing the following:

  • create a new template file for your page that holds the map data with exactly the code from the google example (javascript + html): https://developers.google.com/maps/documentation/javascript/examples/map-simple?hl=de
  • change nothing but your api-key.
  • when you view this page you should see the same map as on the google docs page.
  • replace the fixed values for lat/lng/zoom by those saved in your processwire site. see my example above ($page->map->lat...)
  • view your page, it should show the map at the position that you specified in your backend
  • change your style by adding the styles options (see code below)
  • view your page, you should see the new style
  • if everything works, try to implement your map in your original template file

var map;
function initMap() {
  map = new google.maps.Map(document.getElementById('map'), {
    center: {lat: -34.397, lng: 150.644},
    zoom: 8, // add comma here
    styles: [
  {
    "stylers": [
      { "hue": "#c1d72e" }
    ]
  }
]
  });
}

 

Thanks to your suggestions I finally figured out the problem. I had to replace the % on map's css to px.

Share this post


Link to post
Share on other sites

I have the big map working with this code (quite basic)

$items = $page->children;
$map = $modules->get('MarkupGoogleMap');

$content .= $map->render($items, 'map');

 

For the page with turtles I want to have the current turtle on that page to be visible on the map. I have made the following code:

if($page->hasChildren) {
    $results = $page->children("limit=9, sort=-created");

    $pagination = $results->renderPager();

    $content .= $pagination;
   $content .= renderSchildpadden($results);
    $content .= $pagination;
}


foreach ($results as $result){
    foreach ($result->verspreidingen as $verspreiding) {
    $out .= $verspreiding . "|";
    }
    }
//$item = $out;
$sidebar_bottom = $out;

$map = $modules->get('MarkupGoogleMap');

$sidebar_bottom .= $map->render($out, 'map');

The part for the sidebar_bottom gives the following error:

Error: Uncaught Error: Call to a member function first() on string in /home/deb26781n3/domains/chrysemys.nl/public_html/site/modules/FieldtypeMapMarker/MarkupGoogleMap.module:209
Stack trace:
#0 /home/deb26781n3/domains/chrysemys.nl/public_html/site/templates/schildpadden.php(32): MarkupGoogleMap->render('1213|1198|1199|...', 'map')
#1 /home/deb26781n3/domains/chrysemys.nl/public_html/wire/core/TemplateFile.php(268): require('/home/deb26781n...')
#2 [internal function]: ProcessWire\TemplateFile->___render()
#3 /home/deb26781n3/domains/chrysemys.nl/public_html/wire/core/Wire.php(374): call_user_func_array(Array, Array)
#4 /home/deb26781n3/domains/chrysemys.nl/public_html/wire/core/WireHooks.php(549): ProcessWire\Wire->_callMethod('___render', Array)
#5 /home/deb26781n3/domains/chrysemys.nl/public_html/wire/core/Wire.php(399): ProcessWire\WireHooks->runHooks(Object(ProcessWire\TemplateFile), 'render', Array)
#6 /home/deb26781n3/domains/chrysemys.nl/public_html/wire/modules/PageRender.mod (line 209 of /home/deb26781n3/domains/chrysemys.nl/public_html/site/modules/FieldtypeMapMarker/MarkupGoogleMap.module) 

This error message was shown because: you are logged in as a Superuser. Error has been logged.

 

The input for the big map are the pages that contain the field 'map'.

foreach ($results as $result)

{ foreach ($result->verspreidingen as $verspreiding) {

$out .= $verspreiding . "|";

}

}

The code above produces also an array of pages that contain the field 'map'. But this time the same function strugles on this part of the code in the module:

if($options['useMarkerSettings'] && (count($pageArray) == 1 || !$lat)) {
   // single marker overrides lat, lng and zoom settings
   $marker = $pageArray->first()->get($fieldName); << this line and on first() returns the error
          $lat = $marker->lat;
   $lng = $marker->lng; 
   if($marker->zoom > 0) $zoom = (int) $marker->zoom;
}

What am I doing wrong here?

 

Sanne

Share this post


Link to post
Share on other sites

Not sure if this is the cause of the problem, but this line...

if($options['useMarkerSettings'] && (count($pageArray) == 1 || !$lat)) {

...does not ensure that $pageArray exists. The if() condition is passed if $options['useMarkerSettings'] and !$lat, regardless of what $pageArray is.

  • Like 1

Share this post


Link to post
Share on other sites

I understand, but why does it work on page where I select children (array) but not on a page where I select certain pages as array that are the pages that have the 'map' field.

An array is made on both occasions.

The second array has duplicate items, could that be an issue?

 

Sanne

Share this post


Link to post
Share on other sites
3 minutes ago, webhoes said:

I understand, but why does it work on page where I select children (array) but not on a page where I select certain pages as array that are the pages that have the 'map' field.

An array is made on both occasions.

Not sure - nowhere in the code you posted do you show where $pageArray is defined.

Quote

Uncaught Error: Call to a member function first() on string

What this error means is that $pageArray is a string and not an actual PageArray. Use Tracy to dump $pageArray and find out what is going on with it.

Share this post


Link to post
Share on other sites

@Robin S, yes it is a string. Also it is build upon repeating pagearray which doesn't lead to an correct new array.

1 | 2 | 3 | 4 2 | 5 | 8 5 | 4 | 5...

The 2 in 4 2 is the start of an new array, so is the 5 in 8 5.

It can't find something with 42 or 85.

It seems the output has to be made a new array explicitly and also with the correct setup. Tried that yesterday, could not get it figured out.

Edited by webhoes

Share this post


Link to post
Share on other sites
3 hours ago, webhoes said:

yes it is a string. Also it is build upon repeating pagearray which doesn't lead to an correct new array.

Strings and arrays are different types of data, and a PageArray is a actually an object but you can think of it as a special kind of array. Long story short, you can't use PageArray methods on a string.

It's difficult to help without seeing the code where you set the $pageArray variable.

Share this post


Link to post
Share on other sites

I've been using Map Marker field with great success. 

I may have come across a strange bug, I'm not sure how to debug it...

When using the value Elgin, IL in the Address field, the geocode fetches correctly, BUT after saving the page, the Address field is BLANK.

I can do Elgin, Il (lowercase "L"), or Elgin, Illinois or South Elgin, IL or pretty much anything else I can think of, and everything WORKS.

WHY is the Address field not getting saved with just Elgin, IL? Or how can I debug this (where to look?) Thanks

Share this post


Link to post
Share on other sites
43 minutes ago, rastographics said:

When using the value Elgin, IL in the Address field, the geocode fetches correctly, BUT after saving the page, the Address field is BLANK.

Not sure why that is happening, but just to let you know that address works fine for me. Could some browser extension be interfering perhaps?

2017-02-25_101130.png.875b2cc9c231d9a9b46c73ffb5a04c9a.png

Share this post


Link to post
Share on other sites

Good idea, but unfortunately I just tried incognito mode with all extensions off and still not working.

No JS errors in console. Is there some other thing I can do to trace this down?

Share this post


Link to post
Share on other sites
On 10/7/2016 at 11:51 PM, bee8bit said:

@adrian Thank you, that was not the right solution. But it made me investigate in the right place:

InputfieldMapMarker's init function is never called. At the bottom, InputfieldMapMarker.js says:


$(document).ready(function() {
    $(".InputfieldMapMarkerMap").each(function() {
        var $t = $(this);
        InputfieldMapMarker.init($t.attr('id'), $t.attr('data-lat'), $t.attr('data-lng'), $t.attr('data-zoom'), $t.attr('data-type')); 
    }); 
}); 

When the $(document) is ready() there are no $(".InputfieldMapMarkerMap")s yet, as they will be AJAX-loaded later.

So I guess we need an event that is fired after each successful AJAX call, so we can InputfieldMapMarker.init() all those Maps which haven't been initialized before. Is there a way to register a listener for such events?

Hi @bee8bit. Did you find a solution or work around for this ?

I have a similar issue. "Days, Location, Description" in a Repeater. Where Location was going to be a inputFieldMapMarker. But, obviously not working. Did you figure a work around based on event listener or something ? 

Regards,

Share this post


Link to post
Share on other sites

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?

 

 

Share this post


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

MapMarker: Error geocoding address

The same issue. Running PW 3.0.61 and Map Marker 2.0.6 worked just fine. After upgrading to 2.0.9 and entering my API key I get the above error to any address I try.

Share this post


Link to post
Share on other sites

On a map I setup, I had the trouble of encoded (ampersend made me notice) characters not getting output decoded correctly, so I had to add htmlspecialchars_decode on this this line

$title = $options['markerTitleField'] ? htmlspecialchars_decode($page->get($options['markerTitleField'])) : ''; 

Shouldn't this be the expected behaviour? And why is the page title getting output without decoded entities? Is this expected inside modules for security reasons? 

Just trying to learn some PW here :)

 

Share this post


Link to post
Share on other sites

Hi

I'm trying to display a map with a marker on frontend with this :

	$map = $modules->get('MarkupGoogleMap'); 
	$content.= $map->render($page->children, 'map');
	

The map appear, correctly zoomed at the good location. However there is no marker. The marker appear correctly in backend.

Do I miss something?

Thanks

Mélanie
PW 3.0.69 - MapMarker 2.0.9

Share this post


Link to post
Share on other sites

The basic functionality of the module is great, but I wanted the capacity to add paths, and potentially geometric areas, and the easiest way I found to generate them was using something like Google Earth, or various mobile GPS apps which export KML files.
KML files can contain map markers as well, but the module already handles these fine.
The Google Maps API allows adding KML layers, and of course Processwire already has a files fieldtype, so it's easy to create a files field that only allows files of type kml.

I had to make a few modifications to the FieldTypeMapMarker as well.

MarkupGoogleMap.js

    //Add support for KML overlays, eg exported from Google Earth, or various GPS apps.
    this.addKml = function (url) {
        var zIndex = 99999 + this.numMarkers + 1;
        var layerOptions = {
            url: url,
            map: this.map,
            zIndex: zIndex
        }
        var kml = new google.maps.KmlLayer(layerOptions);

    }

MarkupGoogleMap.module

I added a 'postinit' property that is output after the map has been rendered. I found that the overlays can only be added after the map has been initialised, so the existing 'init' property didn't work.

Here's how I used it in a template:

$map = $modules->get('MarkupGoogleMap');
foreach ($page->kml as $kmlFile) {
    $overlays .= "mgmap1.addKml('$kmlFile->httpUrl'); ";
}
$content .= $map->render($page, 'location', array('type' => 'ROADMAP', 'postinit' => $overlays));

The code could probably be improved to have the foreach loop inside MarkupGoogleMap.module, and just pass the name of the overlay field if any, but it needs to be optional, as not all maps will have an associated field with kml files.

  • Like 2

Share this post


Link to post
Share on other sites

To always display the map at the center even if the browser resized or the full screen button pressed just use the below function:

google.maps.event.addDomListener(window, 'resize', function() {
		var center = map.getCenter()
		google.maps.event.trigger(map, "resize")
		map.setCenter(center)
	});

 

Share this post


Link to post
Share on other sites

Edit: I just realized there are 18 Pages in this thread and I am pretty sure someone else mentioned it, I will have a look :-[

 

I have just added the module to a new site I am creating and it seems like there are some issues.

1. The API key is not recognized when using the <script>-tag from module page (<script type='text/javascript' src='https://maps.googleapis.com/maps/api/js?sensor=false'></script>) – I had to add <script src="https://maps.googleapis.com/maps/api/js?libraries=places&key={{my API key}}"></script> in order to display the map.

2. The map in frontend does not look like the one in the backend. Instead of green areas for parks I get an all grey version, as you can see on the screenshots below. Mapsproblem.jpg.748edc310899b61b36078502d4dc0d92.jpg

Has anyone else noticed this?

PW Version is ProcessWire 3.0.62 from stable channel.

Edited by thmsnhl
  • Like 1

Share this post


Link to post
Share on other sites
On 10/20/2017 at 4:42 AM, thmsnhl said:

Edit: I just realized there are 18 Pages in this thread and I am pretty sure someone else mentioned it, I will have a look :-[

 

I have just added the module to a new site I am creating and it seems like there are some issues.

1. The API key is not recognized when using the <script>-tag from module page (<script type='text/javascript' src='https://maps.googleapis.com/maps/api/js?sensor=false'></script>) – I had to add <script src="https://maps.googleapis.com/maps/api/js?libraries=places&key={{my API key}}"></script> in order to display the map.

2. The map in frontend does not look like the one in the backend. Instead of green areas for parks I get an all grey version, as you can see on the screenshots below. Mapsproblem.jpg.748edc310899b61b36078502d4dc0d92.jpg

Has anyone else noticed this?

PW Version is ProcessWire 3.0.62 from stable channel.

 

 

I had to do this as well!

Share this post


Link to post
Share on other sites

so I am using this module and it is working great, I figured out that it doesn't render properly in collapse.

But now I want to disable or reset what happens when you click on an map marker or icon. I don't want to pass it a url, I want it to href to an id on the same page and I just don't seem to get it, where do I set the url or replace it.

Thank you

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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      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 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 (open spoiler):
      (Please note: these screenshots are from an early development state of SnipWire. To see actual screens please have a look at later posts below!)
       
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      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 Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...