Hi Jonathan, It is possible. Like Henry said, since the publishing job reports keeps a record of who initiate a publish when, and what files were produced. The simplified version of the automation is, on error, login into reddot via rql using job user account, check publishing report, email user that initiated a publishing with such file. Please keep in mind of publishing with all following pages.
The less automated way, but faster way. On error, notify someone, then someone log into reddot, do a text search for said file name in job reports, email the publisher. -Jian On Feb 28, 4:36 am, jonathan nichols <[email protected]> wrote: > Wow - thanks for the detailed reply. > > We wanted to get Publisher info into pages as we use RedDot to publish > our email newsletters, which then get picked up by our mailing tool > and sent out. If the tool comes across any errors, we'd want it to > notify the publisher (which isn't always the last editor). Sounds like > its not possible though. > > Thanks again > > On Feb 26, 1:31 pm, "Henry Lu a.k.a. Javahand" <[email protected]> > wrote: > > > Jon-- > > > This is a catch 22. A user logs in and her/his login guid binds with a > > project guid and becomes a random session guid. That triggers a job guid > > when publishing is activated. > > > The actual execution of that job is an asynchronous process. Only this > > particular process/thread knows whether the publication is a success or > > failure. However, this thread is executed on the RQL server side and does > > not bear a user session guid which is required to modify a RedDot page -- > > for use case you have contemplated, such as writing the the user who > > published the page into the page itself. > > > So all in all it is impossible to implement your idea. While the user clicks > > the publish button, you can assume the last editor is the publisher and > > record that user in the page as publisher. But publishing is asynchronous so > > you do not know if it will succeed and recording that logged in user as > > publisher may not be accurate. The other side of the equation: the server > > kicked-off thread that executes the publishing would get to know the > > publishing result and knows the job guid and therefore can trace back to the > > user guid, but it does not have a legit user session guid to modify the page > > ... so there you go, a perpetual dilemma. > > > But what is the purpose of having the publisher recorded into the pages? If > > it is just for report purposes, why not write a simple app to crawl the logs > > and tabulate who published what and when. > > > Henry > > > On Mon, Feb 21, 2011 at 4:58 AM, jonathan nichols <[email protected]>wrote: > > > > Is it possible to get the login name of the publisher into a page? > > > > It's not one of the info elements (only author/editor/releaser) so has > > > anyone found another way? > > > > -- > > > 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. > > > -- > > 646-807-8683 -- 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.
