Search translations

Hierarchy?

Hierarchy root

Field holds a hierarchy

Allowed values for hierarchy:

This is a wikitext formatted hierarchy.

*Enter
**hierarchy
***values
***in
**a
***format
*like
**this

This is the name of the page containing the hierarchy.

This is the name of the property containing the hierarchy.

Error: Hierarchy enumeration field cannot be created for type "$1".

The Hierarchy Root list contains the hierarchy that will be preserved when you save. The Unused Pages list contains pages in category $1 that are not currently in the hierarchy. You may rearrange the Hierarchy Root list by dragging rows up and down as well as changing their indentation. You may add pages from the Unused Pages list to the hierarchy by dragging and dropping them where you want them in the Hierarchy Root list. You may remove pages from the hierarchy by dragging them from the Hierarchy Root list and dropping them anywhere in the Unused Pages list.

This is the category to which pages in the hierarchy must belong.

This hierarchy cannot be edited because both the hierarchy data and the category from which to draw unused pages are empty. Please ensure that at least one of these data sources is populated.

If this parameter is provided, the hierarchy should be rendered collapsed when it is first displayed.

Use this form to import HTML content into your wiki.

If you upload a zip file, the Collection Name field is used to differentiate the collection from a later version. Also all files will be grouped in a category by the same name. For example, let's say you're importing a collection of HTML files output from your software documentation system, you would enter a unique Collection ID like 'FluxCapacitor-v1.1' so that the whole collection is imported into an article hierarchy starting with 'FluxCapacitor-v1.1'. This way 10 different collections can be imported without clobbering each other.

Specifying an existing Collection Name (or parent path) will update existing wiki content.

If you want to import a single file into an existing article hierarchy, simply specify it's 'parent' as the Collection Name.

For example, if importing a new 'advanced_topics.html' that should exist at <code>'FluxCapacitor-v1.1/docs/advanced_topics.html'</code>, the parent would be 'FluxCapacitor-v1.1/docs/'