Forced experience is about par for the course with RQL.
You may need to move your <!IoRangePreExecute> block marks OUTSIDE of the
render spot. So it looks something like:
<!IoRangePreExecute><reddot:cms>
<htmltext>
<% script code %>
</htmltext>
</reddot:cms><!IoRangePreExecute>
I'm fairly certain I have that working on templates. Although I'd have to go
digging through them to find out for sure.
As for the LoginGUID and SessionKey - well typically RQL which runs at the
Pre-Execute stage doesn't have access to those values at all. So you have
traditionally been stuck with logging in a dummy account.
Most of our RQL runs as either a command line batch job or as AJAX calls
withing SmartEdit (for things like target container assignment).
Chad Killingsworth
Assistant Director of Web & New Media
Missouri State University
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of [email protected]
Sent: Friday, July 09, 2010 2:26 PM
To: RedDot CMS Users
Subject: Re: Outputting values of an Info placeholder from within a render spot
Hi Chad,
Thanks for your input, it is greatly appreciated. A couple of
responses from my (forced) experience with this issue:
---------------
COMMENT: "Your pre-executing section should be entirely contained with
your <htmltext> blocks. You look like you are closing and then
reopening the block which won't work. I've edited your code below -
but haven't tested those edits :-)"
RESPONSE:
When I enclose the pre-executing section in the <htmltext> blocks, the
ASP code does not execute at all. Instead, all of the code (including
the line "<!IoRangePreExecute><%") is copied, wholescale, on to the
published page. Strange ... it seems that <htmltext> overrides even
pre-execute blocks. I am beginning to get the impression that pre-
execute blocks are not valid at all within a content class that is
executed by the Navigation Manager as a Navigation Area. If it were
just a regular content class containing render tags and pre-executing
code, then I believe it would work (it has in the past.)
When the pre-executing section is not enclosed in the <htmltext>
blocks (as in the code above), the code does not result in any output.
Even when I tested it with a single line of ASP code outside of the
<htmltext> block, i.e.:
<!IoRangePreExecute><%
Response.write "Hello world"
%><!/IoRangePreExecute>
nothing happened, and the area where the output should have appeared
was blank.
So, damned if I do and damned if I don't (enclose in <htmltext>
block.)
---------------
COMMENT: "Also, I'm not sure how the nested render spot with the page
guid will work. You may have to create an separate info element just
for that."
RESPONSE:
When the ASP code was wrapped inside the <htmltext> block, the nested
page guid worked fine, but (as noted above) the ASP code never
executed, it was just copied onto the published page.
When the ASP code was not wrapped inside the <htmltext> block (as in
the code above), as mentioned, the ASP did not execute at all, and
blank space appeared where the output should have been.
---------------
COMMENT: "And to top it all off, I've never used info elements which
contained the Session variables for loginguid and sessionkey in pre-
executing blocks with RQL. I'd be interested in hearing how that
works."
RESPONSE: Hmmm ... maybe that's the problem. How do you usually get
the loginguid and sessionkey in such a case?
Michael Klosner
--
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.
--
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.
