ryan

Map Marker Map

Recommended Posts

On 2017-06-19 at 1:35 AM, Jozsef said:

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.

 

On 2017-06-01 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?

 

 

Hi @Arcturus and @Jozsef,

 

Did you find a solution for this issue? I am running  3.0.84 and am having the same problem.

//Jasper

Share this post


Link to post
Share on other sites
On 9/24/2017 at 9:30 PM, PWaddict said:

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)
	});

 

The above function that I posted few months ago it's working perfect for Chrome, Firefox & Opera.

On IE11 it's partial working. If the map's full screen button pressed the map is no more centered. On the browser resize is working properly. Anyone knows how to fix this?

Share this post


Link to post
Share on other sites

I am really stuck here, the map was working fine a few weeks ago but now the address will not geocode automatically, this is a problem as I could have multiple users adding addresses through the api. I have tried adding $p->trackChange('map'); and similar but everytime I have to go in and click on the address field and then click out of it and it works. Any suggestions?

While I am here, how do I get the map markers to not link to a page when someone clicks them.

Share this post


Link to post
Share on other sites

Hello, 

i have 2 different domains for one page. 
In one domain i can see the map markers in other it comes an error. 
 

Google Maps API error: MissingKeyMapError https://developers.google.com/maps/documentation/javascript/error-messages#missing-key-map-error

I have generated an standart Api key 
dont understand why it doesnt works 

the same key also works for me on localhost skyscrapers profile too 

 

Share this post


Link to post
Share on other sites

The Geocode is returning some results in local script - ie,  Japanese is like -  和歌山県.  Is there a way to have it return English?  I know if I search the same place in Google Maps it returns the English equivalent.  I tried adding language=en to the URL in MapMarker.Php but that didn't work.

 

Thanks,

Heather

Share this post


Link to post
Share on other sites
On 14/12/2017 at 2:14 PM, formmailer said:

 

Hi @Arcturus and @Jozsef,

 

Did you find a solution for this issue? I am running  3.0.84 and am having the same problem.

//Jasper

The only solution I've found is to downgrade the MapMarker module to 2.0.6, I believe. That's the last working version for me.

Share this post


Link to post
Share on other sites

Hi,

I'm trying to display the title of a page on the map but I can get it.

Ideally I want to display both $page->lieu->title and page->map_lieu->adress.

I couldn't find the way to write it. The only one working is 'lieu' but it display only id page. Can I use a variable in the array?

        'markerTitleField' => 'lieu',   // $page->lieu->title  ??

Thanks

Mel

Share this post


Link to post
Share on other sites

Not sure if anyone is interested, but I just extended this to support address component fields. Now you can enter the various address components individually and it will automatically populate the final combined address field and geocode the address to lat/long.

image.thumb.png.622315b1d549731b233fe3be3e8a1995.png

I wanted this so I could grab the individual components for displaying a business address in a specific format, rather than relying on what the site editor entered into the combined address field.

You can of course call the components like this:

$page->address->street
$page->address->additional
$page->address->city
$page->address->state
$page->address->postcode
$page->address->country

These are in addition to the existing:

$page->address->address // the combined version
$page->address->lat
$page->address->lng
$page->address->zoom

Is anyone interested in this version? Not sure if @ryan would accept a PR or not?

 

  • Like 6

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Not sure if anyone is interested, but I just extended this to support address component fields. Now you can enter the various address components individually and it will automatically populate the final combined address field and geocode the address to lat/long.

image.thumb.png.622315b1d549731b233fe3be3e8a1995.png

I wanted this so I could grab the individual components for displaying a business address in a specific format, rather than relying on what the site editor entered into the combined address field.

You can of course call the components like this:


$page->address->street
$page->address->additional
$page->address->city
$page->address->state
$page->address->postcode
$page->address->country

These are in addition to the existing:


$page->address->address // the combined version
$page->address->lat
$page->address->lng
$page->address->zoom

Is anyone interested in this version? Not sure if @ryan would accept a PR or not?

 

I would use it

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Not sure if anyone is interested, but I just extended this to support address component fields. Now you can enter the various address components individually and it will automatically populate the final combined address field and geocode the address to lat/long.

image.thumb.png.622315b1d549731b233fe3be3e8a1995.png

I wanted this so I could grab the individual components for displaying a business address in a specific format, rather than relying on what the site editor entered into the combined address field.

You can of course call the components like this:


$page->address->street
$page->address->additional
$page->address->city
$page->address->state
$page->address->postcode
$page->address->country

These are in addition to the existing:


$page->address->address // the combined version
$page->address->lat
$page->address->lng
$page->address->zoom

Is anyone interested in this version? Not sure if @ryan would accept a PR or not?

 

Too late for me since I did that in my /ready.php. But would certainly use it in another project! ;-)

Share this post


Link to post
Share on other sites
1 hour ago, mel47 said:

Too late for me since I did that in my /ready.php.

I am curious how you handled it in ready.php - did you create the additional component inputs, or was it extracting the components from the single combined address field? I have done something similar before, but the problem is that you can't guarantee how site editors will enter the address that way.

Share this post


Link to post
Share on other sites
On 9/24/2017 at 9:30 PM, PWaddict said:

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)
	});

 

The Google Maps API have just been updated and the "center" is now working on all browsers:

  • When the map is resized, the map center is fixed
    • The full-screen control now preserves center.
    • There is no longer any need to trigger the resize event manually.

Share this post


Link to post
Share on other sites
22 hours ago, adrian said:

I am curious how you handled it in ready.php - did you create the additional component inputs, or was it extracting the components from the single combined address field? I have done something similar before, but the problem is that you can't guarantee how site editors will enter the address that way.

Nothing special. Just a concatenate from values like this:

$page->map_lieu->address = "{$page->no_civique} {$page->rue}, {$page->ville}, {$page->codepostal} {$page->pays}";

Data were entered from FormBuilder, with fields similar to yours. I'm now at ~150 adresses collected and I just have a couple which didn't geolocalize (generally a typo).  Status varied to "rooftop to geometric center". My only concerns is if you get a "Zero results" status, on front-end, the square map appears but with nothing. I'm planning to display the map with a "if status>=1", just to be sure.

Share this post


Link to post
Share on other sites

Interesting discussion about extra address fields.

I created a fieldtype 'AddressGeoNames' that consists of separate text inputs for country, city, postcode, lat, lng etc. where field values are verified and partially auto populated through geonames.org API.

This is a standalone Inputfield that geocodes through the google maps api.

But it can also be connected to an InputfieldLeafletMapMarker field so that the given address will be rendered as pin on the map. The pin can also be manually repositioned and writes back lat/lng to the AddressGeonames field.

I am currently using this in one live project with about 1500 users and they seem to get along fine with data input and geocoding.

This is how it looks like when used next to a InputfieldLeafletMapMarker field:
addressgeonames.thumb.png.7811ec93b18df1d5952ce7d9b93044a3.png

Planning on adding support for GoogleMapsMarker, too and eventually releasing it on github. Not quite ready yet, though. But if anyone is interested in the concept, I could share what I have so far.

 

  • Like 4

Share this post


Link to post
Share on other sites

Really nice work on the Map InputFields folks!

I need to do something similar next week for a travel company. They want to plot a route on a map and I have been wondering about the best way to go about this.

My thoughts so far would be to tie a repeater control to a map, let the user use the marker to plot the route, then add the coordinates into a repeater control. 

This approach using jQuery opens up all kinds of issues in terms of managing the UX design for removing steps in the route, adding individual steps into the repeater, synchronizing the plotted route with the repeater control entries from the marker etc....

Wondered if any one else has run into similar UX request and found a better way around it.

 

 

Share this post


Link to post
Share on other sites

Hi guys, 

Do you have the map marker module working in version 2.8 or version 3? In processwire admin, I can see the map, but then when I go to the page where the map should be showing, I'm getting an error: " MarkupGoogleMap Error: Please add the maps.google.com script in your document head. The map is not showing on the page. " 

I have fresh processwire installation

it seems that the module injects the google maps script before html tag, it seems to be causing the problem... I'm not sure how to solve this

 

<script type='text/javascript' src='/site/modules/FieldtypeMapMarker/MarkupGoogleMap.js'></script><div id='mgmap1' class='MarkupGoogleMap' style='width: 100%; height: 300px;'></div><script type='text/javascript'>if(typeof google === 'undefined' || typeof google.maps === 'undefined') { alert('MarkupGoogleMap Error: Please add the maps.google.com script in your document head.'); } else { var mgmap1 = new MarkupGoogleMap(); mgmap1.setOption('zoom', 12); mgmap1.setOption('mapTypeId', google.maps.MapTypeId.HYBRID); mgmap1.init('mgmap1', 40.712776, -74.005974); mgmap1.addMarker(40.712776, -74.005974, '/en/about/', 'About', ''); }</script><!DOCTYPE html>
<html lang="en">
<head>

when I paste the code inside <head> manually, then I can see the map on the page where it should be visible. 

 

Any suggestions?

Share this post


Link to post
Share on other sites
On 14.2.2018 at 3:13 AM, adrian said:

Not sure if anyone is interested, but I just extended this to support address component fields. Now you can enter the various address components individually and it will automatically populate the final combined address field and geocode the address to lat/long.

image.thumb.png.622315b1d549731b233fe3be3e8a1995.png

I wanted this so I could grab the individual components for displaying a business address in a specific format, rather than relying on what the site editor entered into the combined address field.

You can of course call the components like this:


$page->address->street
$page->address->additional
$page->address->city
$page->address->state
$page->address->postcode
$page->address->country

These are in addition to the existing:


$page->address->address // the combined version
$page->address->lat
$page->address->lng
$page->address->zoom

Is anyone interested in this version? Not sure if @ryan would accept a PR or not?

 

I want tha ;)

Share this post


Link to post
Share on other sites
On 2/18/2018 at 4:37 AM, adrian said:

Thanks for this fork - a very useful enhancement. If you think you might submit a pull request I saw a few things that could be good to include.

1. The default address setting in the field config doesn't work in this fork. Maybe it needs separate fields for street, city, etc?

2. Perhaps you could integrate this fix for ajax-loaded inputfields: https://github.com/ryancramerdesign/FieldtypeMapMarker/issues/19

3. Because the inputfield places the text inputs inside paragraph tags, there is an excessive amount of vertical space between rows of inputs (in the default admin theme at least - I didn't check the others). Solutions could be to change from <p> to <div> wrappers, or to add a rule to InputfieldMapMarker.css to reduce the margin on paragraphs.

Edit...

4. Would it be possible to avoid the trailing commas in the Address field if some of the components aren't filled out?

2018-03-05_123037.png.9ddcc6e6abe44532e781abc4522f8eb0.png

  • Like 1

Share this post


Link to post
Share on other sites

Hi @Robin S - glad you're finding the fork useful.

1. I can't see a difference in behavior from the main repo - it looks to me like the lat/lng get populated when creating a new page, but not the address field. I think this actually makes sense to me because I think it's really just designed to give the site editor a local starting view, rather than an exact address. Am I missing something?

2. Happy to incorporate the AJAX fix - thanks.

3. I honestly don't mind the spacing. It is applied differently in default and UiKit themes which makes it a bit of a pain. Probably changing the <p> to <div> as you suggested might make this a little cleaner. Perhaps you'd consider a PR to my repo so you can get it looking how you'd like it - better to have someone tweak this who has a definite opinion on it :) 

4. I am looking at this now - agreed that this should be fixed, but I noticed a bit of a dilemma - currently I trigger the geocode request like this:

            if($street.val() && $city.val() && $state.val() && $postcode.val() && $country.val()) {
                $addrComponent.blur(function() {
                    geoCodeAddr();
                });
            }

In other words, don't trigger it until all subfields are complete (except the additional_address which isn't added to the address which gets geocoded anyway). So if you're in a situation where not all subfields are filled out, it won't geocode. I don't really want to have a manual geocode button - would rather it was automatic - what do you think?

 

As for submitting a PR back to the main repo - I don't think there is really much point - I have a 4 year old PR there already which has been ignored :) Not that I want to have multiple forks of modules floating around either, but not sure what other option there is.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @adrian, I'll have a think about those things.

I realise now that I have made a lot of changes myself to FieldtypeMapMarker for different projects - every time I use it I find something that doesn't really suit me or work too well. Maybe I should go through all of that and consolidate it into my own fork. Then we could possibly look at where it makes sense to combine our forks together.

  • Like 2

Share this post


Link to post
Share on other sites
Just now, Robin S said:

Then we could possibly look at where it makes sense to combine our forks together.

Yeah, I think that would be great - I think we need one feature-rich version going forward that has all these improvements. I don't expect Ryan will accept a PR, but I do remember sometime ago he suggested I could take over this module if I wanted - personally I don't really want to because I already have too many to support, but perhaps if we both had commit rights on the main repo we could share the load?

  • Like 2

Share this post


Link to post
Share on other sites

@ryan

it would be great if there was an option to save the map (using static maps api?) to an image file locally and that local image would update should the map field values change. This would mean not needing to use an API key since the traffic would be to your hosted image and not making requests to google maps api each visit. So to the cms user they are seeing gmaps as usual but the cms saves a static version of their work to an image that is used on the output side.

Also it would be neat to have a checkbox that enabled to  use JS/CSS to provide artificial zoom/map moving function using the static map image assuming it was at a decent resolution/dimensions and perhaps marker placement as well. Otherwise if the checkbox is un-selected, it will show a map image of defined dimensions with no zoom or bells & whistles, etc.

Share this post


Link to post
Share on other sites

Hi

I have frequently error : "initMap is not a function"

But the map is generally displaying correctly. Sometimes I have to refresh the page to get it.

I have this in <head>:      <script async defer src="https://maps.googleapis.com/maps/api/js?key=MYKEY&callback=initMap"  type="text/javascript"></script>

 

Chrome inspector:
js?key=AIzaSyAXQ3WeU…callback=initMap:96 Uncaught 
Kb {message: "initMap is not a function", name: "InvalidValueError", stack: "Error↵    at new Kb (https://maps.googleapis.com/m…QnQ_ThTMb8XNFMZaOHo23Ya04&callback=initMap:146:49"}
message:"initMap is not a function"
name:"InvalidValueError"
stack:
"Error↵    at new Kb (https://maps.googleapis.com/maps/api/js?key=MYKEY&callback=initMap:42:72)↵    at Object._.Lb (https://maps.googleapis.com/maps/api/js?key=MYKEY&callback=initMap:42:182)↵    at ih (https://maps.googleapis.com/maps/api/js?key=MYKEY&callback=initMap:96:104)↵    at https://maps.googleapis.com/maps/api/js?key=MYKEY&callback=initMap:146:34↵    at Object.google.maps.Load (https://maps.googleapis.com/maps/api/js?key=MYKEY4&callback=initMap:21:5)↵    at https://maps.googleapis.com/maps/api/js?key=MYKEY&callback=initMap:145:20↵    at https://maps.googleapis.com/maps/api/js?key=MYKEY&callback=initMap:146:49"
__proto__
:Error

Thanks

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 joshuag
      Hey guys, 
      Thought I would share a quick preview of Designme. A module we (Eduardo @elabx and I) are building for visually laying out your templates/edit screens. 🙂
      This is a really quick, zero polish screen grab. FYI. 
      Video #2 - UPDATE
      This new video shows the following features in Designme:
      Re-arranging fields via Drag & Drop Re-sizing fields via Dragging. Adjusting field settings - with live refresh. Working on "hidden" fields while Designme is active. Creating New fields. Deleting fields. Creating/Deleting Tabs. Dragging fields between tabs. Creating fieldsets. Tagging/Un-tagging fields. Fields without headers expand when hovered (like checkboxes). Live filtering of fields in the sidebar. Ability to adjust (all) Template settings without leaving Designme. Template File Tree Editing Template files source code with ACE Editor. Editing Multiple files with ACE Editor. (New Tabs) Saving files. Techie stuff Fields load their own js/css dependancies. *ready to use on creation (*most fields)  Everything happens via Ajax to ProcessPageEdit (via module + hooks). Designme has a JS api that you can use.  All actions trigger events.  We would love any detailed feedback on what you see so far. If you are interested in testing Designme. Let me know below. 🙂
       
       
      Video #1. 
       
    • By dreerr
      TemplateEnginePug (formally TemplateEngineJade)
       
      This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
      doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
      Project in modules directory: modules.processwire.com/modules/template-engine-pug/
       
      For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
       
    • By tpr
      ProcessNetteTester
      Run Nette Tester tests within ProcessWire admin.
      (continued from here)

      Features
      AJAX interface for running Nette Tester tests, in bulk or manually display counter, error message and execution time in a table run all tests at once or launch single tests show formatted test error messages and report PHP syntax errors stop on first failed test (optional) hide passed tests (optional) display failed/total instead passed/total (optional) re-run failed tests only (optional) auto scroll (optional) include or exclude tests based on query parameters start/stop all tests with the spacebar reset one test or all tests (ctrl+click) https://modules.processwire.com/modules/process-nette-tester/
      https://github.com/rolandtoth/ProcessNetteTester
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour.
       
      Changelog
      180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By tpr
      Update 2018-07-09: ProcessNetteTester module is available in the Modules Directory and on GitHub.

      This is a short tutorial on how to use Nette Tester with ProcessWire.
      As you will see it's very easy to setup and use and it's perfect for testing your code's functionality. With bootstrapping ProcessWire it's also possible to check the rendered markup of pages using the API, checking page properties, etc. It's also a great tool for module developers for writing better code. 
      While there will be nothing extraordinary here that you couldn't find in Tester's docs this can serve as a good starting point.
      Prerequisites: PHP 5.6+
      01 Download Tester
      Go to https://github.com/nette/tester/releases and download the latest release (currently 2.0.2). Download from the link reading "Source code (zip)". You can use composer also if you wish.
      02 Extract Tester files
      Create a new directory in your site root called "tester". Extract the zip downloaded here, so it should look like this:
      /site /tester/src /tester/tools /tester/appveyor.yml /tester/composer.json /tester/contributing.md /tester/license.md /tester/readme.md /wire ... 03 Create directory for test files
      Add a new directory in "/tester" called "tests". Tester recognizes "*.Test.php" and "*.phpt" files in the tests directory, recursively. 
      04 Create your first test
      In the "tests" directory create a new "MyTest.php" file.
      The first test is a very simple one that bootstraps ProcessWire and checks if the Home page name is "Home". This is not the smartest test but will show you the basics.
      Add this to "/tester/tests/MyTest.php":
      <?php namespace ProcessWire; use \Tester\Assert; use \Tester\DomQuery; use \Tester\TestCase; use \Tester\Environment; require __DIR__ . '/../src/bootstrap.php'; // load Tester require __DIR__ . '/../../index.php'; // bootstrap ProcessWire Environment::setup(); class MyTest extends TestCase {     // first test (step 04)     public function testHomeTitle()     {         $expected = 'Home'; // we expect the page title to be "Home"         $actual = wire('pages')->get(1)->title; // check what's the actual title Assert::equal($expected, $actual); // check whether they are equal     }     // second test will go here (step 06)     // third test will go here (step 07) } // run testing methods (new MyTest())->run(); I've added comment placeholders for the second and third tests that we will insert later.
      05 Run Tester
      Tester can be run either from the command line or from the browser. The command line output is more verbose and colored while in the browser it's plain text only (see later).
      Running from the command line
      Navigate to the "/tester" directory in your console and execute this:
      php src/tester.php -C tests This will start "/tester/src/tester.php" and runs test files from the "/tester/tests" directory. The "-C" switch tells Tester to use the system-wide php ini file, that is required here because when bootstrapping ProcessWire you may run into errors (no php.ini file is used by default). You may load another ini file with the "-c <path>" (check the docs).
      If the title of your Home page is "Home" you should see this:

      If it's for example "Cats and Dogs", you should see this:

      Running from the browser
      First we need to create a new PHP file in ProcessWire's root, let's call it "testrunner.php". This is because ProcessWire doesn't allow to run PHP files from its "site" directory.
      The following code runs two test classes and produces a legible output. IRL you should probably iterate through directories to get test files (eg. with glob()), and of course it's better not allow tests go out to production.
      <?php ini_set('html_errors', false); header('Content-type: text/plain'); echo 'Starting tests.' . PHP_EOL; echo '--------------------------' . PHP_EOL; $file = __DIR__ . '/PATH_TO/FirstTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; $file = __DIR__ . '/PATH_TO/SecondTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; echo '--------------------------' . PHP_EOL; echo 'Tests finished.'; exit; Navigate to "DOMAIN/testrunner.php" in your browser to execute the file. If every test succeeds you should get this:

      If there are failed tests the execution stops and you can read the error message. If there were more tests (eg. ThirdTest), those won't be displayed under the failed test.

      06 DOM test
      This test will check if a page with "basic-page" template has a "h1" element. We will create the page on the fly with ProcessWire's API. To keep things simple we will add the new test as a new method to our MyTest class.
      Add this block to the MyTest class:
      public function testBasicPageHeadline() {     $p = new Page();     $p->template = 'basic-page';     $html = $p->render();     $dom = DomQuery::fromHtml($html);     Assert::true($dom->has('h1')); } This will most likely be true but of course you can check for something more specific, for example "div#main". Note that we have used the DomQuery helper here (check the "use" statement on the top of the file).
      07 Custom function test
      You will probably want to make sure your custom functions/methods will work as they should so let's write a test that demonstrates this.
      I don't want to complicate things so I'll check if the built-in "pageName" sanitizer works as expected. Add this to the myTest class:
      public function testPageNameSanitizer() {     $expected = 'hello-world';     $actual = wire('sanitizer')->pageName('Hello world!', true);     Assert::equal($expected, $actual); } This should also be true. Try to change the expected value if you are eager to see a failure message.
       
      08 Next steps
      You can add more methods to the MyTest class or create new files in the "tests" directory. Check out the range of available Assertions and other features in the docs and see how they could help you writing more fail-safe code.
      Once you make a habit of writing tests you'll see how it can assist making your code more bulletproof and stable. Remember: test early, test often 🙂
      If you find out something useful or cool with Tester make sure to share.