Hi everyone, I would not use Context:CurrentUserId inside any content class templates because it is a rendertag listed in the official navigation manager documentation. Support can refuse support on anything that is undocumented.
HOWEVER, if you use within Custom Rendertag code, well, I think it has to be supported because the OpenText rendertag object do expose that property. Since version 9, sessionkey and loginguid is the same, CurrentUserId is something else, something not the same or related. RQL from custom rendertag...to do or not to do. Well, the custom rendertag documentation explicitly says no because it may cause application deadlocks. Well, same thing was said about RQL and preexecution. In the RQL and preexecution case, action="save" RQL may cause deadlocks, query only ones seems to be ok. Hope it is the same for RQL and custom rendertag. The OpenText US Consultant team is undecided on the best practice regarding custom rendertag. It is a beautiful and powerful thing and we wanted to use it. However, just like it was with preexecution, we later found it to be a something that would make a project slow and nightmare to maintain/hand over to client properly. Hilmar, sir, it seems like you are in the same exploration phase as we are. Please, post back to the forum, here or solutionexchange about your findings. Thank you, -Jian On Thursday, February 28, 2013 1:03:59 AM UTC-5, Richard Hauer (5 Limes) wrote: > > Hi Wolfgang, Hilmar, > > > > The “ultimate list” page – which is getting somewhat out of date now – has > those values in the “Session” object (at the very bottom of the tables near > the bottom of the page). > > > > You might have some luck with: > > > > <%!! Context:CurrentUserId !!%> > > If memory serves the SessionKey and LogonGuid are really just the UserId > Guid in recent versions (>= v9) > > > > As far as I can see there is very little that exposes the Session object, > though many types use it. > > > > A custom render tag to expose these values would be trivial. > > > > HTH > > > > Richard H. > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Wolfgang Roiter > *Sent:* Wednesday, 27 February 2013 7:06 PM > *To:* [email protected] <javascript:> > *Subject:* Re: Getting login information in Custom Render Tag > > > > Hi Hilmar, > > > > unfortunately not. Even the "ultimate list" does not mention any solution > how to retrieve session information: > > http://www.reddotcmsblog.com/reddot-cms-render-tags-the-ultimate-list > > > > But why don't you use the info elements? > > > > Regards, Wolfgang > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected]<javascript:> > . > Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
