-
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.
-
Understanding the phone-data pipeline & cursor cache (admin view)
A plain-language model of how your app’s data is built and cached, so you can reason about why a change shows up instantly, late, or not at all.
-
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.
-
What your account code is and why it links your site to your app
Your account code is the enrollment ID that ties this WordPress site to your customer record at Tiny Screen Labs, so content, previews, and publishes route to the right app.
-
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.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
