This might be messy.. However you might get around the publishing issue if the content was managed within a 'page part' that is connected to a container within a foundation page. The CMS wont publish content within a container unless the foundation page has been released... however if the foundation page is in draft mode, you will have problems enabling other users view the page unless you set up a workflow requiring a release step. Put all of the users into the group who are responsible for releasing the page and they will be able to view the page.
Hope that makes sense! ..As Markus has already mentioned, the CMS is not a wiki - so its not designed to handle this kind of scenario. Regardless of the solution you choose, it will inevitably be a messy process for your editors. Cheers, Kim On Dec 4, 6:38 am, Tiffany <[email protected]> wrote: > Thanks Markus, we don't sell it as a wiki, far from it, but our people > love to collaborate so I am trying to keep from telling them the > system won't do it. I think RedDot is frustrating enough for the end > user. > > Wayne - I actually never used the Display setting before! So this is > very helpful. And I also copied your 3rd paragraph idea and I think > that is just what I needed but couldn't conceptualize before. Thanks! > > On Dec 3, 1:08 am, Wayne Bouwmeester <[email protected]> > wrote: > > > Not in the Main Menu -> Display settings. > > Those dictate how you view the site, as a CMS user. > > > Checking the "Publish unreleased pages" for a project variant is a > > different story. > > That's where you allow the to be published out. > > > If it's just one text field you are collaborating on, you might > > consider creating two text fields. > > Wrap the second (txt_BodyContentCollaboration) which could appear > > below the first, in Smart Edit Only tags, so that you only see the > > content in Smart Edit. > > Make that particular element "Not relevant for workflow" so that you > > don't need to release it. > > Wrap it with a marching ants border, whatever you need to do to > > identify it as the collaboration content. > > > Then collaborate 'til your hearts are content. It won't hit workflow > > and won't go into draft mode because the field is workflow exempt. > > When all users are happy with the content, copy and paste to the field > > not wrapped in smart edit only block markers, submit to workflow, > > release, publish. > > > If you want to actually see the content outside of RedDot, make a > > template variant that publishes to a staging site. > > Include both the regular content and the collaborated content below > > the original content so that executives or marketing folks can see > > both versions. > > > Hope that helps. > > Wayne. > > > On Dec 2, 10:40 am, Tiffany <[email protected]> wrote: > > > > Wayne - won't that publish my unreleased pages? I don't want the pages > > > to be published until they are released. > > > > On Dec 1, 1:17 pm, Wayne Bouwmeester <[email protected]> > > > wrote: > > > > > Have you tried checking the "Unreleased Pages" box in the main menu -> > > > > Use settings window? > > > > You might check "Ignore appearance schedule" as well. > > > > Wayne. > > > > > On Dec 1, 6:55 am, Tiffany <[email protected]> wrote: > > > > > > Markus - We are using that bit, but there is a problem if the page > > > > > hasn't been released, it doesn't appear on the list and the new user > > > > > can't pick it up. But for pages already established this is a great > > > > > solution. > > > > > > On Nov 30, 10:51 pm, Wayne Bouwmeester <[email protected]> > > > > > wrote: > > > > > > > Yes, I guess clicking on the "assign user" link, then the ... > > > > > > button, > > > > > > then clicking search (maybe having typed in some search criteria), > > > > > > then clicking the radio button for the specific user, then clicking > > > > > > OK, then clicking OK to the message telling you that clicking the > > > > > > next > > > > > > OK will change the last editor of the page, then actually clicking > > > > > > the > > > > > > OK to apply the change, then clicking OK because windows wants to > > > > > > close the popup, and then refreshing the page might work. > > > > > > Not sure how much of a shortcut that is to clicking a "take draft > > > > > > ownership" button. > > > > > > I guess it depends on how much your users are willing to put up > > > > > > with. > > > > > > > If you are trying, as an admin, to change ownership to someone else, > > > > > > then yes, you are at the mercy of said interface. > > > > > > If you are trying to take ownership quickly as part of a repetitive > > > > > > business process, I think some investment in click reduction might > > > > > > be > > > > > > in order. > > > > > > > Wayne. > > > > > > > On Nov 30, 6:38 pm, markus giesen <[email protected]> wrote: > > > > > > > > Uhm, you don't necessarily need a plugin to change the user of a > > > > > > > page. > > > > > > > Just use this shortcut:http://bit.ly/75HLuH > > > > > > > > Cheers :) > > > > > > > Markuswww.reddotcmsblog.com > > > > > > > > On 1 Dez., 08:17, Wayne Bouwmeester <[email protected]> > > > > > > > wrote: > > > > > > > > > I wrote a plugin years ago that allowed users to "steal" a page > > > > > > > > in > > > > > > > > draft. > > > > > > > > Basically, I found that if you changed the page via an RQL > > > > > > > > statement > > > > > > > > it became yours, ignoring the current draft user. > > > > > > > > I just wrote some RQL that filled in the current user's name in > > > > > > > > a > > > > > > > > field named stf_CurrentOwner. > > > > > > > > So to steal the page for editing, you just clicked the button, > > > > > > > > it ran > > > > > > > > the plugin, put your name in the field, and now it's in your > > > > > > > > drafts > > > > > > > > instead of your friend's. > > > > > > > > It's kinda making use of RedDot's security by obscurity, but it > > > > > > > > worked > > > > > > > > then. Not sure if it will work in more recent versions, but you > > > > > > > > might > > > > > > > > want to try it. Not much invested if it doesn't work. > > > > > > > > Wayne. > > > > > > > > > On Nov 25, 9:02 am, Tiffany <[email protected]> wrote: > > > > > > > > > > My users would like the CMS to act more like a > > > > > > > > > wiki...basically they > > > > > > > > > want to collaborate on a page, share it between editors, but > > > > > > > > > WITHOUT > > > > > > > > > releasing the page for publication. We have tried a few > > > > > > > > > creative > > > > > > > > > measures to make this happen: (1) allowing them to Assign > > > > > > > > > Last Editor > > > > > > > > > (2) Releasing the page but publishing to a staging area (3) > > > > > > > > > putting > > > > > > > > > fake text in the released version that says "coming soon" > > > > > > > > > until the > > > > > > > > > real text is agreed upon (4) multi leveled workflow that > > > > > > > > > shuffles the > > > > > > > > > page around a max of 3 times before releasing > > > > > > > > > > None of these options are working very well. Does anyone have > > > > > > > > > a system > > > > > > > > > in place where multiple editors can review a *new* page > > > > > > > > > before it gets > > > > > > > > > released for publication? Any ideas are appreciated! -- 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.
