Title: Mapsemble
Author: mapsemble
Published: <strong>October 23, 2026</strong>
Last modified: October 23, 2026

---

Search plugins

![](https://ps.w.org/mapsemble/assets/banner-772x250.png?rev=3761497)

![](https://ps.w.org/mapsemble/assets/icon.svg?rev=3761497)

# Mapsemble

 By [mapsemble](https://profiles.wordpress.org/mapsemble/)

[Download](https://downloads.wordpress.org/plugin/mapsemble.0.5.0.zip)

 * [Details](https://wordpress.org/plugins/mapsemble/#description)
 * [Reviews](https://wordpress.org/plugins/mapsemble/#reviews)
 *  [Installation](https://wordpress.org/plugins/mapsemble/#installation)
 * [Development](https://wordpress.org/plugins/mapsemble/#developers)

 [Support](https://wordpress.org/support/plugin/mapsemble/)

## Description

Mapsemble connects WordPress to the [Mapsemble](https://mapsemble.com/map-builder)
map service. You design the map — styling, clustering, filters, cards — in Mapsemble;
this plugin puts it on a page and, when you want, feeds it from your own posts.

#### Embed any map

Every map embeds by its Mapsemble map id — with the Mapsemble Map block, the `[mapsemble
map="…"]` shortcode, or the `mapsemble_embed()` template function. No setup on this
site is needed: the block lists your account’s maps, a typed id works for any public
map, and `[mapsemble map="sample"]` renders a real, fully populated sample map before
you have entered any credentials at all. Your account’s maps are listed under Mapsemble
Maps, where locations for maps hosted on Mapsemble are edited in the Mapsemble location
editor, which opens from your admin in a new tab with the map beside it — this works
on a local development site too.

#### Or build a map from this site’s content

Add a map under Mapsemble  Built from this site to make a post type the map’s data:
give posts a location and Mapsemble fetches them from a public endpoint on your 
site, with the cards rendered from your own templates. Always-on filters, visitor
filter mappings, sort options and marker style properties shape the feed per map.
This is the advanced option: it needs a publicly reachable site, and the Pro plan
on the Mapsemble side — nothing is blocked before then; visitors see an upgrade 
notice over the map until the account is upgraded.

Editing follows the data: maps hosted on Mapsemble are edited in the Mapsemble editor(
opened from Mapsemble  Maps in your admin); maps built from this site are edited
by editing the posts themselves.

#### Shaping a site-fed map

A map built from this site does not have to serve the whole post type:

 * **Always-on filters** restrict which posts appear — by taxonomy term or custom
   field — so two maps on the same post type can show different posts.
 * **Visitor filters** bind the filter widgets you configured on Mapsemble to your
   taxonomies and custom fields, so choosing one actually narrows the results. Option
   pickers are fed from your content.
 * **Sort options** bind the map’s sort choices to publication date, title, a custom
   field, or entropy — an even geographic spread, so the first results cover the
   map instead of clustering.
 * **Marker style properties** put taxonomy terms or custom field values on every
   map feature, for Mapsemble’s marker-style rules to match.

All of this lives on the map’s own edit screen and applies to the feed immediately—
no reindexing.

#### Placing a map

 * **Block editor** — add the **Mapsemble Map** block (under Embed) and pick any
   map right in the canvas: search your account’s maps and maps built from this 
   site, or choose the sample or a typed id. The chosen map previews live, and “
   Change map” in the block toolbar picks another. New blocks insert as Wide. Height,
   scroll behaviour and initial filters are in the block sidebar. The same block
   works in Appearance  Widgets and in the Site Editor.
 * **Classic editor, Text widgets, page builders** — use the shortcode. `map` takes
   a Mapsemble map id (or `sample`); `id` takes a site-fed map’s WordPress id, shown
   ready to copy on the Built from this site list:
    [mapsemble map=”0198…” height
   =”60vh” scroll_capture=”mobile”] or `[mapsemble id="123"]`
 * **Theme templates** — `mapsemble_embed( '0198…' )` / `the_mapsemble_embed( 'sample')`
   for any map by id, or `mapsemble_map( 123 )` / `the_mapsemble_map( 123 )` for
   a map built from this site.

A map built from this site serves from this site however it is embedded, by its 
map id too — “fed by WordPress” is a property of the map, not of where you embed
it.

    ```
    height and the two offsets take a CSS length (`50vh`, `480px`, `2rem`). `scroll_capture` is `none` or `mobile`, and turns the map into a sticky section: scroll gestures over it move the card list instead of the page. While scroll capture is on, the map sticks at the top offset — that is how you clear a fixed site header. While the map fills the visible screen, both offsets are also taken off its height, leaving room above and below it — as long as the minimum `height` leaves that room. Leave any of them out and the map keeps its own default.
    ```

Two more attributes shape the embed:

 * `fill_viewport="false"` stops the map from growing to the visible viewport. Normally`
   height` is a minimum: the map is at least that tall and grows to fill the visible
   screen. With `fill_viewport="false"` it is the exact height — `height="300px"`
   makes a 300px map.
 * `filters` seeds the map’s filters on load, as a JSON object of filter slug to
   value. Quote it with single quotes so the editor does not mangle the JSON: `[
   mapsemble id="123" filters='{"category":"parks"}']`. An unreadable value is ignored.
   In the block, both live in the sidebar; in `mapsemble_map()`, pass `filters` 
   as a native array.

**A Mapsemble account is required.** See the External Services section for details
on what data is exchanged.

### External Services

This plugin connects to the Mapsemble service (https://app.mapsemble.com):

 * It loads the Mapsemble map widget (widget.js) from app.mapsemble.com on pages
   where you embed a map, and in the block editor’s live preview of one. Visitors’
   browsers request map tiles and configuration from the Mapsemble service; their
   IP address and the map id are visible to it, as with any embedded map service.
 * From the admin area it authenticates with your API credentials to list the maps
   in your account, to read a map’s filters and sort options (for a map’s edit screen
   and the block’s Filters panel), to create maps, and to tell Mapsemble where each
   map’s data comes from.
 * When you connect from the settings screen, the link your browser opens carries
   a one-time random code to Mapsemble; you approve there, and the plugin then collects
   the API credentials over a server-to-server request, so they never pass through
   your browser.
 * For a map whose locations live in Mapsemble, “Open the location editor” under
   Mapsemble  Maps sends a new browser tab to app.mapsemble.com, signed in with 
   a single-use token minted from your API credentials at the moment you click. 
   The token is scoped to that one map, and the session it opens reaches that map’s
   editor and preview and no other part of your Mapsemble account. WordPress users
   never see the credentials.
 * When an editor searches for an address in a post’s Map location box (“Find an
   address”), the text they typed is sent from this site’s server to the Mapsemble
   API (`/api/v1/geocode`), authenticated with your API credentials, and Mapsemble
   forwards it to Google’s Geocoding API to look up its coordinates. It is sent 
   only when an editor searches; visitors never trigger it. The “check it on OpenStreetMap”
   link next to a found address opens openstreetmap.org only when clicked. Google
   Maps Platform terms: https://cloud.google.com/maps-platform/terms — Google privacy
   policy: https://policies.google.com/privacy
 * For a map built from this site, the Mapsemble service fetches your published,
   geo-tagged content from public endpoints this plugin provides on your site.

Terms of service: https://www.mapsemble.com/terms — Privacy policy: https://www.
mapsemble.com/privacy

## Screenshots

[⌊The Mapsemble Map block: search your maps by name; same-named maps show their 
date and short id.⌉⌊The Mapsemble Map block: search your maps by name; same-named
maps show their date and short id.⌉[

The Mapsemble Map block: search your maps by name; same-named maps show their date
and short id.

[⌊Settings once connected: how many maps your Mapsemble account holds, with reconnecting
folded away.⌉⌊Settings once connected: how many maps your Mapsemble account holds,
with reconnecting folded away.⌉[

Settings once connected: how many maps your Mapsemble account holds, with reconnecting
folded away.

[⌊A site-fed map: bound to a map on your account, it says how many of this site's
posts it serves.⌉⌊A site-fed map: bound to a map on your account, it says how many
of this site's posts it serves.⌉[

A site-fed map: bound to a map on your account, it says how many of this site’s 
posts it serves.

[⌊The sample map on a published page, with cards and map side by side.⌉⌊The sample
map on a published page, with cards and map side by side.⌉[

The sample map on a published page, with cards and map side by side.

## Blocks

This plugin provides 1 block.

 *   Mapsemble Map Embed any Mapsemble map: one of yours, the sample, or one built
   from this site's content.

## Installation

 1. Install and activate the plugin.
 2. Under Mapsemble  Settings, click Authenticate on Mapsemble, approve the connection
    in the tab that opens, and the page finishes on its own. (You can still paste a
    client ID and secret by hand.)
 3. Add the Mapsemble Map block to a page and pick one of your maps — nothing else 
    is needed. Your account’s maps are listed under Mapsemble  Maps, where “Edit locations”
    leads to a button that opens the Mapsemble location editor in a new tab.
 4. To feed a map from this site’s posts instead, go to Mapsemble  Built from this 
    site and click Build a map from this site. Pick a map from your account, or create
    a new one from this screen.
 5. Pick a post type and a location source, and save. Then give your posts a location
    with the built-in location box (find an address, or enter latitude and longitude)
    or an ACF Google Map field.
 6. Embed it with the Mapsemble Map block, or with the shortcode shown on the Built
    from this site list: `[mapsemble id="123" height="60vh"]`.

## FAQ

### Where does the map design come from?

From your Mapsemble account. Styling, clustering, filters and layout are configured
in the Mapsemble map builder. This plugin decides only where the locations come 
from, and renders the content cards when they come from this site.

### Who can edit a map’s locations?

Editors, by default. Maintaining locations is content work, so it has its own capability(`
edit_mapsemble_map_data`) that the administrative ones deliberately do not imply—
the person adding locations does not need the screen holding your API credentials.
Administrators hold both.

### Can I change the card markup?

Yes. Copy `templates/card.php` from the plugin into your theme as `mapsemble/card.
php` and adjust it. Developers can also use the `mapsemble_card_html`, `mapsemble_card_css_urls`
and `mapsemble_card_data` filters.

### My coordinates live in custom fields already. Can I use them?

Yes. Choose the “Custom fields (latitude/longitude meta keys)” location source and
name the two meta keys — that covers Metabox.io, Pods, imported data and hand-rolled
meta. An ACF Google Map field has its own named source. For computed cases, the `
mapsemble_post_coordinates` filter remains. After switching sources, run “Reindex
locations” on the map.

### Is the map’s interface translatable?

Yes. The widget’s interface strings (“Filters”, “Search”, “Sort by”, …) run through
the plugin’s `mapsemble` text domain, so a `.po` file for your language translates
them; English sites send nothing extra. Developers can add or override strings with
the `mapsemble_widget_translations` filter.

### Can I develop against a local site?

A map whose locations live in Mapsemble works on a local site with no extra setup:
nothing on the Mapsemble side ever fetches from your server.

A map built from this site’s content does not, because the Mapsemble service has
to reach your feed. Expose the site through a tunnel and define `MAPSEMBLE_REMOTE_BASE_URL`
in `wp-config.php`; the plugin then hands Mapsemble that address instead of your
local one.

Two more constants exist for people running the Mapsemble service itself locally.`
MAPSEMBLE_APP_BASE` points the plugin at another Mapsemble host; TLS is still verified
against it. `MAPSEMBLE_SSL_VERIFY` set to `false` switches that verification off—
define it only for a local stack whose certificate the WordPress container does 
not trust, never on a public site.

The sample map is the exception: it always loads from app.mapsemble.com whatever`
MAPSEMBLE_APP_BASE` says. A stack that publishes its own copy can point it elsewhere
with the `mapsemble_sample_app_base` filter.

### Can I keep the credentials out of the database?

Yes — define `MAPSEMBLE_CLIENT_ID` and `MAPSEMBLE_CLIENT_SECRET` in `wp-config.php`
and the settings fields become read-only. One caveat: credentials set that way never
pass through the settings form, which is what normally clears the cached access 
token and plan details. After changing them, delete the `mapsemble_token`, `mapsemble_token_failed`,`
mapsemble_remote_maps`, `mapsemble_feature_flags` and `mapsemble_backoff` transients—
from code, `\Mapsemble\Api\Client::forget_account_caches()` drops exactly that set,
as the settings form and the connect flow do — or the plugin keeps answering for
the previous account for up to fifteen minutes.

### How many posts can a map serve?

The feed is a standard WordPress meta query and is comfortable up to roughly ten
thousand geo-tagged posts. Beyond that, use a persistent object cache. The entropy
sort option additionally needs MySQL 8 or MariaDB 10.2 for its window function; 
on older databases it degrades to a stable per-map random order. The filter option
pickers group over meta values, capped at ten options per lookup.

### What are the public endpoints?

For site-fed maps only: `mapsemble/v1/features` (the GeoJSON feed), `mapsemble/v1/
feature` (one rendered card) and `mapsemble/v1/filter/options` (values for a mapped
filter). All serve published, geo-tagged content that the map’s own conditions admit—
a post excluded by an always-on filter answers 404 exactly like a missing one. Maps
whose locations live in Mapsemble answer 404 on all three. Responses carry `Cache-
Control: public, max-age=60` and an ETag; the cache is refreshed when a served post,
its terms, or the map’s settings change, and developers can tune or disable it with
the `mapsemble_feed_cache_ttl` filter.

### The map preview in the block editor stays blank. Why?

The editor shows a chosen map live in a frame served by this site to a request that
carries no login cookie — the block editor isolates itself in Chromium browsers,
and the frame’s request goes out without cookies. Anything that turns such requests
away before WordPress parses them keeps the preview out: a maintenance or “members
only” plugin that redirects logged-out visitors on `init`, or HTTP basic auth in
front of a staging site. The published page is unaffected; the map still renders
there.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Mapsemble” is open source software. The following people have contributed to this
plugin.

Contributors

 *   [ mapsemble ](https://profiles.wordpress.org/mapsemble/)

[Translate “Mapsemble” into your language.](https://translate.wordpress.org/projects/wp-plugins/mapsemble)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/mapsemble/), check 
out the [SVN repository](https://plugins.svn.wordpress.org/mapsemble/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/mapsemble/) by [RSS](https://plugins.trac.wordpress.org/log/mapsemble/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.5.0

 * Changed: the Mapsemble location editor opens in a new tab, with the map beside
   it, instead of in a frame inside the admin. The sign-in token is minted when 
   you click, not when the screen loads.
 * Added: the block’s map picker is searchable — type part of a name or paste an
   id. Maps are listed newest first with “Another map id…” at the top, and maps 
   that share a name are told apart by their creation date and a short id. The map
   edit screen’s select follows the same order and gains a filter box on long lists.
 * Added: a chosen map renders live in the block editor, and a “Change map” toolbar
   button picks another.
 * Added: “Find an address” in a post’s Map location box looks the address up through
   Mapsemble and fills in the coordinates, with a link to check the spot on OpenStreetMap.
 * Added: with one of your maps chosen, the block’s Filters panel lists that map’s
   filter slugs; clicking one adds it to the initial filters.
 * Added: a map built from this site shows how many posts it currently serves, and
   saving warns about always-on filter terms that do not exist.
 * Added: Mapsemble  Maps is searchable and paginated, newest first, with a Created
   column and All / Hosted on Mapsemble / Built from this site views. The location
   editor’s heading names the map and links back to the list.
 * Added: the Built from this site list shows each map’s shortcodes with a Copy 
   button, and a shortened map id.
 * Changed: the Mapsemble menu reads Maps / Built from this site / Settings. Maps(
   formerly Map data) lists your account’s maps and comes first; the site-fed maps(
   formerly Maps) are under Built from this site. Links are unchanged.
 * Changed: new Map blocks insert as Wide, so desktop visitors get the desktop layout;“
   None” is still a choice. Blocks already set to Wide or Full now render that way
   on the published page; others are unchanged.
 * Changed: with “Fill the visible viewport” off, `height` is the map’s exact height,
   on existing blocks too; with it on, the sidebar calls it “Minimum height”.
 * Changed: switching a block’s “Which map” to “Select a map” clears the sample’s
   still from the canvas, which now just asks which map.
 * Changed: map screens say “Map saved.” instead of “Post published.”, bulk actions
   count maps, and creating a map on Mapsemble from the edit screen confirms it.
 * Changed: the Pro plan note appears once, inline; “Add them on Mapsemble” links
   straight to the map’s filters or sort panel in the Mapsemble builder.
 * Changed: on a map’s edit screen the manual map id is folded away unless the list
   is empty, and the meta-key and ACF inputs show only for their location source.
 * Changed: on Settings, “Finish connecting” appears only once the automatic connect
   gives up, and the uninstall choice has its own Data section.
 * Fixed: a typo in the location box no longer erases the saved location — invalid
   input leaves it untouched and says what is wrong. Comma decimals work, and a 
   pasted “lat, lng” pair fills both fields.
 * Fixed: an unknown or unavailable map no longer leaves a screen-tall blank box—
   visitors see the section collapse, and editors get a notice naming the likely
   cause, on the page and in the block preview.
 * Fixed: a one-click connect or reconnect ends on the “Connected to Mapsemble” 
   notice instead of a silent reload.
 * Fixed: with `MAPSEMBLE_CLIENT_ID` defined in `wp-config.php`, saving the settings
   no longer wipes the stored client ID; a save that only changes the uninstall 
   choice keeps the cached token and map list.
 * Fixed: the “cannot reach this site” warning no longer shows when Mapsemble itself
   runs on your local network; private-network and loopback addresses now count 
   as local.
 * Fixed: an always-on filter whose only slug is `0` no longer drops out and lets
   the map serve every post.
 * Fixed: accessibility — the location-source radios are a fieldset with a legend,
   location box errors, filter matches and copied shortcodes are announced, address
   search keeps focus, and the Maps list’s actions column is labelled.
 * Developer: new REST routes `mapsemble/v1/geocode` and `mapsemble/v1/map-filters`,
   for users who can edit posts; the `loadErrorText` widget setting is gone.

#### 0.4.0

 * Added: one-click connect on Mapsemble  Settings — Authenticate on Mapsemble, 
   approve in the tab that opens, and the page finishes on its own. A “Finish connecting”
   button covers the no-JavaScript case; pasting a client ID and secret by hand 
   is still available in a collapsed section.
 * Added: the block defaults to the sample map, so a freshly inserted block always
   shows a real map. A “Which map” choice switches to your own maps, listed by where
   their data comes from (fed by this site / on your Mapsemble account), and the
   canvas shows a still of the sample map while no map is chosen.
 * Added: suggested privacy-policy text under Settings  Privacy  Policy Guide, naming
   the configured Mapsemble host.
 * Added: the block editor’s strings are translatable — the editor script now carries
   the plugin’s translations.
 * Changed: the sample map is the one shared with the Drupal module and the Framer
   plugin (id `019c09be-4113-7222-95d8-c616d8d7efc1`) and always loads from app.
   mapsemble.com, even when `MAPSEMBLE_APP_BASE` points elsewhere. A block or shortcode
   using `sample` picks the new map up on the next render.
 * Changed: TLS verification of the Mapsemble service is no longer switched off 
   by `MAPSEMBLE_APP_BASE`. Local stacks whose certificate the container does not
   trust must now define `MAPSEMBLE_SSL_VERIFY` as `false` — a DDEV site that relied
   on the old implicit behaviour will fail to connect until it does.
 * Changed: the public feed endpoints answer from a 60-second cache with `Cache-
   Control` and an ETag (a browser revalidating gets a bodiless 304). Saving, trashing
   or deleting a served post, changing one of its terms, or saving the map configuration
   refreshes it; logged-in requests bypass it.
 * Changed: after a 429 from the Mapsemble service the plugin waits as long as `
   Retry-After` says (at most five minutes) before asking again, instead of retrying
   on every admin screen.
 * Changed: site-fed embeds seed the widget with the map’s first configured sort,
   so the card list and the map agree on what comes first.
 * Fixed: the map list no longer shows a map twice when several configurations bind
   the same map id, and a picker with no maps to list still offers a typed id.
 * Fixed: reconnecting from an already connected site works the same as a first 
   connect.
 * Fixed: uninstalling on a multisite network with more than 100 sites now cleans
   every site; uninstall also removes the connect state, the backoff marker and 
   the feed cache counters.
 * Fixed: every “Read more” card link has an accessible name that includes the post
   title; the Map data editor frame sends no referrer.
 * Developer: `mapsemble_map_config_saved` action (`MapConfig $config`, `string 
   $previous_map_id`) fires after a configuration’s meta is written; `mapsemble_feed_cache_ttl`
   filter tunes or disables the feed cache; `mapsemble_sample_app_base` filter for
   a self-hosted Mapsemble that publishes its own copy of the sample; `MAPSEMBLE_SSL_VERIFY`
   constant; `Client::forget_account_caches()` drops every account-derived transient;
   CI fails when the version is stated inconsistently.

#### 0.3.0

 * Added: embed any map by its Mapsemble map id — block picker (account maps, maps
   on this site, a typed id), `[mapsemble map="…"]`, and `mapsemble_embed()`. A 
   map id bound to a site-fed configuration automatically serves from this site.
 * Added: a published sample map — `[mapsemble map="sample"]` — that renders before
   any credentials are entered.
 * Changed: map configurations are source-only; the hosted/site mode choice is gone.
   Existing hosted configurations keep working exactly as before (embeds render,
   feeds keep refusing them) and gain an explicit convert option.
 * Changed: Mapsemble  Map data lists your account’s maps directly — hosted locations
   are editable in-admin for any account map, no configuration post needed. Old 
   links redirect.
 * Fixed: embedding the same map twice on one page now boots both instances.
 * Developer: the `mapsemble_widget_settings` filter’s second argument is now `MapConfig
   |null` — null for embeds of maps this site has no configuration for. Type-hinted
   callbacks need widening.

#### 0.2.0

 * Added: always-on filters — per-map taxonomy/custom-field conditions, so two maps
   on one post type can differ.
 * Added: visitor filter mappings and the `mapsemble/v1/filter/options` endpoint—
   the map’s filter widgets now narrow the served posts.
 * Added: sort mappings, including entropy ordering for an even geographic spread(
   MySQL 8/MariaDB 10.2, with a stable random fallback).
 * Added: marker style properties — taxonomy terms and custom-field values on every
   feature, remaining dots included, for Mapsemble style rules.
 * Added: a generic custom-fields location source — name a latitude and longitude
   meta key, no PHP filter needed.
 * Added: the widget’s interface strings are translatable through the plugin text
   domain.
 * Added: embeds pass a fresh backend endpoint each render (stale data-source URLs
   heal without a re-save), and new `fill_viewport` and `filters` options on the
   block, shortcode and template functions.
 * Improved: creating a map on Mapsemble is an inline form instead of a browser 
   prompt; the map screen opens with a “How this works” explainer.
 * Improved: a Settings link on the Plugins row, and a dismissible pointer to the
   settings screen until credentials are entered.
 * Improved: save notices are tied to the map that produced them and can no longer
   be consumed by another admin page.
 * Fixed: the loading placeholder resolves to an error message when the map widget
   cannot be loaded, instead of spinning forever.
 * Developer: refreshed translation template, guarded by CI against drifting again.

#### 0.1.1

 * Fixed: maps whose locations live in Mapsemble now show their cards — the embed
   no longer installs a card renderer that only site-fed maps can use.
 * Fixed: the Map data screen answers a real 404 for maps that are not edited there.
 * Fixed: a failed connection names the fix — bad credentials point at the client
   ID and secret, an unreachable service points at the connection — and failed sign-
   ins are not retried for a minute.
 * Fixed: saving the settings shows a confirmation notice, and saving a map shows
   every applicable warning instead of only the first.
 * Fixed: the uninstall option describes what is always deleted, not only the opt-
   in part.
 * Fixed: capabilities granted to your own roles survive deactivating and reactivating
   the plugin.
 * Fixed: an unreadable map extent is ignored instead of hiding every location.

#### 0.1.0

 * Initial development version.

## Meta

 *  Version **0.5.0**
 *  Last updated **3 days ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.3 or higher **
 *  Tested up to **7.1.3**
 *  PHP version ** 8.0 or higher **
 * Tags
 * [geolocation](https://wordpress.org/plugins/tags/geolocation/)[interactive map](https://wordpress.org/plugins/tags/interactive-map/)
   [map](https://wordpress.org/plugins/tags/map/)[maps](https://wordpress.org/plugins/tags/maps/)
   [Store locator](https://wordpress.org/plugins/tags/store-locator/)
 *  [Advanced View](https://wordpress.org/plugins/mapsemble/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/mapsemble/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/mapsemble/reviews/)

## Contributors

 *   [ mapsemble ](https://profiles.wordpress.org/mapsemble/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/mapsemble/)