Does anyone else see the idiocy of this? Why can't OpenText have an interim stage where pages can be released but not set to publish until it gets into workflow?
We have different problems in our environment where multiple authors share content responsibility on the same pages. It's a huge headache to force drafts to be released in order to pass the work onto the next stage. And with enough headaches publishing each project into its own space, I couldn't imagine publishing to a secondary project. Also, what if someone chooses the wrong project? As for the boss who can't be bothered to log in, that problem is solved by active directory. Visit the CMS page, get logged in. Then open the link to the preview window, specifying the page GUID. Only works if you have access to those pages, but if they're all released anyway... Thanks for listening, -Tony On 2012-02-15, at 5:36 PM, Markus Giesen <[email protected]> wrote: > The ideal solution for this is a second project variant. > Call it Preview or Staging and use the normal HTML templates for it. > Set it to "publish pages saved as draft" for this variant. > Then create a publishing target ideally on a password secured or > internal server. > > That's it. Hope that helps? > > On Feb 16, 5:08 am, "Ray Evans" <[email protected]> wrote: >> Struggled with this for a while as well... using the draft state and >> publishing it to a different publishing target seemed to create another >> set of problems. >> >> In the end, I created a development publication package, and then >> created a Development Area node in the site tree where editors can >> create new content. All content in this node uses the development >> publication package, and publishes to an internal site where new content >> can be reviewed. >> >> When they're ready to go live with a page - or set of pages, I >> disconnect them from the development area, and then reconnect them to >> the appropriate section within our live site tree. >> >> If there's a set of pages (a page with a number of child pages), I do >> have to remember to update the publication package - when disconnecting, >> the development area publication package remains assigned to the child >> pages list. >> >> Cheers, >> >> Ray >> >> From: [email protected] >> [mailto:[email protected]] On Behalf Of >> [email protected] >> Sent: Wednesday, February 15, 2012 10:36 AM >> To: [email protected] >> Subject: Re: Has anyone found a good way to show draft previews to >> non-cms users? >> >> Have you tried a big stick? ;) >> >> If the boss just needs to see it in situ, you can always set up a >> separate project variant with it's own publication target. This will let >> you publish out draft content somewhere that people can review it. >> >> Paul >> >> On 15 Feb 2012, at 15:00, Dmitry Terner wrote: >> >> We get asked this by CMS users all the time and so far I have not had a >> good answer for them. The story goes "I have a boss who cannot be >> bothered to log in and review something but I need to show them the >> progress before submitting the changes. Also they have no imagination so >> they need to see it in situ" I'm paraphrasing .... slightly. >> >> So does anyone know of a good way to tackle this? >> >> Thanks, >> >> - Dmitry >> >> -- >> You received this message because you are subscribed to the Google >> Groups "RedDot CMS Users" group. >> To view this discussion on the web >> visithttps://groups.google.com/d/msg/reddot-cms-users/-/0_UhG4szsfwJ. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group >> athttp://groups.google.com/group/reddot-cms-users?hl=en. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "RedDot CMS Users" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group >> athttp://groups.google.com/group/reddot-cms-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/reddot-cms-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
