developer
-
The notification dispatcher: how one action fans out to channels
Why MAM Suite routes every email, SMS, and push through one mam_notification_send_message action, and how the dispatcher fans it out across channels.
-
How sibling plugins extend your app: the filter-driven architecture
Every MAM feature plugin injects into the app through WordPress hooks instead of importing core classes, and filter priority decides the order they run in.
-
How a list-with-detail feature is assembled (geodirectory reference architecture)
How mam-geodirectory assembles a list-with-detail feature: one content class drives list/map/calendar surfaces, content sections, tab-bar buttons, forms, and notifications.
-
Frozen public contracts and the wrap-don’t-rename discipline
Why field-deployed mobile apps and ~2K customer sites freeze MAM Suite’s AJAX names, option keys, hooks, and tables — and how migration lets you evolve them safely.
-
The entitlement model: how plugins gate themselves on license and version
How MAM Suite sibling plugins decide whether to run: the mam_plugin_entitlement filter, an async-synced cache, fail-open behavior, and version checks.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
