• Actions

    Developer reference for the WordPress action hooks MAM Main fires for extending it in code.
  • Forms manager hook reference

    Every form-manager hook in firing order: signature, when it fires, expected return shape, real example. Plus the $local_app_form_array global and the option-key conventions that glue the system together.

  • Action: mam_app_user_invite_accepted (invite lifecycle)

    Actions fired when an app-user invite changes status (pending → accepted/declined/revoked). Lets a plugin provision a user the moment they accept an in-app invite — set roles, attach to a…

  • Action: mam_form_manager_send_notifications

    The contract between forms-manager and notifications-manager. Fired after a form submission completes; subscribers fire mam_notification_send_message to dispatch confirmation emails / pushes / SMS. Frozen contract — go through this hook,…

  • Action: mam_main_iap_subscription_has_changed

    Action fired when the in-app purchase subscription state shifts. Sibling plugins (typically mam-inapp-purchase-manager) update entitlements, gate features, or dispatch notifications.

  • Action: mam_manage_favorites

    Action fired when the app reports a favorite-toggle event. Sibling plugins subscribe to persist the change in their own usermeta — mam-geodirectory uses gd_user_favourite_post.

Need Support?

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