updateMultiImagePost
Edit album metadata (title, description, status) and append photos to an existing group using comma-separated image URLs. Requires group ID.
Instructions
Update an album group - Update an existing portfoliogroup record by ID. Fields omitted are untouched. Writes live data.
Use when: editing metadata (title, description, group_status) OR appending photos via post_image CSV + auto_image_import=1 (APPENDS, does not replace). Existing photos are edited via updateMultiImagePostPhoto (title/order only).
Required: group_id.
Enums: group_status: 0=Draft, 1=Published.
Verify appended photos via listMultiImagePostPhotos, NOT via getMultiImagePost.post_image. The parent's post_image field is a transient write-through, not a mirror of child rows — it does NOT reflect appended photos. Child rows land in users_portfolio. Silent-failure possible (empty file, image_imported=0) — check each child row.
group_name rename does NOT update group_filename (the URL slug). group_filename is writable — see Rule: URL slug rename for when to suggest a slug update + redirect. Report group_filename from getMultiImagePost when giving the user a URL.
See also: createMultiImagePost, deleteMultiImagePost, deleteMultiImagePostPhoto.
Returns: { status: "success", message: {...updatedRecord} } - photo rows land asynchronously.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes | ||
| group_name | No | ||
| group_filename | No | Public URL slug path (e.g. `photo-albums/my-slug`). Writable — BD does NOT regenerate the slug when `group_name` changes. See **Rule: URL slug rename** for when to suggest a slug update + redirect. | |
| group_desc | No | Album description HTML. Froala body field — see **Rule: Post-body formatting** (structure, `fr-dib fr-fil`/`fr-fir` float + inline `width: 350px`, landscape Pexels images). | |
| group_status | No | 0=Not Published, 1=Published, 3=Pending Approval (rare — set when site admin requires manual moderation before albums go live). | |
| post_tags | No | Comma-separated keywords for the album. | |
| auto_geocode | No | ||
| auto_image_import | No | **Auto-import images to site storage.** Set `1` when any external image URL field on this multi-image post holds a URL - BD fetches and saves each image locally. Without the flag, BD stores URLs as-is; images break if source hosts go down. **Recommended default when supplying external image URLs**; omit or set `0` only if user explicitly wants external URL references. Supports JPG/PNG/GIF/WebP/SVG. Processing delay: several minutes per image. | |
| post_image | No | Comma-separated image URLs — APPENDS new photos (does NOT replace existing). **LANDSCAPE only — verify each candidate's orientation via `getImageDimensions` per **Rule: Image dimensions** before commit; bare URLs, no `?query`, each must end in `.jpg`/`.jpeg`/`.png` (WebP/GIF/AVIF skipped pre-tool per the same rule) — see **Rule: Image URLs**.** Query strings get baked into imported filenames and 404. Pair with `auto_image_import=1` to fetch externals into site storage. | |
| _clear_fields | No | Column names to clear to empty string. Available on every `update*` operation. Works on base columns AND EAV/`users_meta` rows (rows preserved with `value=""`). To actually clear a field you MUST use this parameter — sending the field with `""` alone is a no-op (BD drops empty values). To remove a `users_meta` row entirely, use `deleteUserMeta`. See **Rule: Clearing fields**. Example: `_clear_fields: ["h2", "hero_link_url"]`. |