Only administrators can configure projects.
Click the Save button at the bottom of the page to save any changes you have made.
The title is a user-friendly name to display in the user interface. This is useful if the project name contains abbreviations, acronyms or underscores. The title can include punctuation and spaces to describe the project. It’s not recommended to use hyphens in project titles.
The title is optional, and if left empty, the project name is then displayed.
The Name field auto-fills with the project title, but it can be changed.
The name of the project is required, must be a unique filename system-wide and is used as a prefix for all subprojects and groups under that project. It is also used as the project template name.
The “URL” is the fundamental building block of PageSeeder. Because the project and group names express context for the URLs that represent content and functionality, it is important the names do not conflict with existing system URLs or the URL syntax itself
To avoid inconsistent, ambiguous or non-compliant URLs, projects must be named according to the following conventions:
_
or tilde ~
.admin
, default
, member
, public
.Because the full name of a project includes the name of its parent project, [project]-[subproject]
, and is used in URLs and email addresses, it’s a good idea to keep project names
short. We recommend that the full name of a project not exceed 40 characters.
Changing the project title is much less risky than changing the project name. Unless people fully understand the consequences, they should NOT change the name.
Renaming a project changes the URLs for content and functionality.
Click the Rename... button to open the dialog, You see warnings:
Enter the new name for your project – required.
By default, all the groups under the project are re-indexed – clear the checkbox if you don’t want to re-index.
A short description is required and is often displayed as a subtitle of the project in the user interface and in emails.
These options are configurable in more than one place. Rather than duplicate the documentation, all relevant information is available in the advanced options (project) document.
These properties are configurable in more than one place. Where in the system the changes are made, determines the scope of the update. For example, a change at the project level affects the subprojects and groups it contains. A change at group level only affects that group. Rather than duplicate the documentation, all relevant information is available in the group properties form document.
Administration menu >
The PageSeeder user manual
© Allette Systems (Australia)