You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "James Holmes (JIRA)" <ji...@apache.org> on 2007/08/15 18:33:34 UTC

[jira] Updated: (WW-1832) Template directory config (struts.ui.templateDir) causes all templates to fail completely

     [ https://issues.apache.org/struts/browse/WW-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Holmes updated WW-1832:
-----------------------------

    Affects Version/s: 2.0.10
                       2.0.7
                       2.0.8
                       2.0.9
        Fix Version/s:     (was: 2.0.10)
                       2.0.11

Moving to 2.0.11 in preparation for 2.0.10 release.

> Template directory config (struts.ui.templateDir) causes all templates to fail completely
> -----------------------------------------------------------------------------------------
>
>                 Key: WW-1832
>                 URL: https://issues.apache.org/struts/browse/WW-1832
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Views
>    Affects Versions: 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.0.10
>            Reporter: Brian Pontarelli
>            Priority: Critical
>             Fix For: 2.0.11
>
>
> There are a number of issues regarding themes that need to be addressed. All of these issues stem from the fact that Struts2 allows a property to move the location of the theme overrides from /template to anywhere within the web application. Setting it to something like this causes nothing to work at all.
> struts.ui.templateDir=/WEB-INF/template
> The first issue is that overrides no longer work because this directory is assumed to be the directory for ALL templates including the base template being overridden. All path variables no longer work and the theme no does not pick up templates from its parent.
> The second issue is that some variables are no longer being set, such as the themeProperties.parent. This is obviously due to the directory problem, but effects every template file.
> So, for all intents and purposes, this configuration parameter doesn't work at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.