On Apr 2, 2007, at 11:47 AM, joshua portway wrote:
As an aside - most of the tags in magnolia retrieve pages and
nodes and properties and store them in a user-specified variable,
whereas the equivalent Magnolia tags generally set the "active
page". Personally, I find the "active page" method quite confusing
and difficult to use, because you need to remember to restore the
active page, and you can't easily nest loops etc. I'm wondering why
the magnolia tags choose to work this way - am I missing something
important in the way that Magnolia works somehow and wasting my
time here ?
I agree and would prefer your method or changing the loadPage tag to
require a body and only affect the active page within that body, e.g.,
<cms:loadPage path="/foo/bar">
<!-- do stuff w/active page set to /foo/bar -->
</cms:loadPage>
Tom
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
