tag:help-archives.hannonhill.com,2010-02-09:/discussions/velocity-formats/3747-velocityxpath-for-calling-block-content-and-calling-page-pathCascade CMS: Discussion 2018-10-18T20:36:51Ztag:help-archives.hannonhill.com,2010-02-09:Comment/268404292013-05-14T18:37:47Z2013-05-14T18:37:47ZVelocity/xpath for calling block content and calling page path<div><p>Hi Craig,</p>
<p>Currently, the only way you would be able to access both the
XHTML Block contents AND the Calling Page content would be to use a
Block Chooser within your Data Definition, like you had
previously.</p>
<p>The only other way I can think of is to attach a Folder Index
Block that indexes your XHTML Block to your region and also include
the Calling Page content. This would give you access to both;
however, isn't much of a difference from the Block Chooser
(probably more complicated as well).</p>
<p>I did find a <a href=
"http://ideas.hannonhill.com/forums/52559-cascade-ideas/suggestions/3471585-automatically-include-calling-page-information-for">
related suggestion</a> that would include the contents of the
Calling Page automatically within a Velocity Format.</p>
<p>Please Feel free to vote up and/or comment on the suggestion, or
create one if you have any additional ideas. Let me know if you
need access to the Idea Exchange and I'll send over an
invitation.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/268404292013-05-14T19:11:49Z2013-05-14T19:11:49ZVelocity/xpath for calling block content and calling page path<div><p>Thanks for the quick response, Ryan! I'll experiment with your
Folder Index Block idea to see if that will work for us. In the
meantime, I've voted up the suggestion in your Ideas Community.</p>
<p>Much appreciated!</p></div>craig.haisstag:help-archives.hannonhill.com,2010-02-09:Comment/268404292013-05-14T20:06:48Z2013-05-14T20:06:48ZVelocity/xpath for calling block content and calling page path<div><p>Is there any way to populate a block chooser with the value
chosen from another block chooser? If so, I could use block
choosers in both the inline region and the data definition. The
inline region could be used to track block subscribers, and the
chooser in the data definition could be used for pulling content
from that same block as well as page path into the same velocity
script. If one of them could be auto populated, users creating
pages would only have to make a selection in one of them.</p>
<p>Just thought I'd ask. :o)</p></div>craig.haisstag:help-archives.hannonhill.com,2010-02-09:Comment/268404292013-05-15T12:10:03Z2013-05-15T12:10:03ZVelocity/xpath for calling block content and calling page path<div><p>Hi Craig,</p>
<p>Unfortunately, conditional logic similar to what you mentioned
is not currently available. There is a <a href=
"http://ideas.hannonhill.com/forums/52559-cascade-ideas/suggestions/1423939-add-branch-logic-to-data-definitions-example-rad">
related suggestion</a> on the Idea Exchange for a similar feature.
Please feel free to vote up and/or comment if you would like to see
this feature implemented in a future release.</p>
<p>Regarding the subscribers, I believe there has been discussion
on reworking what constitutes a subscriber. For example, a Page
will become a subscriber when using a Block Chooser.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/268404292013-05-15T19:01:17Z2013-05-15T19:01:17ZVelocity/xpath for calling block content and calling page path<div><p>Thanks so much, Ryan!</p></div>craig.haiss