Just out of interest, is there a particular reason as to why you use a WQO agent to build the "Elsehwere" links on your site?
I assume that each "elsewhere" link is a document? If that is the case why not use an @DBLookup in some computed text which returns a particular column from an "elsewhere view". Obviously you can design the column to contain html in the format you need.
I would imagine this is quicker than performing some loop in the WQO LS to get each document and do something with it to get the html you need. However I have not done any research into timings etc so therefore I may be completely wrong but it was just a thought !
Jake,
Just out of interest, is there a particular reason as to why you use a WQO agent to build the "Elsehwere" links on your site?
I assume that each "elsewhere" link is a document? If that is the case why not use an @DBLookup in some computed text which returns a particular column from an "elsewhere view". Obviously you can design the column to contain html in the format you need.
I would imagine this is quicker than performing some loop in the WQO LS to get each document and do something with it to get the html you need. However I have not done any research into timings etc so therefore I may be completely wrong but it was just a thought !
Cheers
Lee