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 group name contains abbreviations, acronyms or underscores. The title can include punctuation and spaces to describe the group. It’s not recommended to use hyphens in group titles.
The title is optional and if left empty, the group name is then displayed.
The Name field auto-fills with the group title, but it can be changed.
The “URL” is the fundamental building block of PageSeeder. To avoid inconsistent, ambiguous or non-compliant URLs, groups must be named according to the following conventions:
_
) or tilde (~
).Also, by default, the [project-group] string is part of the group email address which means these additional constraints apply:
-silent
’ or contain a double hyphen ‘--
’ because these two strings are reserved for PageSeeder email switches.When creating groups, the name you use is the short name of the group. We ask for the short name because it’s created within the project.
The full name of the group includes the name of its parent project, [project]-[group]
and is used in URLs and email addresses. The full name of the group cannot exceed
60 characters.
Changing the group title is much less risky than changing the group name and unless people fully understand the consequences, they should NOT change the name.
Renaming a group changes the URLs for content and functionality.
Click the Rename... button to open the dialog, You see warnings:
Enter the new name for your group – required.
By default, all the documents under the group 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 group in different parts of the user interface and in emails. Characters are limited to 250.
These options are configurable in more than one place. Rather than duplicate the documentation, all relevant information is available in the advanced options (group) 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 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)