[
http://jira.magnolia-cms.com/browse/DOCU-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antti Hietala updated DOCU-266:
-------------------------------
Assignee: Ruth Stocks (was: Antti Hietala)
Security: Public (was: Private)
Description:
The way components are inherited changed in Magnolia CMS 4.5. While the idea is
the same, configuration is done differently. Make the [Inheritable
components|http://documentation.magnolia-cms.com/templates/inheritable-components.html]
article to adhere to the new convention.
Inheritance is now configured in the area definition, see for example Site
Definitions > {{/default/templates/prototype/areas/promos}}.
{code:none}
+ <area name>
+ inheritance
- components = <all|filtered|none>
- enabled = <true|false>
{code}
An area that has an {{inheritance}} content node can inherit its content from
the parent. An {{enabled}} data node under it, when set to {{true}}, enables
inheritance for components inside the area. The {{components}} data node
defines which components are inherited:
* {{all}} means that all the components from the parent area are inherited.
* {{filtered}} means that only components whose {{inheritable}} property is set
to {{true}} are inherited. The property is set with the "Show in subpage"
checkbox.
* {{none}} means that no components are inherited
Validate the article against 4.5. At least the following sections need updating:
* "Footer, metanavigation and section header" section has outdated text and
screenshot of footer area in the prototype. The {{cms.includeTemplate}}
directive is deprecated. An area loops through its components automatically now
so the whole code snippet is irrelevant. The text says the template script
ensures that inherited components are rendered without area bars. The script
doesn't need to do this anymore. If the component is inherited (Show in subpage
checkbox is checked = has {{inheritable}} property when viewed in JCR Browser)
then the component doesn't get a toolbar. Simple as that.
* "Automatic inheritance" section. Procedure is incorrect. Replace with a
procedure for creating the {{inheritance}} configuration under the area
definition and setting {{components}} to {{all}}.
* "Optional inheritance" section. Exactly the same as "Automatic" except add
the Show in subpage control in the component dialog and set {{components}} to
{{filtered}}.
was:http://documentation.magnolia-cms.com/templates/inheritable-components.html
> Updated inheritable components article to 4.5
> ---------------------------------------------
>
> Key: DOCU-266
> URL: http://jira.magnolia-cms.com/browse/DOCU-266
> Project: Documentation
> Issue Type: Task
> Security Level: Public
> Components: content
> Reporter: Antti Hietala
> Assignee: Ruth Stocks
>
> The way components are inherited changed in Magnolia CMS 4.5. While the idea
> is the same, configuration is done differently. Make the [Inheritable
> components|http://documentation.magnolia-cms.com/templates/inheritable-components.html]
> article to adhere to the new convention.
> Inheritance is now configured in the area definition, see for example Site
> Definitions > {{/default/templates/prototype/areas/promos}}.
> {code:none}
> + <area name>
> + inheritance
> - components = <all|filtered|none>
> - enabled = <true|false>
> {code}
> An area that has an {{inheritance}} content node can inherit its content from
> the parent. An {{enabled}} data node under it, when set to {{true}}, enables
> inheritance for components inside the area. The {{components}} data node
> defines which components are inherited:
> * {{all}} means that all the components from the parent area are inherited.
> * {{filtered}} means that only components whose {{inheritable}} property is
> set to {{true}} are inherited. The property is set with the "Show in subpage"
> checkbox.
> * {{none}} means that no components are inherited
> Validate the article against 4.5. At least the following sections need
> updating:
> * "Footer, metanavigation and section header" section has outdated text and
> screenshot of footer area in the prototype. The {{cms.includeTemplate}}
> directive is deprecated. An area loops through its components automatically
> now so the whole code snippet is irrelevant. The text says the template
> script ensures that inherited components are rendered without area bars. The
> script doesn't need to do this anymore. If the component is inherited (Show
> in subpage checkbox is checked = has {{inheritable}} property when viewed in
> JCR Browser) then the component doesn't get a toolbar. Simple as that.
> * "Automatic inheritance" section. Procedure is incorrect. Replace with a
> procedure for creating the {{inheritance}} configuration under the area
> definition and setting {{components}} to {{all}}.
> * "Optional inheritance" section. Exactly the same as "Automatic" except add
> the Show in subpage control in the component dialog and set {{components}} to
> {{filtered}}.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
