[
https://issues.apache.org/jira/browse/WW-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914127#comment-17914127
]
cococo42 commented on WW-5516:
------------------------------
According to this:
[https://struts.apache.org/getting-started/themes]
{quote}You can specify the theme on a per Struts 2 tag basis or you can use one
of the following methods to specify what theme Struts 2 should use:
* The {{theme}} attribute on the specific tag
* The {{theme}} attribute on a tag’s surrounding {{form}} tag
* The page-scoped attribute named {{theme}}
* The request-scoped attribute named {{theme}}
* *+The session-scoped attribute named {{theme}}+*
* The application-scoped attribute named {{theme}}
* The {{struts.ui.theme}} constant in {{struts.xml}} (defaults to
{{{}xhtml{}}}){quote}
In Struts2 version 2.5.33, we included a {{theme}} attribute in session, which
was respected in the pages (allowing the theme used to be dynamic). After
migrating to version 6.4.0, this stopped working, and I had to explicitly
include the {{theme}} attribute in the {{s:form}} tags, referencing the session
value.
> Session theme problems after struts2 migration to 6.4.0
> -------------------------------------------------------
>
> Key: WW-5516
> URL: https://issues.apache.org/jira/browse/WW-5516
> Project: Struts 2
> Issue Type: Bug
> Affects Versions: 6.4.0, 6.6.0, 6.6.1, 6.7.0
> Reporter: cococo42
> Priority: Minor
>
> When migrating an application from version 2.5.33 to version 6.4.0 (due to
> the S2-067 bug), session themes in Freemarker templates stopped being
> applied. It became necessary to add a {{theme}} attribute in the {{s:form}}
> tags that would retrieve the value from the session.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
