Goal
Configure how mobile-app reviews and ratings behave and read, all from one place: Mobile App Manager → Reviews. These settings used to live inside MAM Main’s app-settings array; as of 26.23.0 they have their own dedicated screen, and each one is a plain WordPress option the providers and content sections read directly.
Before you start
mam-reviews-manageris active and you can see Mobile App Manager in the WordPress admin menu.- You have
manage_optionscapability (administrator).
Steps
- In the WordPress admin, go to Mobile App Manager → Reviews.
- Set each option (table below).
- Click Save Settings.
Changes take effect on the next app data refresh — the text/behavior fields are pushed to the app in the global app (phone) data, and the rating-behavior fields are read server-side when sections are built and reviews are saved.
The settings
| Setting | Choices | Default | What it controls |
|---|---|---|---|
| New reviews are inserted as | Approved / Pending | Pending | Whether a submitted review is immediately visible or held for moderation. Pending reviews return a pending flag to the app so it shows the pending message instead of the confirmed one. |
| Rating display | Stars / Numeric | Stars | How a rating value renders. Input is always a 1–5 selector; this only switches between star glyphs and a number badge (e.g. 4.5). |
| Require login to review | Yes / No | Yes | Whether the add-review form requires the user to be signed in. |
| Allow review photos | Yes / No | Yes | Whether the add-review form offers a photo picker. |
| Link reviews from Home screen to Reviews screen? | Yes / No | No | If Yes, tapping the reviews summary on the Home screen opens the full Reviews screen. |
| Reviews title | text | (empty) | Overrides the title shown above the reviews list. |
| My Reviews text | text | (empty) | Label for the current user’s own reviews grouping. |
| Confirmed review message | text | (empty) | Message shown after a review is submitted and immediately approved. |
| Pending review message | text | (empty) | Message shown after a review is submitted but held pending approval. |
Leaving a text field empty uses the app’s built-in default for that label.
How these reach the app
- Behavior fields (approval, rating display, login, photos) are read on the server when the
add_review/reviews_headersections are built and when a submission is saved — they shape the section payload and the saved comment’s approval state. - Text & linking fields are injected into the global app (phone) data via the
mam_get_phone_data_before_sendfilter (keysreviews_title_text,my_reviews_text,reviews_confirmed_message,reviews_pending_message,reviews_open_review_screen), so the app can read them once, globally, rather than per listing.
Notes
- The approval option is the frozen key
tsl-setting-reviews_automatically_approveand is read withtsl_mam_get_option_value(); the screen tolerates the legacy MAM-Main array storage when reading the current value, so upgrading sites keep their existing choice. - Each non-text field only accepts one of its declared option slugs — anything else falls back to that field’s default — so a malformed POST can’t store a junk value.
Related articles
- Plugin: mam-reviews-manager
- Reviews content sections
Metadata
| Field | Value |
|---|---|
| Article type | Recipe (Admin) |
| Plugin slug | mam-reviews-manager |
| Applies to plugin version | 26.23.0+ |
| Category | Building Your App |
| Audience | WordPress admin |
| Estimated time | 5 minutes |
| Last verified | 2026-06-04 |
