What it does

mam-geodirectory is the largest of the no-code MAM plugins. It connects the WordPress GeoDirectory plugin (a third-party directory/listing/event CMS) to the MAM mobile app pipeline. Once active it:

• Turns every registered GeoDirectory post type (typically gd_place plus any custom CPTs the site adds, except gd_event which is treated specially) into a mobile content surface — list, map, calendar, off-directory, and admin-approval views.
• Builds a per-listing detail screen out of MAM “content sections” (address, business hours, social media, events, post content, favorite/check-in, event details).
• Adds tab bar action buttons to listing screens — Edit Listing, Edit Staff, Edit Events, Send Notification, Claim Listing, Approve Listing, Share — visible only to the right user role for the current listing (owner, manager, staff, admin, or anonymous viewer).
• Registers seven Gravity-Forms-backed mobile forms — Add/Edit Listing, Send Notification, Add Users (Staff/Manager invites), Manage Invite, Approve Listing, Claim Listing, Add QR Code — and a per-post-type Add/Edit Listing form.
• Provides an admin Settings page (per-post-type tabs plus a global tab and a Claim Listings bulk-invite tool) that wires those forms and toggles to per-app behavior.
• Hooks into other MAM plugins: feeds GeoDirectory cities into mam-geofilters, exposes per-listing coordinates and radius to mam-special-offers, gates In-App Purchase requirements via mam-inapp-purchase-manager, and joins owners/staff/managers to listing chat groups in mam-chat-manager.

Most installations are configuration-first: install GeoDirectory, install this plugin, fill in the Gravity Form IDs on the Settings page, and the listings start appearing in the app. The hooks listed above are the developer extension points for everything that configuration cannot express.

Setup paths

There is one canonical setup path. The plugin will silently no-op if any of these are not satisfied:

1. The WordPress plugin geodirectory/geodirectory.php is present and active.
2. mam-main is installed and the entitlement filter mam_plugin_entitlement returns a non-blocked record for the slug mam-geodirectory.
3. mam-main is at least version 1.9.1 (checked on admin_init).

When all three are true, mam_geodirectory_manager::init() runs on plugins_loaded and registers the full hook set described in this article.

Where it appears in the app

See Content type: GeoDirectory list and map and the related screen articles for the per-surface details.

Default fields and behavior

• GeoDirectory post types are auto-discovered via geodir_get_posttypes(). gd_event is treated as a separate event surface; everything else (gd_place and any custom GD CPTs) is treated as a “listing.”
• Listing data shape sent to the app is built in mam_geodirectory_content::get_data_for_app() (aliased as local_app_geodirectory). It normalises post_id → id, latitude/longitude → lat/lon, business_hours → raw_business_hours, etc., then layers on category data, marker icons, images, social platforms, claim status, and (when enabled) a chat tab. See Mobile listing data shape.
• Search radius defaults to 25 miles (or 100 for the initial query before falling back to default coordinates). The role-scoped setting tsl-setting-geofilter_radius overrides it; ?radius= on the request overrides everything (capped at 3000).
• Pending and draft listings are visible to the listing’s author and to admins; everyone else only sees published listings. Admin-approval mode (category=999999 for an admin) returns only pending rows.

Mobile JSON contract — flags and feeds

mam-geodirectory writes into the mobile JSON payload via mam_get_phone_data_before_send. The keys it sets are part of the frozen mobile contract — renaming them will break deployed apps.

Per-listing rows additionally carry claim_status and can_claim when the GeoDir Claim Manager plugin is active. See Mobile listing data shape for the full per-listing field map.

Admin surfaces

Hooks exposed

The hooks below are owned by this plugin. Each has its own dedicated article — see Related articles.

The plugin also fires mam_notification_send_message (mam-main contract) when sending push notifications, and mam_get_main_qr_code / mam_create_qr_code for the in-app QR feature. Those names belong to mam-main and are documented there.

The plugin subscribes to a large set of mam-main, mam-special-offers, mam-chat-manager, mam-geofilters, mam-inapp-purchase-manager, and GeoDirectory hooks. Those are documented in their owning plugin’s reference, not here. The most important to know about:

• mam_get_phone_data_before_send, mam_tab_manager, mam_main_ajax, mam_manage_favorites, mam_main_skip_tab_bar_button, mam_main_add_tab_bar_item_*, mam_content_section_* — all owned by mam-main.
• mam_geofilter_list — owned by mam-geofilters. This plugin populates GD-derived cities into it.
• mam_specials_get_post_lat, mam_specials_get_post_lon, mam_specials_get_post_radius, mam_special_offers_deals_allowed, mam_special_offers_hard_skip_tab_bar_button — owned by mam-special-offers.
• mam_iap_require_iap — owned by mam-inapp-purchase-manager.
• mam_for_gravity_forms_form_result_form_{id}, mam_gravity_forms_after_form_processed_{id}, mam_gf_get_form_settings, mam_gf_get_custom_form, mam_gf_get_custom_forms_list, mam_gf_get_form_from_cache, mam_generated_forms, mam_add_prog_form — owned by the Gravity Forms manager.
• geodir_pricing_package_settings, geodir_pricing_process_data_for_save — owned by GeoDir Pricing.
• mam_gd_staff_member_accepted and mam_gd_staff_member_removed — these are subscribed to here for chat-group maintenance, but the plugin does not fire them; whichever component fires them lives outside this plugin. See Integration: chat manager for context.

Common tasks

• Configure the per-post-type forms and toggles → Recipe: Configure the GeoDirectory settings page
• Add custom fields to a listing pricing package → Recipe: Pricing package fields
• Add staff or managers to a listing in WordPress admin → Recipe: Manage staff and managers (admin)
• Bulk-invite venue owners to claim their listings → Recipe: Bulk-invite venue owners
• Understand the data the app receives for each listing → Mobile listing data shape
• Build the listing detail screen → Listing detail content sections
• Decide which tab bar button shows for whom → Listing tab bar buttons
• Let users add or edit listings from the app → Form: Add/Edit Listing
• Let venue owners send push notifications from the app → Form: Send Notification
• Let venue owners invite staff from the app → Form: Add or remove staff and managers
• Let users claim a listing → Form and flow: Claim Listing
• Approve user-submitted listings from the app → Form: Approve Listing
• Replace the listings array entirely (bypass the GD query) → Hook: mam_geodirectory_explcit_listings

Verification

This article was last verified against:

• Plugin: mam-geodirectory v2.1.5
• mam-main (required)
• GeoDirectory plugin (required)
• mam-geofilters, mam-special-offers, mam-chat-manager, mam-inapp-purchase-manager, mam-gravity-forms-manager, mam-reviews-manager (optional integrations)

Re-verify whenever a hook is added or removed, the bootstrap class adds or drops a sub-class instantiation in mam_geodirectory_manager::__construct(), the listing-row keys produced by mam_geodirectory_content::get_data_for_app() change, the seven mobile forms are renamed or split, or the admin Settings tab structure changes.

Related articles

• Recipe: Configure the GeoDirectory settings page
• Recipe: Pricing package fields
• Recipe: Manage staff and managers (admin)
• Recipe: Bulk-invite venue owners
• Content type: GeoDirectory list and map
• Listing detail content sections
• Listing tab bar buttons
• Mobile listing data shape
• Form: Add/Edit Listing
• Form: Send Notification
• Form: Add or remove staff and managers
• Form: Approve Listing
• Form and flow: Claim Listing
• Form: Manage staff invitation
• Form: Add QR Code
• Integration: GeoFilters
• Integration: Special Offers
• Integration: Chat Manager
• Integration: In-App Purchase Manager
• Integration: WooCommerce pricing packages
• GeoDirectory notification types
• Hook: mam_geodirectory_add_edit_form_fields
• Hook: mam_geodirectory_admin_settings_tabs
• Hook: mam_geodirectory_admin_settings_tabcontent{tab}
• Hook: mam_geodirectory_admin_settings
• Hook: mam_geodirectory_event_card
• Hook: mam_geodirectory_explcit_listings
• Hook: mam_geodirectory_final_listings
• Hook: mam_geodirectory_skip_record
• Hook: mam_geodirectory_send_notification_users
• Hook: mam_gd_date_format
• Hook: mam_gd_social_icons_only
• Hook: mam_gd_events_exclude_from_map
• Hook: mam_gd_send_notification_types
• Hook: mam_gd_get_event_schedule
• Hook: mam_gd_manage_favorites

Metadata