You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2013/03/26 23:51:15 UTC
[jira] [Updated] (WOOKIE-290) Widget templates not allowing content
to be overwritten properly
[ https://issues.apache.org/jira/browse/WOOKIE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler updated WOOKIE-290:
--------------------------------
Fix Version/s: 0.14.0
> Widget templates not allowing content to be overwritten properly
> ----------------------------------------------------------------
>
> Key: WOOKIE-290
> URL: https://issues.apache.org/jira/browse/WOOKIE-290
> Project: Wookie
> Issue Type: Bug
> Components: Template
> Affects Versions: 0.9.2
> Reporter: Ross Gardler
> Priority: Minor
> Fix For: 0.14.0
>
>
> When there a widget template depends on another there is a break in the ability to override content. Consider, for example, the login widget which extends the base widget. Content provided by the base template or the widget definition is correctly used but content from the login template is not.
> This is because the base template defines the token (e.g. content.primary) in its template_build.xml from either the base template or the widget definitions. Once defined the token is not overwritten in the login template.
> We need to change the way properties are defined. The correct process (in this example) would be:
> - copy all content files from base template to build folder
> - copy all files from login template (overwriting any that already exist) to build folder
> - copy all files from widget definition (overwriting any that already exist) to build folder
> - define the properties by loading executing each of the appropriate targets in each template_build.xml
> - build the widget using the content files in the build folder
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira