• Submitted by dgivens8 on
  • Last updated by dgivens8 on Tue, 11/17/2026 - 17:08

Most of our Drupal sites have Revisions turned on. When you make changes to the page and save them, new revisions are created and preserved in a list. This way you can roll back changes if needed by switching to an older revision. 

When you save a new revision it is automatically published -- there is no 'draft' mode. We often see situations where people unintentionally unpublish a page after getting confused by the revision process.

Additionally, we've seen people create content on the stage versions of their Upsun-hosted site in order to simulate a draft mode, then they ask to migrate it, which is not possible.


Your two options for staging content

To clarify your options, below are the two procedures you can choose from for staging content -- and each of these procedures applies to the creation of new content and revisions to existing content on your site.

1. Default pipeline for creating new pages

The default is to keep drafts unpublished until ready. This is the stock solution for staging a new page. A new revision is still created when you save changes to an unpublished page, and site editors have the ability to publish a revision when ready.

-- OR --

2. Workflow module for complex cases

This is specifically for more complex use cases where several people are editing pages at once. You have ask a web developer to install the Workflow module on your Drupal site.

Here's a video about the module:
https://www.youtube.com/watch?v=HiwPSIFu3Ec

This module enables you to create Workflows and assign them to content types (like Basic Pages).

Workflows are made up of workflow states. Transitions between states can be allowed per role, such as an Editor for a site. For example, a workflow with the states Draft, Review, and Published could be assigned to the Basic Page node type, and only users with a specified role can set the content to the Published state.