CMS SaaS 2026.3 Release Notes

Highlights

• Content approval workflows are now available, enabling multi-stage review before publication.
• Graph sync performance improved by approximately 40% for large content sets.
• Bulk media upload supports up to 100 files in a single operation.
• The Legacy Media Upload API (v1) is deprecated and will be removed in 2026.6.

---

New features

Content approval workflows

Content now moves through configurable approval stages before publication. Administrators define approval stages (for example: draft, review, legal, publish), assign reviewers to each stage, and set whether approval is sequential or parallel.

How to use it:

1. Navigate to Settings > Workflows > Approval Stages.
2. Create stages and assign reviewers.
3. Enable the workflow for specific content types.

Editors see the current approval stage in the content toolbar and can submit content for review with a single click.

For details, see Manage Users and Permissions.

Bulk media upload

Upload up to 100 files at once through the media library. Drag and drop files onto the upload area or use the file picker. The system processes uploads in parallel and reports results for each file.

Supported formats: JPEG, PNG, WebP, SVG, GIF, PDF, DOCX, MP4.

Maximum file size: 50 MB per file (unchanged from previous releases).

---

Improvements

Graph sync performance

Content sync to Optimizely Graph is approximately 40% faster for repositories with more than 10,000 content items. The improvement comes from batched indexing and reduced network round trips during full sync operations.

No configuration changes are needed. The improvement applies automatically.

Content tree navigation

The content tree sidebar now loads child nodes on demand instead of pre-loading the entire tree. This reduces initial load time for sites with deep content hierarchies (1,000+ pages).

Rich text editor

• Added support for pasting tables from Google Sheets and Excel.
• Improved link insertion dialog with inline search for internal content.
• Fixed an issue where nested lists lost formatting on save.

---

Bug fixes

• Fixed an issue where scheduled publish failed silently when the publish time fell during a maintenance window.
• Fixed an issue where content area drag-and-drop stopped working after adding more than 20 blocks.
• Fixed an issue where the media library search did not return results for files with special characters in the name.
• Fixed an issue where version comparison showed incorrect diff highlights for content areas with personalized blocks.

---

Breaking changes

Media Upload API response format

What changed: The /api/media/upload endpoint now returns a JSON response with a results array instead of a single file object. This aligns the single-file and bulk upload responses.

Previous response:

{
  "file": { "id": "abc", "name": "photo.jpg", "url": "..." }
}

New response:

{
  "results": [
    { "id": "abc", "name": "photo.jpg", "url": "...", "status": "success" }
  ]
}

Why: The unified response format supports both single-file and bulk upload scenarios without conditional response parsing.

Migration: Update client code that reads the file property to read results[0] instead. The old format is no longer returned.

Affected versions: All API clients using /api/media/upload.

---

Deprecations

Legacy Media Upload API (v1)

Deprecated in: 2026.3

Removal planned: 2026.6

What is changing: The v1 media upload API (/api/v1/media) is deprecated. All upload operations should use the v2 API (/api/v2/media).

Migration path: Replace v1 endpoint references with v2. The v2 API accepts the same parameters but returns the new response format and supports bulk operations. See the Media Upload API reference for the v2 specification.

---

Known issues

• Bulk upload progress indicator may show 100% before all files finish processing when uploading more than 50 files. The upload completes correctly; only the progress display is affected. A fix is planned for 2026.4.