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.
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…
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 fired when the in-app purchase subscription state shifts. Sibling plugins (typically mam-inapp-purchase-manager) update entitlements, gate features, or dispatch notifications.
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.
Can't find the answer you're looking for? Don't worry we're here to help!