Umbraco 17.7 and 18.2: Editor Workflow Updates
Learn what Umbraco 17.7 and 18.2 change for editors, which version fits your roadmap, and how to test bulk publishing, pickers, media and upgrades.
Umbraco released CMS 17.7.0 and 18.2.0 on 17 September 2026. Both releases include the same headline improvements for bulk actions, collections, pickers, media handling and the document tree, alongside performance work and fixes for publishing, preview, migration and rich-text behaviour.
This is not a reason to jump from Umbraco 17 to 18. Umbraco 17 is the current Long-Term Support release, while Umbraco 18 is a Standard-Term Support release. The useful story is that teams on either supported line can adopt the September workflow improvements without changing their major-version strategy.
For Australian businesses, the release is commercially relevant because small reductions in repetitive editor work compound across campaign launches, catalogue updates, media libraries and multi-site estates. The value is clearest when the upgrade is paired with a short workflow review and measurable before-and-after checks—not when it is treated as a feature list.
What editors gain in September
The strongest changes reduce uncertainty during bulk work and make large content trees easier to navigate.
Visible bulk progress
A shared progress dialog now reports bulk publish, unpublish, delete, move and copy operations.
Persistent collections
Collections remember the selected view, filter, ordering and page instead of resetting the editor's working context.
Clearer pickers
Browse and search are separated, selected-item counts are visible, and ancestor paths help distinguish similar media.
Flexible tree views
The document tree gains card and table views for teams working across different content structures and screen sizes.
Umbraco 17.7 or 18.2: which release applies?
If your website is already on Umbraco 17, update within the 17 line and test 17.7. If it is already on Umbraco 18, test 18.2. A minor update is different from a major-version migration: it should not be used as a reason to change support strategy without reviewing the site's packages, custom extensions, hosting model and roadmap.
Umbraco 17 is the current LTS release. Umbraco lists its end of support as 27 November 2027 and end of life as 27 November 2028. Umbraco 18 is STS, with security phase beginning 25 March 2027 and end of life on 25 June 2027. Businesses that prioritise a longer maintenance horizon will usually prefer 17 unless they specifically need capabilities introduced in 18, such as the Library and Elements.
Umbraco's own versioning guidance says active majors receive minor releases on a six-week cadence and that these minors include features and bug fixes without breaking changes. That lowers the expected risk, but it does not remove the need to test packages, custom backoffice extensions, integrations and business workflows.
Bulk operations are easier to supervise
Before this release, editors could start bulk operations but had less consistent feedback about progress. Umbraco 17.7 and 18.2 introduce a shared progress dialog for bulk publishing, unpublishing, deleting, moving and copying. The release also fixes collection-table selection so selections can accumulate across pages.
The business benefit is not simply a nicer dialog. A content owner can see whether a large operation is still running, distinguish completion from a stalled interface, and avoid repeating the same action because the outcome was unclear. That matters when a campaign, product range, language set or section of a multi-site estate changes at once.
Progress visibility does not turn a high-impact action into a low-risk one. Keep permissions narrow, filter the working set before selecting it, review the destination and language, agree who can approve mass unpublish or delete operations, and retain a recovery path. Test the progress dialog with a representative batch in staging before relying on it during a launch window.
Editors keep their place in large collections
Collections now remember the editor's view, filter, ordering and page. That sounds small, but it removes a recurring interruption in product catalogues, news archives, people directories, locations and other content types that editors manage as lists.
A useful acceptance test is simple: configure the collection as the team normally works, open an item, complete or cancel the edit, and return to the collection. Verify that the chosen view, filter, ordering and page remain intact. Repeat with browser refresh, a second collection and the roles used by real editors.
Measure the improvement using a task such as finding and updating ten records from the same filtered list. Compare completion time, repeated clicks and navigation errors before and after the upgrade. This turns a subjective preference into evidence for whether the new workflow is helping.
Upgrade the CMS and verify the work
Pickers and media libraries need less guesswork
Several changes target the moment an editor chooses content or media. Pickers now split browse and search into separate tabs, show how many items are selected, and let editors navigate rows or cards that contain children. The media picker can show the ancestor breadcrumb path in table search results, helping editors distinguish files with similar names stored in different folders.
Umbraco also added a drag-and-drop call to action for media collections and pickers. For teams that upload campaign assets, staff photos or product media repeatedly, these changes can reduce mis-selection and make the intended action more obvious.
Test with the difficult cases in your real library: duplicate filenames in different folders, deeply nested folders, a large multi-select, restricted start nodes, non-image files and a search term that returns similar assets. Verify the chosen asset, crop and link in preview and on the rendered website—not only inside the picker.
Match each feature to a business task
Choose representative work from your own content operation and prove whether the release reduces friction.
Campaign launch
Publish a controlled page set and confirm progress, completion, language and final public URLs.
Catalogue maintenance
Filter a large collection, update multiple records and confirm the list preserves working context.
Media reuse
Search duplicate filenames, use folder paths to select the correct asset and verify the rendered result.
Site restructuring
Move or copy a representative branch and confirm permissions, URLs, descendants and navigation.
Content recovery
Exercise the recycle-bin path and confirm the intended item and descendants are restored or retained.
Daily navigation
Compare card, table and tree views for the roles and content volumes used by the team.
Safer recovery and a more flexible document tree
At the service level, the release adds support for restoring a document or media item without automatically restoring its descendants. That gives developers and package authors a more precise recovery option. Confirm how your backoffice, custom tools or support procedures expose the capability before assuming editors can use it in every workflow.
The document tree also gains card and table views. These views can help when names, icons or hierarchy alone are not enough to scan a large content structure. They are especially worth testing with multisite roots, multilingual content, member areas and editors restricted to particular start nodes.
View choice should not conceal governance problems. If editors struggle because content types have unclear names, folders are inconsistent or permissions expose too much of the tree, fix those structural issues as well. A better view improves navigation; it does not replace a maintainable information architecture.
Important fixes beyond the headline features
The release notes contain fixes that may be more valuable than the visible features for particular sites. Umbraco 17.7 and 18.2 address migration errors from version 13 databases with block editors, preserve the published state of property-less blocks during upgrade, and retain block-level elements nested inside <div> containers in the TipTap rich-text editor.
They also refresh external preview tabs and tokens on repeated preview, re-fetch the current user when authorisation returns after a session timeout, improve cache-instruction broadcasting in load-balanced environments, and filter document and media notifications by the recipient's start-node access. The releases include many other fixes, so a technical owner should review the full notes against the site's architecture.
Do not convert the entire changelog into a generic regression pack. Identify which paths your site actually uses—version 13 migration, custom rich text, load balancing, external preview, multilingual variants, custom extensions or restricted editors—and concentrate evidence there.
A seven-step update plan
Treat the release as a small, owned change with evidence and rollback—not an unattended package bump.
1. Confirm the branch
Record whether each site runs Umbraco 17 or 18, plus its exact CMS, .NET and add-on versions.
2. Map dependencies
List packages, custom backoffice extensions, integrations, deployment steps and hosting dependencies.
3. Back up
Create recoverable database, media, configuration and code snapshots and confirm restore access.
4. Rehearse
Apply the minor update in a representative non-production environment using the real deployment path.
5. Test work
Run editor tasks, publishing, preview, forms, search, redirects, integrations and scheduled jobs.
6. Deploy attended
Use an owned window with logs, health checks and a rollback decision available.
7. Measure and close
Monitor errors and editor feedback, then compare task time and friction against the earlier baseline.
Test the workflows that can affect customers
| Area | Test | Evidence |
|---|---|---|
| Content editing | Create, edit, preview, schedule, publish and roll back representative pages with real editor roles. | Content IDs, roles, timestamps and public URLs. |
| Bulk actions | Publish, unpublish, move or copy a controlled batch and observe progress through completion. | Selected item count, destination, result and error details. |
| Collections | Apply a view, filter, sort and page; edit an item; then return to the collection. | Before-and-after screen state and task time. |
| Media and pickers | Find similar filenames across folders, multi-select assets and verify crops or links. | Selected asset keys and rendered pages. |
| Website journeys | Exercise navigation, search, forms, ecommerce or booking, authentication and key calls to action. | Submission, order, booking or request IDs in downstream systems. |
| Operations | Check deployment health, cache refresh, scheduled work, webhooks, logs and monitoring. | Deployment record, job status and stable error rates. |
For load-balanced sites, include publishing on one instance and reading from another. For multilingual sites, test variants, fallback behaviour, culture-specific search and the correct language in link pickers. For upgraded version 13 sites, include rich-text content and blocks that previously relied on TinyMCE-era markup.
Measure whether the release helps
Choose two or three repeated tasks and record a baseline before the update. Useful measures include time to update ten records from a filtered collection, clicks needed to locate and reuse an asset, number of wrong-media corrections, time spent checking whether a bulk publish finished, and support requests caused by lost list context.
After the release has been in normal use for two weeks, repeat the tasks with the same roles and similar content volumes. A small team does not need a formal usability laboratory: a screen recording, task timer and short editor interview can reveal whether the change removes friction or merely moves it.
Keep performance claims local. The release notes list several technical optimisations, but they do not promise a universal percentage improvement for every website. Measure backoffice start time, key API requests, publishing duration and public-page performance in your own environment before claiming a gain.
Questions to ask your Umbraco partner
- Are we on Umbraco 17 LTS or 18 STS, and what support date drives our roadmap?
- Which CMS, Forms, Deploy, Commerce, Workflow, Engage and third-party package versions are installed?
- Which custom backoffice extensions depend on the collection, picker, tree or rich-text interfaces?
- What is our tested database, media and configuration restore process?
- Which editor roles and start-node restrictions will be included in acceptance testing?
- Do we have version 13 migration risks, custom TipTap markup or property-less blocks to verify?
- How will we test bulk publish, cache propagation and public rendering across every production instance?
- Which editor tasks will we measure before and after the release?
- Who owns monitoring, rollback and post-release support?
Sources checked
- Umbraco CMS 17.7.0 release notes
- Umbraco CMS 18.2.0 release notes
- Umbraco release schedule and versioning
- Umbraco Long-term Support and End-of-Life
- Umbraco documentation: Upgrade your project
- Umbraco 18 release overview
- Umbraco documentation: Maintaining packages
Sources were accessed on 22 September 2026. Check the current release notes, package compatibility and support lifecycle before updating a production site.