You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.

Pages Tree View

The Pages Tree View shows the node structure of the pages. It is pageable, filterable and nodes can be dragged and dropped to move elements around.

When hovering over a node context-elements are displayed:

  • Clone Element Button Clones the element at the same hierarchy level
  • Link File Button Opens a link dialog where the node can be linked to a file node. Only visible for certain types (e.g. a, img, link and script)
  • Edit Content Button Lets the user directly edit the content of the element/file
  • Edit Properties Button Opens the “Edit Object Properties” dialog
  • Delete Button Removes the element from the page effectively moving it to the Unused Elements section
  • Access Control and Visibility Button Opens the “Access Control and Visibility” dialog where rights and visibility of this element (and sub-elements) can be set

Pages Tree View

Search results for "Pages Tree View"

Pages Tree View

The Pages Tree View is the main interface for editing Structr pages. It shows a filterable, pageable list of all pages in the database and allows browsing and editing of the underlying node structure. At the root level, a page is represented by the page icon (Page icon) and the name of the page next to it. The name can be changed by clicking on it.

Shared Components

The Shared Components flyout is the place where you can create and manage Shared Components. It is very similar to the Pages Tree View flyout, because it shows a list of elements and the tree structure those elements. In fact, Shared Components are all linked to a single, hidden page which we call the Shadow Document.

Creating a Shared Component

You can create new Shared Components by dragging and dropping an element from the Pages Tree View into the drop area at the top of the Shared Components flyout. When you do that, Structr copies the source element to the Shared Components flyout and moves all its children to the new copy. The source element becomes a so-called “synced node” that relays the rendering process to the Shared Component.