You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Vijayakannan (JIRA)" <ji...@apache.org> on 2014/07/10 03:57:05 UTC

[jira] [Commented] (WW-1832) Support template overriding

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

Vijayakannan commented on WW-1832:
----------------------------------

is there any plan to fix this issue? i don't see any update after 2008.I faced similar problem as well. Refer WW-3764

> 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: 3.0
>
>
> 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)