[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ondřej Chytil resolved MGNLSTK-671.
-----------------------------------

    Fix Version/s: 1.3.x
       Resolution: Fixed

> Singleton Template Definitiona (feature pages): Contain relative include of 
> mainArea.ftl which doesn't work if using a custom main.ftl
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MGNLSTK-671
>                 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-671
>             Project: Magnolia Standard Templating Kit
>          Issue Type: Bug
>          Components: templates
>    Affects Versions: 1.3.4
>            Reporter: Christian Ringele
>            Assignee: Ondřej Chytil
>             Fix For: 1.3.x
>
>         Attachments: Screen shot 2010-08-02 at 12.18.48 PM.png
>
>
> Relative includes of sub templates/sub snippets don't work, if you use a 
> main.ftl located in a different location/module.
> The relative include is the executed on the new location (relative to the new 
> main.ftl).
> We had the same problem with all Section templates and removed the relative 
> pathes from the Section templates.
> The the singleton paragraph templates still contain these relative includes, 
> see print screen.
> Best would be to check all template definitions (and all ftl's for include of 
> macros) if there are still any relative includes left.
> All includes, no matter where, should be absolute paths.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to