0.5experimentalSection Hierarchy
Allows hierarchy view of a section in backend
Clone URLhttps://github.com/jonmifsud/section_hierarchy.git
Add as a submodulegit submodule add https://github.com/jonmifsud/section_hierarchy.git extensions/section_hierarchy --recursive
Compatibility
2.x.x | 2.1.x | 2.2.x | 2.3.x | 2.4.x | 2.5.x | 2.6.x | 2.7.0 | 2.7.1 | 2.7.2 | 2.7.3 | 2.7.4 | 2.7.5 | 2.7.6 | 2.7.7 | 2.7.8 | 2.7.9 | 2.7.10 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
No | No | No | 0.1 | 0.2 | 0.5 | No | No | No | No | No | No | No | No | No | No | No | No. Soon? |
Readme
section-hierarchy
This extension works whowever it is not 100% idiot proof at the moment so you're going to have to edit the config and know the field Id's to get it to work.
Install the Extension
Add this snippet in your config file
SECTION_HIERARCHY
'section_hierarchy' => array( 'pages' => '{ 'title':'74', 'parent':'77' }', ),
#
Replace
pages
with the section name that you would like to use section_hierarchy onReplace the
title
andparent
values with the respective Field ID's. Note that the field names need not match title and parent, but a title refers to the key/first field you'd usually have in the table. It is mainly used to edit for indenting. And parents is used to identify the parent field and set it as a child of a parent section.If you need for more then one section copy the
pages
block and repeat steps 2/3 as many times as needed
Version history
Requires Symphony 2.5
Symphony 2.4 to 2.4.x
Symphony 2.3 to 2.3.x