Hi Jason, The word "draft" in the HTML (Draft) publishing combination refers to templates, not pages. If you are using template workflow, these combinations will allow you to publish out the page with the draft templates, but the released content.
If the goal however is to publish draft content, then I would do what Wayne recommends, create a seperate Staging project variant that is set to publish unreleased pages. Best, - Eric On Aug 20, 3:23 pm, jljohnstone <[email protected]> wrote: > Here's a good one... > > I have two publishing targets, "production" and "draft" for example. > When I publish files to the "production" target, all files publish as > expected and things work fine on the live web site. If I publish files > to the "draft" target (by selecting HTML(Draft) and XML(Draft) in the > Publish Pages dialog) some files (XML files) don't get published. > > Initially, I thought I had some project variant related settings > incorrect and that was causing this problem. After checking those > settings and republishing, the problem remains. > > As a test, I changed the FTP path in the "production" target to match > the FTP path in the "draft" target, essentially making the production > target publish to the draft web server. After publishing with this > configuration, following the same steps (selecting HTML(Draft) and XML > (Draft)) all files were published properly to the draft web server and > everything worked as expected. > > If both publication targets are identical except for the FTP path, why > would some files be published under one target but not with another? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
