Content Staging: Ins, Outs, and Why

Version History Capabilities In DNN

Content Staging is now available for the DotNetNuke CMS. Staging allows Content Editors to modify a site without their changes becoming permanent. In setting a site up this way, Admins of the site will be able to verify and approve any content changes prior to them being published live, allowing time for any necessary corrections.

Getting it Enabled
Contact Foremost Media to see how this recent upgrade can benefit your company, as well as how the implementation process works. We will partner with you to determine the best time to make the transition, as well as make sure all content editors for your site understand the changes.

Using Content Staging
Once Content Staging is enabled across your site, using it is very straightforward. You modify the content of an HTML module just like you used to. The only difference is the addition of a checkbox for Publish near the Update button. The checkbox gives you a little flexibility. In general, you will not want to check this, as it defeats the purpose of Content Staging. However, if you do check the box, you are able to revert back to content changes being published live.

Once you hit Update, the page reloads. It will appear as though your changes are now live. This is only because you are still logged into the site. When you look at the page in another browser where your login is not valid, you will notice your changes are not published.

Approval of changes is simple. An Admin of the site will login and go to the page where the changes are pending. Depending on the version of the CMS you are running, there are different instructions:

- DNN 5: Below the content, there is a green checkmark to Publish Content

- DNN 6: In the "Manage" menu, Publish Content

- DNN 7: Edit the page, hover Edit menu, Publish Content

Contact us at ForemostMedia.com for further information.

Read More