|
Enabling users to create groups |
|
|
|
|
|
Enabling users to create groups |
|
|
|
|
You can enable site users to create new groups by placing the Community -> Group registration web part on your site. You have to set the following properties of the web part:
| • | Template source alias path - alias path of a location where group template source files are stored |
| • | Template target alias path - alias path where files created from group template source files will be loaded when the group is created |
| • | Combine with default culture - if checked, default culture will be used when creating group pages under a culture where the source or target nodes were not found |
| • | Group name label text - text that will be displayed in the form before the field where group name is entered |
| • | Text after successful registration - text displayed when a group is successfully created |
| • | Text after successful registration with approving - text displayed when a group is successfully created, but requires administrator's approval to be published on the web |
| • | Require approval - if checked, the group will have to be approved by a site administrator before it is published on the site |
| • | Redirect to URL - URL where the user will be redirected after creating the group |
| • | Hide form after registration - if checked, the form will be hidden after creating the group |
Group pages templates
Each group has its own section on the website where its content is stored - so called group pages. When adding the Group registration web part to your site, you have to specify the Template source alias path and Template target alias path properties. These two properties are essential when creating the group pages section of each group.
The page specified by the Template source alias path and all its sub-pages are copied to the location specified by the Template target alias path.
To get a better idea of how this works, you can take a look at our sample Community Starter site. On the site, the Group registration web part is configured the following way:
| • | Template source alias path: /Groups/Template |
| • | Template target alias path: /Group-pages |
As you can see in the screenshot below, there is the /Groups/Template page with one sub-page: Pages. When a new group is created, its title page is created under /Group-pages and the Pages page is created under it. As you have probably noticed, the web parts placed on the title page are identical to those placed on the Template page. Web parts on the Pages page are also identical to the source Pages page. Under Pages, all group's documents will be stored.
All Kentico CMS documents can be set to be owned by a group. This can be done by signing into CMS Desk, selecting a document from the content tree, switching to Edit mode and going to Properties -> General -> Owned by group and choosing a group from the drop-down list displayed after clicking the Change button. This property is most useful for group pages and it is mainly informative. It does however influence the editing permissions of Group administrator widget zones. To learn more about widgets, please refer to the Development -> Widgets chapter of this guide.
Please refer to Community Site Guide -> Part 2 -> Creating the Groups section for a step-by-step tutorial on how to create a sample group pages section of a website.
Page url: http://devnet.kentico.com/docs/devguide/index.html?enabling_users_to_create_groups.htm
