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.
