[jira] [Comment Edited] (WW-1832) Support template overriding

["Lukasz Lenart (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WW-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057142#comment-14057142 ] 

Lukasz Lenart edited comment on WW-1832 at 7/10/14 6:50 AM:
------------------------------------------------------------

This is partially supported, you can define your own template and put it under {{WebApp/template/simple/a.ftl}} (for example) - templates from web app are resolved first then templates on classpath are scanned


was (Author: lukaszlenart):
This is partially supported, you can define your own template and put it under {{WebApp/template/simple/a.ftl} (for example) - templates from web app are resolved first then templates on classpath are scanned

> Support template overriding
> ---------------------------
>
>                 Key: WW-1832
>                 URL: https://issues.apache.org/jira/browse/WW-1832
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Plugin - Tags
>    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.3.18
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)