Publishing Draft pages

77 views
Skip to first unread message

Daniel Petroff

unread,
Dec 20, 2012, 5:48:40 AM12/20/12
to reddot-c...@googlegroups.com
Hi All

In our new project we need to be able to publish unreleased/draft pages to a different location from the live pages. I wanted to use the HTML/English (Draft) publishing combination to assign the new publication target to it and thought that would be the very easy solution. The rest of the publication structure is the same as live.
Unfortunately it doesn't seem to work as expected. When I make a change to a page and publish the page (ticking both HTML/English and HTML/English(Draft)) both publishing reports say page published but neither location is updated (this is unexpected as it should publish the draft of the page to the draft variant - or at least that's what I am expecting). When I release the page and republish again - both are updated (this is expected).

So, anybody have any insight on this? Am I just misinterpreting the use of HTML/English (Draft)? Is this not the way to do that?

I tried assigning the deftault publishing targets in project variant settings, I also tried setting the tick box for "Publish Unreleased Pages".

Is the problem in the state of the page? At the moment I have no workflow so do I need to create one and Submit the page to workflow so it is in "Unreleased" state and not draft?
What is the point of the (Draft) variant?

Sorry about the huge number of questions but I hope they are related so will be easy ti answer :)

Thanks!
Daniel

Gavin Cope

unread,
Dec 20, 2012, 6:12:33 AM12/20/12
to RedDot CMS Users
The "<VARIANT> (Draft)" built-in Variant that exists is for publishing out Draft versions of Content Classes for testing.

To publish unreleased pages, you would need to create a new Variant and tick the box to "publish unreleased pages".

Something to also keep in mind is the automatic clean-up of deleted pages does not function for "Draft" variants.

Cheers,

Gavin


Daniel

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/iZtc8L-NI-QJ.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

Daniel Petroff

unread,
Dec 20, 2012, 6:25:27 AM12/20/12
to reddot-c...@googlegroups.com, RedDot CMS Users
Ah, thanks! That makes sense.

Daniel

Sent from my iPad

Marky T

unread,
Jan 31, 2013, 6:26:55 AM1/31/13
to reddot-c...@googlegroups.com
Sorry just hijacking the thread :). Is it correct that the 'publish unreleased pages' checkbox only publishes pages that are in Workflow and NOT actual draft content that hasn't been submitted at all yet?
 
We want our admins to be able to publish unreleased content to our QA system but they are also the final workflow step so if they click 'Submit to Workflow' it just releases the pages.

Gavin Cope

unread,
Jan 31, 2013, 6:32:10 AM1/31/13
to RedDot CMS Users
That's correct, a page needs to have entered workflow to publish using that option. Prior to that, it is considered exactly what the name suggests, an author only draft that can't be published.

Cheers,

Gavin


On 31 January 2013 21:26, Marky T <mark....@arm.com> wrote:
Sorry just hijacking the thread :). Is it correct that the 'publish unreleased pages' checkbox only publishes pages that are in Workflow and NOT actual draft content that hasn't been submitted at all yet?
 
We want our admins to be able to publish unreleased content to our QA system but they are also the final workflow step so if they click 'Submit to Workflow' it just releases the pages.

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-use...@googlegroups.com.

To post to this group, send email to reddot-c...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages