The 21 content-type handlers that drive what the mobile app can render. Each represents one type of mobile UI element (Login, Map, Web URL, etc.). Covers the duck-typed interface, the…
The Login content class — renders the app’s primary auth button and owns the login-related per-button settings. Backed by the user-roles login flow and the legacy mam_user_roles_cred_handler AJAX action.
The Logout content class — clears app session state and triggers the mam_logout / mam_update_current_user actions. Mirrors the Login button; only renders for authenticated users.
The Favorites content class — renders the user’s saved-items list. Source data comes from sibling plugins via the mam_manage_favorites action; mam-main owns the list-rendering and the favorites-sync flags in the…
The Map content class — renders a geographic map with markers. Markers are sourced from a configured WP post type, GeoDirectory post type, or sibling plugin via mam_get_phone_data_before_send. Supports default…
Can't find the answer you're looking for? Don't worry we're here to help!