Configure forms: photos, location capture, and required fields

Forms in a MAM app can do more than collect text. They can snap a photo, grab the user’s current GPS position, and fill in address fields from that position automatically. Here’s where each of those controls lives and how to set it up.

One thing worth knowing before you dive in: every setting below applies to all the forms your app renders for the role you’re editing, not just one form. If you need different behavior on different forms, that’s a job for your developer — these toggles work at the role level, not per form.

Goal

By the end you will be able to:

  • Set the pixel size and file format (JPEG or PNG) of photos captured through forms.
  • Add a “use my location” button to forms and have address fields auto-fill from GPS.
  • Require that form photos come from the camera, blocking photo-library uploads.

Prerequisites

  • MAM Suite installed with MAM Main active.
  • Access to Mobile App Manager → App Settings in WordPress admin (an admin-level account).
  • For the location features, your form must actually contain the relevant fields (a location/GPS field, and address fields for auto-fill). The settings here turn the behavior on; the form still has to have somewhere to put the data.
  • An icon image hosted at a public URL if you want a custom graphic on the location button.

Where these settings live

Everything in this guide lives on the App Settings page, inside the Gravity Forms section. Don’t let the name throw you — several of these settings apply to MAM forms generally, not just Gravity Forms. Think of it as the catch-all “forms” group.

To get there:

  1. In WordPress admin, open Mobile App Manager.
  2. Open App Settings, and pick the user role you’re configuring (start with mam-all).
  3. Scroll to — or use the section links at the top of the page to jump to — the Gravity Forms section.

The whole App Settings page works this way — sections with a row of jump links up top — so clicking Gravity Forms in that row takes you straight there without any scrolling.

Note: what you change here feeds into the app configuration your devices download. Depending on your setup, the app may need a refresh — reopening it, or pulling a new config — before you’ll see the new behavior.


Step 1 — Set the photo size and format

Two settings control how photos captured through forms are processed before upload.

  1. Find Photo size (Square) (forms_photo_size) — a text field where you set the target size, in pixels, for square photos captured or uploaded through forms. A value like 1024 gives you roughly 1024 x 1024 images. Go bigger for higher-resolution photos (and bigger uploads); go smaller for faster uploads and less storage. Pick whatever balance suits your users.

  2. Find Use JPEG instead of PNG for images? (forms_use_jpeg) — a yes/no toggle for the file format form photos are uploaded in.

    • On — form photos are uploaded as JPEG. Smaller files, faster uploads. Best for photographs.
    • Off — form photos are uploaded as PNG. Larger files, lossless. Choose this only if you specifically need PNG (for example, images where sharp edges or transparency matter).

For most apps that collect real-world photos, turn Use JPEG on and choose a sensible square size.

  1. Optionally, find Show Image Placeholder in Image UI Element (form_show_image_placeholder). Turn it on and image fields show a placeholder graphic that makes it obvious where to tap to add an image.

Save the page.


Step 2 — Require photos from the camera (optional)

Want to be sure a photo was taken live, not pulled from someone’s existing library? Here’s how:

  1. Find Only photos from camera…no library access (require_camera_for_forms) — a yes/no toggle.
  2. Turn it on to restrict image fields to the camera only — users cannot pick an existing image from their photo library.
  3. Save the page.

Use this when the photo needs to be proof of something happening now (an inspection, a delivery, a damaged item) rather than any picture the user happens to have. Leave it off if users should be free to upload existing photos.


Step 3 — Add a location-capture button

The location button lets a user drop their current GPS position into a form with one tap.

  1. Find Location button URL (form_location_button) — a text field for the URL of the icon/image that becomes your “use my location” button on forms.
  2. Paste the public URL of the icon image you want to use for that button.
  3. Save the page.

Use a square icon hosted somewhere publicly reachable — your media library works well. The app turns that image into the tappable location button on any form with a location field.


Step 4 — Auto-fill address fields from GPS (reverse geocoding)

Reverse geocoding turns the device’s GPS coordinates into a human-readable address and drops it into your form’s address fields automatically.

  1. Find Automatically fill reverse GPS fields (auto_reverse_geo) — a yes/no toggle.
  2. Turn it on.
  3. Save the page.

When on, address fields on forms are auto-filled from the device’s current GPS location using reverse geocoding — the user does not have to type their street, city, state, and ZIP by hand.

Just remember: the form still needs actual address fields for the result to land in. Pair this with Step 3 so the user has an obvious button to capture their location in the first place.


Putting it together: a “report an issue with a photo” form

A common pattern combines several of these settings:

  • Use JPEG on, Photo size set to a moderate square value — small, fast photo uploads.
  • Only photos from camera on — the photo must be taken on the spot.
  • Location button URL set, and Automatically fill reverse GPS fields on — one tap captures where the user is and fills in the address.

The result: a field-report form where the photo is guaranteed live and the location gets captured with barely any typing.


Verify

  1. Open (or refresh) the app on a test device.
  2. Go to a form that contains an image field and a location/address field.
  3. Confirm the image field behaves as configured — placeholder shown if you enabled it, and (if you required the camera) that only the camera opens, with no library option.
  4. Tap the location button and confirm the address fields fill in.
  5. Submit a test photo and confirm the uploaded image matches the size and format you set.

  • App setting reference: Photo size (Square) (forms_photo_size)
  • App setting reference: Use JPEG instead of PNG for images? (forms_use_jpeg)
  • App setting reference: Only photos from camera…no library access (require_camera_for_forms)
  • App setting reference: Location button URL (form_location_button)
  • App setting reference: Automatically fill reverse GPS fields (auto_reverse_geo)
  • App setting reference: Show Image Placeholder in Image UI Element (form_show_image_placeholder)

What’s next

  • If you are building the form itself (rather than just tuning these app-wide toggles), see the contact form and Gravity Forms setup recipes for how fields are defined and where the form is placed in the app.
  • If you need photo or location behavior to differ between two forms, flag it for your developer — these settings are global.

Last verified against mam-main/includes/app-settings/admin-settings-page.php (category forms).

Was this article helpful?
Contents

    Need Support?

    Can't find the answer you're looking for? Don't worry we're here to help!