explanation
-
Why MAM Suite extends through filters and actions only (the no-import rule)
Sibling plugins never import mam-main classes; they hook its filters and actions. Why that decoupling is what lets MAM Suite scale to 9+ plugins across ~2K sites.
-
Tab bar vs. left menu vs. home buttons: choosing your navigation model
Your app gets three separate navigation surfaces — home buttons, the left menu, and the bottom tab bar. Here’s what each one is for, and how to put them together.
-
What the Activity screen is and when to use it
MAM Suite’s Activity screen is where field work gets checked in — routes, punch-ins, and site visits included. Here’s what it does and when to turn it on.
-
The security and role model: app-request auth, the pid soft-nonce, capabilities
How MAM authenticates app requests from a device pid, why app AJAX leans on a soft-nonce model, where capability checks live, and who sanitizes input.
-
The settings cascade: how global, per-role, and per-button settings resolve
Why a setting resolves to the value it does — the per-button, per-role, and global fallback chain behind mam_app_settings_get_setting, and where to write.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
