Primary responsibility

mam-geodirectory registers fourteen tab bar action buttons against listing detail screens. The full set is declared in mam_geodirectory_content::tab_bar_manager_buttons(); per-button behavior (icon, action, source) is built by mam_gd_tab_bar_buttons and mam_gd_claim_listing_manager. Each button corresponds to a mam_main_add_tab_bar_item_* filter (owned by mam-main); this plugin subscribes to those filters and decides whether the button should appear for the current user/listing combination.

This article documents what each button does, when it appears, and which option/permission gates it.

The fourteen buttons

Visibility logic in detail

mam_main_skip_tab_bar_button — the role-aware skip filter

When the current viewer is the owner / manager / admin / staff of the listing, the buttons listed in $exclude are skipped:

$exclude = ['website', 'email', 'phone', 'favorites', 'map', 'share', 'chat'];

This is intentional — owners and staff get owner-style action buttons (Edit Listing, Edit Staff, Send Notification, etc.) instead of consumer-style ones. The chat button is re-allowed for admins specifically, but only when the listing has at least one non-admin staff or manager (to avoid an empty chat group).

For non-staff users, the chat button is suppressed if the listing has no staff/managers at all (get_manager_or_staff_for_location($id, 'all') returns empty).

claim_listing — three-state title

The Claim Listing button renders one of three forms based on the user’s current claim state:

1. “Claim Pending” — when GeoDir_Claim_Post::is_claim_pending($post_id) returns true. Action is empty (the button just informs).
2. “Request to Claim” — when mam_gd_claim_requires_approval is 'yes' and the user has no approval flag (_mam_claim_approved_{post_id} user meta). Action is claim_request.
3. “Claim Listing” — when ready for purchase. Action is open_claim_purchase; payload includes the configured packages, the checkout mode, the CTA text, and the features list.

The button is hidden entirely when the listing is already claimed, when the GeoDir Claim Manager plugin is not active, when the listing’s post type does not support claiming, or when the current user is the listing’s author.

send_notifications — quota gate

The button checks pn_sent_{YYYY_MM} post meta on the listing against the package’s pn_per_month. When the count meets or exceeds the cap, the button is suppressed for the rest of the calendar month. Counts reset implicitly on the first of the next month.

edit_staff — pre-fill array

The button’s source is an array of sub-forms — one per existing staff member, pre-filled with their first/last name, user ID, email, and current role; plus one “Add Staff Member” form when below the staff cap. The app renders this as a list view inside a modal. Each sub-form points at the same Add Users Gravity Form ID; the app sends back which one was edited.

For each sub-form, the plugin can also exclude specific fields by ID — used to hide the Reinvite User, Delete User Check, and Delete User fields on the “Add” sub-form (those only make sense when editing an existing staff member).

Allow-admin-to-do-stuff toggle

mam_gd_tab_bar_buttons only treats an admin as elevated when the request includes ?pid=.... Without pid, an admin sees consumer-style buttons. This isolates admin-only buttons (Edit Listing, Approve Listing) to admin-mode views — a normal browse of the directory by an admin doesn’t show them.

The PLUGIN_AUDIT.md previously called out the gd-admin-can-edit-all-listings option as the intended gate, but the runtime currently reads ?pid instead. If you need true admin-everywhere editing, set the request parameter or override via Hook: mam_geodirectory_explcit_listings in custom flows.

Gotchas

• The share button uses the in-app share sheet. It does not respect any custom URL filtering.
• chat requires mam-chat-manager. Without it, no chat button is registered (see tab_bar_manager_buttons()).
• Quota and staff caps are silent. When the send_notifications or edit_staff cap is hit, the button simply disappears with no on-screen explanation. Document the limit in your in-app onboarding to avoid support tickets.
• edit_listing requires both the post-type form AND gd-author-can-edit-on-app. Either gate alone hides the button.
• approve_listing requires admin AND status pending/draft. Admins viewing a published listing do not see this button.

Verification

This article was last verified against:

• Plugin: mam-geodirectory v2.1.5
• Source: includes/mam_gd_tab_bar_buttons.php
• Source: includes/mam_gd_claim_listing_manager.php
• Source: content-classes/local-app-geodirectory-v2-class.php — tab_bar_manager_buttons()

Re-verify whenever a button is added or removed, the $exclude list in mam_app_settings_tab_bar_button_skip changes, the package-meta keys (pn_per_month, no_of_staff_members) are renamed, or the claim-button state machine in mam_gd_claim_listing_manager::tab_bar_button changes.

Related articles

• Plugin: mam-geodirectory
• Listing detail content sections
• 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
• Recipe: Pricing package fields
• Integration: Chat Manager
• Integration: Special Offers

Metadata