Matthew Boynes

<p>This plugin adds a store/location directory to your WordPress site. Once you add stores, you can add the Store Search widget to your widget area or you can add the form to your theme manually.</p>
<p>This plugin is intentionally light and simple. It’s very flexible and is intended to be something on which you can build.</p>
<h3>Filters</h3>
<h4>wpsd_radius_options</h4>
<p>Param: <code>array( 5, 10, 25, 50, 100 )</code></p>
<p>This filter allows you to modify the options in the radius dropdown in the store search form. Values are in miles by default.</p>
<h4>wpsd_register_post_type</h4>
<p>Param: <code>true</code></p>
<p>This filter allows you to disable the <code>store</code> post type altogether. To do so, simply add <code>add_filter( 'wpsd_register_post_type', '__return_false' )</code> to your theme or plugin.</p>
<h4>wpsd_post_type_args</h4>
<p>This filter gives you the ability to modify the arguments passed to <code>register_post_type()</code> for the ‘store’ post type. See <a href="https://codex.wordpress.org/Function_Reference/register_post_type" rel="nofollow ugc">register_post_type in the Codex</a> for valid arguments and values.</p>
<p>Param:</p>
<pre><code>array(
    'public'      => true,
    'has_archive' => true,
    'supports'    => array( 'title' ),
    'labels'      => array(
        'name'                => __( 'Stores', 'store-directory' ),
        'singular_name'       => __( 'Store', 'store-directory' ),
        'all_items'           => __( 'Stores', 'store-directory' ),
        'new_item'            => __( 'New store', 'store-directory' ),
        'add_new'             => __( 'Add New', 'store-directory' ),
        'add_new_item'        => __( 'Add New store', 'store-directory' ),
        'edit_item'           => __( 'Edit store', 'store-directory' ),
        'view_item'           => __( 'View store', 'store-directory' ),
        'search_items'        => __( 'Search stores', 'store-directory' ),
        'not_found'           => __( 'No stores found', 'store-directory' ),
        'not_found_in_trash'  => __( 'No stores found in trash', 'store-directory' ),
        'parent_item_colon'   => __( 'Parent store', 'store-directory' ),
        'menu_name'           => __( 'Stores', 'store-directory' ),
    )
)
</code></pre>
<h4>wpsd_automap</h4>
<p>Param: <code>true</code></p>
<p>By default, a Google Map is added to the store archive views and store singular views using the <code>'loop_start'</code> action. This may not be desirable in all circumstances, especially if you loop through your posts multiple times. To disable this, add <code>add_filter( 'wpsd_automap', '__return_false' )</code> to your theme or plugin. If you choose to disable this, see the <code>wpsd_the_map()</code> tempalte tag to manually display the map.</p>
<h4>wpsd_mappable_data</h4>
<p>Param:</p>
<pre><code>array(
    'name'      => $post->post_title,
    'address'   => get_post_meta( $post->ID, 'address', true ),
    'latitude'  => $post->latitude,
    'longitude' => $post->longitude,
    'distance'  => $post->distance
)
</code></pre>
<p>Param: <code>$post</code></p>
<p>This filter allows you to customize the data used in the map. There is also a javascript “hook” that works in tandem with this, <code>wpsd_custom_create_marker</code>. To use the data you pass through the <code>wpsd_mappable_data</code> filter, you need to define a javascript function, <code>wpsd_custom_create_marker( latlng, data )</code>. This function should take two params, where the first is a <code>google.maps.LatLng</code> object and the second is an object with your filtered data. Armed with this data, you can create the marker however you need! See <code>js/maps.js:wpsd_create_marker()</code> for an example of how to create a marker.</p>
<h3>Template Tags</h3>
<h4>wpsd_the_store_search_form()</h4>
<p>Output the store search form. If you choose not to use the provided widget, this lets you add the form wherever you’d like.</p>
<h4>wpsd_the_map()</h4>
<p>Param: <code>$posts</code> array An array of posts to map. Each entry in the array should contain the following keys:</p>
<ul>
<li><code>'name' =></code> The marker title.</li>
<li><code>'address' =></code> The marker address.</li>
<li><code>'latitude' =></code> The latitude of the point.</li>
<li><code>'longitude' =></code> The longitude of the point.</li>
<li><code>'distance' =></code> The distance of the point from the center (optional, not presently used).</li>
</ul>
<p>See <code>WPSD_Search::get_mappable_data()</code> for an example.</p>
<p>Param: <code>$lat</code> float The latitude of the center point for the map.<br />
Param: <code>$long</code> float The longitude of the center point for the map.</p>
<p>Output a Google Map with the given points (posts) centered around the given latitude and longitude.</p>
<h3>Other Notes for Developers</h3>
<p>Beyond the above, pretty much everything in this plugin is modifiable by editing the properties of the singleton classes. Here are some examples:</p>
<ul>
<li>To change the post type, e.g. to be <code>'location'</code> instead of store, you can set it by calling <code>WPSD_Post_Type()->post_type = 'location';</code> from your theme or plugin (ideally during <code>after_setup_theme</code> at a priority higher than 10).</li>
<li>To change the units from miles to kilometers, <code>WPSD_Post_Type()->units = 'km';</code></li>
</ul>


Store Directory

A simple, flexible plugin for keeping a store/location directory and searching for them by radius.

Kyle Phillips

<p><strong>Why use Simple Locator?</strong></p>
<p>Simple locator is ideal for developers who are looking for a way to implement location search for any post type. Simple locator is different in that it allows the selection of any existing custom fields for use as the geocoded data sources.</p>
<p>Don’t have an existing post type with geocoded latitude and longitude fields? Simple Locator includes a default “Locations” post type with fields for latitutde, longitude, address, phone number, website, & more. This post type’s name and labels are configurable through the plugin settings.</p>
<p>Simple Locator also offers developer-friendly options for adding custom Google Maps styling. Select from an existing list, leave the default styles, or add your own JSON styles.</p>
<p><strong>Using Simple Locator</strong></p>
<ol>
<li>Add locations. This can either be the included “locations” post type or an existing custom post type with existing geocoded fields. Locations can also be imported in bulk using the included CSV importer.</li>
<li>Use the Shortcode [wp_simple_locator] or Widget to display a search form. The shortcode offers more options for map and form customization.</li>
</ol>
<p>For more information visit <a href="http://locatewp.com" rel="nofollow ugc">locatewp.com</a>.</p>
<p><strong>Important: Simple Locator requires WordPress version 3.8 or higher, and PHP version 5.4 or higher.</strong></p>
<h3>More Information</h3>
<h4>Shortcode Options</h4>
<p>The shortcode to display the form and results is [simple_locator]. There are several options available for customizing the form and results:</p>
<ul>
<li><strong>distances</strong> – A comma separated list of numbers used to customize the list of available distances to choose from in the form. Defaults to 5,10,20,50,100</li>
<li><strong>mapheight</strong> – The height of the map in pixels. Defaults to 250.</li>
<li><strong>mapcontainer</strong> – The unique ID of a custom container in which to load the map (ID parameter of HTML element).</li>
<li><strong>resultscontainer</strong> – The unique ID of a custom container in which to load the search results (ID parameter of HTML element).</li>
<li><strong>buttontext</strong> – Text to display in submit button. Defaults to “Search”.</li>
<li><strong>addresslabel</strong> – Customize the address form label</li>
<li><strong>mapcontrols</strong> – Hide or show the map controls</li>
<li><strong>mapcontrolsposition</strong> – Google Maps formatted position for map controls (ex: TOP_LEFT)</li>
<li><strong>showgeobutton</strong> – Whether to show or hide the “Use My Location” button. This button is hidden on sites that do not include an https connection. Defaults to false.</li>
<li><strong>geobuttontext</strong> – Customize the text content of the geolocation button if shown. Defaults to “Use My Location”.</li>
<li><strong>ajax</strong> – Whether to submit the form with an ajax request. Defaults to true.</li>
<li><strong>formmethod</strong> – The method of which the form submits. Default to “post”. If using a GET method with a non-ajax request, a results page must be specified.</li>
<li><strong>placeholder</strong> – Customize the search input placeholder text. Defaults to “Enter a Location”</li>
<li><strong>noresultstext</strong> – Customize the text displayed if no results are returned. Defaults to “No results found”.</li>
<li><strong>ajax</strong> – To disable AJAX form submission, use ajax=”false”. NOTE: custom map/results containers are not available for non-AJAX forms (added in v1.3.0)</li>
<li><strong>perpage</strong> – Used in conjunction with AJAX option. If a perpage option is included in a non-AJAX form, the results will be displayed with simple pagination, limited to the number per page specified. (Ex: ajax=”false” perpage=”15″). Pagination is not available with AJAX forms.</li>
<li><strong>resultspage</strong> – If a non-ajax form is being submitted (see ajax option), a separate results page may be specified.</li>
<li><strong>taxonomies</strong> – To include taxonomy filters in the search form, use a comma-separated list of taxonomy names/slugs. The form will include select menus for each of the taxonomies specified. (AJAX only)</li>
<li><strong>taxonomy_field_type</strong> – If taxonomy fields are displayed, the field type may be either “select” or “checkbox”. Defaults to “select”.</li>
<li><strong>allowemptyaddress</strong> – Set as “true” to allow empty address fields to be submitted (useful for returning all locations regardless of the user-specified location)</li>
<li><strong>showall</strong> – Whether to show all locations on page load. Defaults to false.</li>
</ul>
<p>Visit <a href="https://locatewp.com#documentation" rel="nofollow ugc">locate.wp</a> for more detailed information.</p>
<h4>Widget Use</h4>
<p>Options include the title, distance options, and the map height. To use the widget outside of a predefined sidebar area, use the following function in your template, as outlined in the <a href="https://codex.wordpress.org/Function_Reference/the_widget" rel="nofollow ugc">WordPress documentation</a>. The widget name is SimpleLocator\Widgets\Form (must include namespaces).</p>
<h4>Form Options</h4>
<p>To enable Google Places autocomplete in the search form, visit Settings > Simple Locator > General, and select the “Enable Autocomplete in Search” option. Your form will now include an autocomplete dropdown populated by the Google Places API.</p>
<h4>Singular View</h4>
<p>By default, a map of the location is added to the content on singular views. To remove this feature, update the setting under Simple Locator > General Settings.</p>
<h4>Extending & Customizing Map Display</h4>
<p>A number of JavaScript functions are provided to extend and customize the map results. Visit <a href="http://locatewp.com#documentation" rel="nofollow ugc">locatewp.com</a> for a list and usage details.</p>
<h4>Filters</h4>
<p>For a complete description of available filters and example usage, see the <a href="http://locatewp.com#documentation" rel="nofollow ugc">plugin website</a>.</p>
<ul>
<li><code>simple_locator_form($output, $distances, $taxonomies, $widget)</code> – Customize the search form HTML</li>
<li><code>simple_locator_result($output, $result, $count)</code> – Customize the result output within the result list</li>
<li><code>simple_locator_infowindow($infowindow, $result, $count)</code> – Customize the display of results within the Google Maps infowindow</li>
<li><code>simple_locator_post_fields()</code> – Add additional fields to the search parameters (field names for $_POST data)</li>
<li><code>simple_locator_sql_select($sql)</code> – Add additional fields to the SELECT sql query during search</li>
<li><code>simple_locator_sql_join($sql)</code> – Join additional fields in the sql query during search</li>
<li><code>simple_locator_sql_where($sql)</code> – Add additional WHERE parameters to the sql query during search</li>
<li><code>simple_locator_form_in_results($display_form)</code> – Whether to show the form in results (bool)</li>
<li><code>simple_locator_all_locations_text($text)</code> – Filter the text output of “All Locations”</li>
<li><code>simple_locator_map_pin_single($html)</code> – Filter the single view map pin</li>
<li><code>simple_locator_js_map_options($options)</code> – Filter the Javascript options passed to Google Maps for map display</li>
<li><code>simple_locator_autocomplete_js_options($options)</code> – Filter the Javascript options passed to the Google Maps Autocomplete API</li>
<li><code>simple_locator_form_taxonomies($taxonomies)</code> – Filter the taxonomies displayed in the search form</li>
</ul>


Simple Locator

This is a great plugin.
I literally spent two days testing out various free and premium locator plugins so I could get exactly what I needed. I needed a locator that stored the locations as a custom post type, allowed for categories, didn't clog up my database, and allowed me to extend onto of it. Simple Locator does all of that.



Just What I Needed

"Simple enough for plug and play, flexible enough for a customized location search solution." 

No kidding, impressive work. 

So slick.

Add Google Maps location search functionality for any post type.

Store Directory vs Simple Locator