Plugin

  • Forms architecture — providers and extensibility

    How mam-main supports multiple form providers (Gravity Forms today, programmatic forms today, additional providers like Ninja Forms via the same extension surface). Explains the two parallel hook namespaces — generic…

  • Forms manager end-to-end cookbook

    A worked example walking a single form from declaration through submission: the mam_gf_get_form_settings entry, slug→field-id admin mapping, cache pre-warm, dynamic data injection, the three row→form surface patterns, and the submission…

  • Forms manager prefill paths (row → form)

    The three patterns a content row can use to open a form: tabbar button, custom_form_array on a row, and content_type=form tap. Each path’s data shape, the iOS resolver site, and…

  • Form submission lifecycle

    End-to-end trace of an app form submission: AJAX POST → mam_gf_processing_form → field validation → mam_for_gravity_forms_form_submitted_{id} → result envelope → mam_form_manager_send_notifications.

  • Content class: Open Notifications

    The Open Notifications content class — opens the in-app notification center showing the user’s history of received notifications. Backed by the wp_mam_notification_history table.

Need Support?

Can’t find the answer you’re looking for? Don’t worry we’re here to help!