By Rafael H. Schloming and Pete -Su
</authorblurb>In this document, we'll examine the user interface pages of
the Notes application in more detail, covering two separate aspects
@@ -35,7 +41,7 @@
the site map. We'll repeat this description here, assuming that
you have mounted an instance of Notes at the URL /notes
as we did in the packages-example:
AOLserver receives your request for the URL /notes/somepage
.
This URL is passed to the request processor.
The RP looks up the URL in the site map, and sees that the
-object mounted at that location is an instance of the notes
application.
The RP asks the package manager where in the file system the
+object mounted at that location is an instance of the notes
application.
The RP asks the package manager where in the filesystem the
Notes package lives. In the standard case, this would be
ROOT/packages/notes
.
The RP translates the URL to serve a page relative to the page
root of the application, which is ROOT/packages/notes/www/
. Therefore, the
@@ -78,7 +84,7 @@
set context_bar [ad_context_bar "Edit Note"]
} else {
- permission::require_permission -object_id $note_id -privilege create
+ permission::require_permission -object_id $package_id -privilege create
set context_bar [ad_context_bar "New Note"]
}
@@ -240,8 +246,8 @@
that appears to provide each user in a system with their own
private notes database.
We also saw how to use the templating system's forms API in a simple way, to create forms based pages with minimal duplication -of code.
($Id: subsites.xml,v 1.10 2017/08/07 -23:47:54 gustafn Exp $)
+of code.