Author: rwatler
Date: Fri Mar 19 00:51:02 2010
New Revision: 925060
URL: http://svn.apache.org/viewvc?rev=925060&view=rev
Log:
JS2-1134: enhancements to support rooted space menus and reserved folder
filtering
Modified:
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
Modified:
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
URL:
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml?rev=925060&r1=925059&r2=925060&view=diff
==============================================================================
---
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
(original)
+++
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
Fri Mar 19 00:51:02 2010
@@ -90,7 +90,7 @@ There are many valid attributes for the
</tr>
<tr>
<td>options</td>
- <td>Specifies root document path for this menu if deep inclusion of
documents and folders is specified by this menu. This attribute may also define
document paths that specify page, folder, or link menu options. Paths specified
in this attribute are <a href="#Portal_Site_Component">Page URIs</a>; these
URIs may or may not directly reflect the folder and page hierarchy. The <a
href="#Portal_Site_Component">Portal Site Component</a> maps these options
paths to PSML folder and page elements. Multiple option paths can be specified
as a comma separated list of paths and/or regular expression patterns. Relative
paths are interpreted as relative to the current page. Special patterns, '~' or
'@', can be used to reference the current page. Elements of the current page
path can be referenced within options using one of the following special
patterns: '@0', '@1'..'@N', or '@$'. The '@0' pattern is replaces with the
whole current path, (trimmed of leading and trailing separators). T
he '@N' pattern is replaced with the Nth, (one based index), path element of
the current path. Finally, the '@$' pattern is replaced with the last element,
(normally a page name), of the current path.</td>
+ <td>Specifies root document path for this menu if deep inclusion of
documents and folders is specified by this menu. This attribute may also define
document paths that specify page, folder, or link menu options. Paths specified
in this attribute are <a href="#Portal_Site_Component">Page URIs</a>; these
URIs may or may not directly reflect the folder and page hierarchy. The <a
href="#Portal_Site_Component">Portal Site Component</a> maps these options
paths to PSML folder and page elements. Multiple option paths can be specified
as a comma separated list of paths and/or regular expression patterns. Relative
paths are interpreted as relative to the current page. Special patterns, '~' or
'@', can be used to reference the current page. Elements of the current page
path can be referenced within options using one of the following special
patterns: '@0', '@1'..'@N', or '@$'. The '@0' pattern is replaces with the
whole current path, (trimmed of leading and trailing separators). T
he '@N' pattern is replaced with the Nth, (one based index), path element of
the current path. Finally, the '@$' pattern is replaced with the last element,
(normally a page name), of the current path. Finally, the special pattern '+'
can be used to reference the trimmed path of folder that the menu is defined
within, (if the menu is defined on a page or template, the parent folder path
is used). This pattern can be used to "pin" a menu to a specific folder.</td>
</tr>
<tr>
<td>depth</td>
@@ -519,7 +519,7 @@ Notes:
<ul>
<li>Menu options attempting to use invalid Page URIs are ignored. Invalid
URIs include those containing reserved folders such as '_user', '_role', etc.
or other physical paths specific to the the Page Manager implementation.</li>
<li>Security constrained pages or folders cannot be referenced by requests
and will not appear in menus.</li>
- <li>Hidden pages and/or folders can be requested, but are not visible in
menus. There is one exception for pages: a hidden page is considered visible if
it is the request page.</li>
+ <li>Hidden pages, (or hidden and reserved folders), can be requested, but
are not visible in menus. There is one exception for pages: a hidden page is
considered visible if it is the request page.</li>
</ul>
</p>
</section>
