Primary responsibility

Renders a geographic map with markers. Markers come from:

• A configured WP post type (post category)
• A GeoDirectory post type (when mam-geodirectory is active)
• Any sibling plugin contributing markers via mam_get_phone_data_before_send at the right priority

Settings

JSON shape (marker)

{
  "id": "123",
  "title": "Venue name",
  "lat": "40.7128",
  "lon": "-74.0060",
  "marker_icon": "https://...",
  "snippet": "Short description"
}

lat/lon are strings (frozen — older mobile parsers reject numeric coordinates).

Hooks involved

The Map content class doesn’t fire dedicated hooks. Markers are usually contributed by sibling plugins:

• mam-geodirectory: mam_geodirectory_explcit_listings, mam_geodirectory_final_listings, mam_gd_events_exclude_from_map
• mam-special-offers: mam_specials_get_post_lat, mam_specials_get_post_lon, mam_specials_get_post_radius
• mam-geofilters: contributes per-region marker subsets

The Map class consumes geofilter_default_name and the geofilter radius from the JSON payload.

Gotchas

• lat/lon are strings. Don’t emit numeric values — older mobile parsers fail.
• Default coords are global, not per-button. All maps in the app share default_lat/default_lon.
• Search radius defaults differ between the initial query (100) and subsequent queries (25). The role-scoped setting tsl-setting-geofilter_radius overrides the default; ?radius= on the request overrides everything (capped at 3000).
• Map rendering is the mobile client’s job. mam-main provides the markers; the app uses a native map view (Apple Maps / Google Maps depending on platform and config).

Related articles

• Content classes overview
• Hook: mam_get_phone_data_before_send
• Mobile JSON shape

Metadata