Currently, you can only change element attributes like its title, theme and state from -the page configuration UI. The only action you can take from the Manage Includelets -page is to delete the element (which perversely can't be done from the page configuration +the page configuration UI. The only actions you can take from the Manage Includelets +page are to copy the element, or to delete the element (which perversely can't be done from the page configuration page, mostly to keep users from destroying their environment if they're allowed to have personal pagesets).
Below this list is a list of includelets which can be bound to elements and added to
-the pageset being configured. You can add an includelet as a new layout element as many
+the pageset being configured. Unless the includelet is marked "singleton", you can add an
+includelet as a new layout element as many
times as you want. For example, you might want to include an instance of the forums includlet
on each page displayed to the user. To do so, add the includelet as a new layout element
once for each layout page that will be created for the subsite, then add them individually to
Index: openacs-4/packages/layout-managed-subsite/www/doc/pageset-configuration.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/layout-managed-subsite/www/doc/pageset-configuration.adp,v
diff -u -r1.1 -r1.2
--- openacs-4/packages/layout-managed-subsite/www/doc/pageset-configuration.adp 26 Nov 2008 11:10:23 -0000 1.1
+++ openacs-4/packages/layout-managed-subsite/www/doc/pageset-configuration.adp 21 Jan 2010 20:43:49 -0000 1.2
@@ -2,9 +2,25 @@
It's very similar to the configuration tool provided by .LRN's new-portal package, and -should be self-explanatory. Similar restrictions apply, in particular you con't remove a page, - or change its layout if there are any elements placed on it. +should be self-explanatory. Similar restrictions apply, in particular you con't remove a page +that has elements bound to it. +
+However, unlike new-portal, you may change the layout of a page even if it contains elements. +If you change to a layout with fewer columns, elements that were on columns that don't +exist in the new layout are placed on the rightmost column. If you change to a layout with +additional columns, those columns will initially be blank. +
+When you create a new page, you must provide a human-readable page name, which can be localized. +The page will be created with a default URL snippet derived from the human-readable name. +The name is converted to lower case, spaces converted to "-", and non-alphanumeric characters +other than "-" removed. Its theme will be blank (in other words, will inherit the pageset +theme), and the page will initally have two columns. +
+After the page has been created, you can edit the page's URL snippet (the character restrictions +described above will be enforced, and URL snippets must be unique within a given +pageset), theme, and page layout template. Index: openacs-4/packages/layout-manager/www/doc/new-portal-compare.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/layout-manager/www/doc/new-portal-compare.adp,v diff -u -r1.2 -r1.3 --- openacs-4/packages/layout-manager/www/doc/new-portal-compare.adp 26 Nov 2008 11:14:21 -0000 1.2 +++ openacs-4/packages/layout-manager/www/doc/new-portal-compare.adp 21 Jan 2010 20:43:49 -0000 1.3 @@ -20,6 +20,8 @@ making it more difficult to customize the output, the template engine is unable to cache the compiled byte-code generated for dynamic HTML, which impacts efficiency.