Thanks for your reply, you were right.  Once freemarker has control
it's unaware of the parent theme.  Pretty much all controls have
<#include "/${parameters.templateDir}/${parameters.theme}/controlheader.ftl"
/> in their template.  Once I added my own controlheader.ftl it
worked.  My other problem was that I had templates in my application
root instead of /WEB-INF/classes/.  Once I added it there I saw
freemarker errors, telling me it was the theme variable issue.

Thanks,
Nick

On Thu, Jul 3, 2008 at 3:14 AM, Jeromy Evans
<[EMAIL PROTECTED]> wrote:
> Nick Scavelli wrote:
>>
>> Here's what I've done:
>> /WEB-INF/classes/struts.properties:
>> struts.ui.theme=ccast2_0
>> struts.ui.templateDir=templates
>>
>> /templates/ccast2_0/theme.properties
>> parent=css_xhtml
>>
>> Please advise because this is so annoying.
>>
>>
>
> I can't see anything wrong with that.  I do the same thing in 2.1.2 so I'm
> confident it still works as per 2.0.x.
>
> A common problem problem occurs when you implement a template that includes
> a sub-template with ${parameters.theme} in its path. The issue is that
> ${parameters.theme} equals your theme "ccast2_0" but your theme doesn't
> include the referenced template.
> That is,  the S2 template system knows about template hierarchy to find the
> parent template, but freemarker's include tag does not.
>
> This will cause the exception you're seeing but I can't say exactly where
> without see what you've included in your theme.
> The only solution is to bring more templates into your theme from the parent
> and/or remove the ${parameters.theme} references (which may be in the
> parent).
>
> This issue shouldn't normally apply to form-close.ftl, unless (perhaps?) you
> included form.ftl in your theme but not form-close.ftl.
>
> Note: you'll notice many of the parent templates include hardcoded theme
> names in their include statements precisely for this reason.  There is no
> fix without an overhaul of the S2 template system.
>
> Hope that helps,
> Jeromy Evans
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to