Craig, Thanks for the input. I think I should better explain myself. I can do so now because of all of the attempts I've made at this. I'm a home schooled student in RedDot and I'm the teacher too. The more I dig, the more I understand. So I don't think I've been explaining my situation as well as a more experienced person could.
I have a tempale I call Banners. Banners contains very basic elements, e.g. an image element and an anchor element, etc. Most of my Banners are used throughout the site. Normal behaviour I think. When I perform the query via RQL I receive an xml file that contains the page information for every page the banner is linked from. Most cases result in a very large xml file. Again, expected. When I comb through the xml file, I want to extract the page information relevent to the page I have open. In one case I have a page named Newsroom Page open with a Live Chat banner linked. The Newsroom Page guid is 4585...C479 and the banner has a guid of 1AA5...2654. (This particular banner is linked to well over 100 pages). When I visually parse the xml file I see the <LINK.. /> that contains a reference to the Newsroom Page. This is the one I want for this page. So, what I need to do is to have already identified the Newsroom Page guid (this is what I have called the Parent Page GUID) before I loop through the xml file. I see that the RedDot onclick for the banner contains a reference to the Parent Page GUID, pageGUID=458...C479 I hope this helps. On Thu, Jul 1, 2010 at 5:01 AM, Craig Castledine <[email protected] > wrote: > So you want the GUID of the page that contains the element? You can use > the "pageguid" attribute returned from your query: > > Change > getParentPageGUID = RDxmlNodeList(0).getAttribute("guid") > to > getParentPageGUID = RDxmlNodeList(0).getAttribute("pageguid") > > Hope that helps. > > Craig. > > > > On 1 July 2010 00:08, Bill Rishsew <[email protected]> wrote: > >> With closer examination the function to get the Parent Page GUID isn't >> return the Parent Page GUID. >> The value being returned is the same. I need it to return the GUID of the >> Page it is contained in. >> Thoughts. >> >> Function getParentPageGUID(strSessionKey, strLoginGUID, strPageGUID) >> XMLString = "" >> XMLString = XMLString & "<IODATA loginguid='" & strLoginGUID & "' >> sessionkey='" & strSessionKey & "' format='0'>" >> XMLString = XMLString & " <ELT action='load' guid='" & strPageGUID & >> "' />" >> >> XMLString = XMLString & "</IODATA>" >> xmlFile = xmlPage(XMLString) >> Set xmlDoc = Server.CreateObject("Msxml2.DOMDocument.4.0") >> xmlDoc.loadXML(xmlFile) >> Set RDxmlNodeList = xmlDoc.getElementsByTagName("ELT") >> Response.Write("<!-- " & xmlFile & " -->") & vbCrLf >> getParentPageGUID = RDxmlNodeList(0).getAttribute("guid") >> End Function >> On Wed, Jun 30, 2010 at 10:16 AM, Bill Rishsew <[email protected] >> > wrote: >> >>> The way I set it up is how you outlined below. Just slows the page load a >>> bit is all. Hoped to compact it a bit. Maybe I'll sit and stare a bit. >>> Considering the number of clicks it is saving the content editors, it's >>> worth it. Now they can see when the all of the links expire on that page in >>> a glance. >>> On Wed, Jun 30, 2010 at 9:43 AM, Wayne Bouwmeester < >>> [email protected]> wrote: >>> >>>> You mean all the parent page guids for all the links? >>>> I don't think so - too complicated since you'd need to specify which >>>> link, and RQL isn't that complex. >>>> >>>> At best you might be able to add multiple ELT nodes in one call, and >>>> run it at the end of all your PAGE calls. Try it and see what you get. >>>> I didn't see anything in the documentation, but I know you can save >>>> multiple elements in a single call back to RD, so it might work. >>>> >>>> >>>> On Jun 30, 10:34 am, Bill Rishsew <[email protected]> wrote: >>>> > Got it, thanks. Works well. >>>> > Is there a way to get the information in a single XML. >>>> > >>>> > I'm using >>>> > >>>> > <IODATA sessionkey=[!key!] loginguid=[!guid_login!]'> >>>> > <PAGE guid=[!guid_element!]'> >>>> > <LINKSFROM action='load' /> >>>> > </PAGE> >>>> > </IODATA> >>>> > >>>> > and >>>> > >>>> > <IODATA loginguid="[!guid_login!]" sessionkey="[!key!]" format="0"> >>>> > <ELT action="load" guid="[!guid_element!]" /> >>>> > </IODATA> >>>> >>>> -- >>>> 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]<reddot-cms-users%[email protected]> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>> >>>> >>> >>> >>> -- >>> Work Hard! Play Harder!! >>> >>> >> >> >> -- >> Work Hard! Play Harder!! >> >> -- >> 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]<reddot-cms-users%[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]<reddot-cms-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/reddot-cms-users?hl=en. > -- Work Hard! Play Harder!! -- 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.
