Skip to main content

 Configuration

Configuration manual for PageSeeder

Developer tools

When developer mode is enabled, developers have access to the following essential tools, additional features and information specifically aimed at developers:

The developer options usually require administrator rights on the PageSeeder Server.

  • Template files page – lists all the files used in a specific customization.
  • Document types page – all the document types specific available to the current project are listed. The default ones (inherited) can be viewed and the custom ones can be edited. A new document type can also be created. Project managers can access this option.
  • User Interface – the organization theme and logo can be the changed in the organization-config.xml.

Template files

All the files that define a project customization are listed on this page, using the original hierarchy. Go to the Administration menu > project [Project] > file-template Template > Template files.

The default Template files can be viewed from the project System administration menu, Templates > Default files.

Each file has various actions available through the drop-down on the right hand side:

  • For folders –  main actions are Create a file or folder, Upload and Delete.
  • For documents – they are Download, Edit, History, Rename and Delete. Each document can also be moved by drag-and-drop movements. Clicking the document name opens the document in a Template file panel, where it can be edited (if possible). When editing a document, a previous version is stored and can be accessed using the History button.

The entire project customization can also be exported using the Export button. A ZIP archive containing all the document files is downloaded. The export is not for editing purposes—more for recreating the project on a different server so you don't have to start from scratch, or for testing purposes. This same archive can then be imported by clicking the Import button.

Document configuration

The various document types and all the possible customizations available in the project are listed in a table, on the Document types page.

Each custom configuration file can be created or accessed directly from this table and when edited, they open in a Template file panel on the right.

Bundle view

This fragment was moved above the deprecated Layout tools fragments below but not sure if still relevant, or if note content is still relevant.
Update this fragment, or remove?
Asked Christophe if "Bundle view" is still relevant.
Answer : "they are effectively the group of files associated with each document type, media type, or url type. Actually, it's been more or less replaced by the "Types" page"

From the Document config page and from the Layout Tools, documents can be clicked and then viewed in the Bundle View page. This page lists the different files used by the component (XSLT, CSS, Javascript...).

These files can be created, viewed and modified directly on the Bundle View page.

After modifying an XSLT script, the layout needs to be reloaded by clicking the button Reload PageSeeder Cache in the Developer Tools block visible in the Developer perspective or by adding the following parameter to any PageSeeder URL: ?ps-reload=true

Layout tools (deprecated)

Customizing the PageSeeder UI is now deprecated, instead use Berlioz to create a custom app.

There are two ways to see the layout customizations: the Layout Analyzer and the Layout Tree.

Layout analyzer

This page is useful to ensure that a customization is behaving the expected way. It lists the components (new or overwritten) with their details the same way they are registered in the Layout Manager. If a component is not behaving correctly, a quick look in the Layout Analyzer can show if the customization is correct.

Each available layout can be analyzed using the top menu filter Analyze, including perspectives (such as default.developer). The layout chain is also displayed, this is useful to see the order of inheritance of the components.

The components are listed in three tables underneath. By using the top menu filter Show, they can be restricted to the ones defined in the layout selected only or to all the components (including the inherited ones).

The components listed in red are the ones that overwrite a default component. For each component, the following options are displayed:

  • Layout – the layout that the component is defined in.
  • URL Pattern – the URLs matching the component.
  • Scope – the scope that the component can be accessed in (Server, Project or Group).
  • Style – If a specific style is defined for the component (either CSS or XSLT).

Layout tree

The layout tree also lists the components of the different layout available but as a tree.

For each component, details are available in the tree. The details include the sub components used (for example the blocks and trees used in a specific page), the permission required, the servlets and generators used (with the parameters) and the scripts.

A search field is also provided to locate a specific component. The matching components are displayed in the tree in bold.

Created on , last edited on