[Bug 6348] New: dynamicdata dot notation not working in xarpages include

http://bugs.xaraya.com/show_bug.cgi?id=6348

           Summary: dynamicdata dot notation not working in xarpages include
           Product: App - Modules
           Version: Weekly Tarball
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: minor
          Priority: P3 - Standard
         Component: xarpages
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6)
Gecko/2009011913 Firefox/3.0.6
Build Identifier: 

If I do this...

<xar:if condition="isset($current_page.dd.author2)">
        <xar:set name="author2_id">$current_page.dd.author2</xar:set>
</xar:if>

...in a xarpages template (page-something.xt), there is no problem.  If I do
the same thing in xarpages/includes/someInclude.xt, it causes an exception: 
Use of undefined constant dd - assumed 'dd'

The following works fine in both the xarpages template and in the include...

<xar:if condition="isset($current_page.dd.author2)">
        <xar:set name="author2_id">$current_page['dd']['author2']</xar:set>
</xar:if>

I don't know if it matters, but author2 is a dropdown list that uses a function
for the validation.

So it looks like in this narrow case -- with a module include file and use of
the dd dot notation inside of xar:set -- an exception is raised.  The
workaround is very easy but it took me a while to figure out the workaround. 
It seems like, for consistency, the dot notation should work in all situations
in blocklayout.

Reproducible: Always


-- 
Configure bugmail: http://bugs.xaraya.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

---- ** IMPORTANT ** READ BELOW ** ----
[Clip Me Start]
--------------------------------------------------------------------------
If you wish, you can reply to this message directly **however**, make sure
to use the "Reply To All" feature of your client **and** ensure that the 
bug specifier is in the subject (ie: [Bug ####]). Also, you _MUST_ have 
you're From or Reply-To address set to the same address you use to log
into your bugzilla account or your reply will not be attached to the bug.
--------------------------------------------------------------------------
[Clip Me End]