Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml,v
diff -u -r1.10 -r1.11
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml 17 Jul 2006 05:38:37 -0000 1.10
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml 27 Oct 2014 16:39:30 -0000 1.11
@@ -94,7 +94,7 @@
} -query {
}
-set user_id [ad_verify_and_get_user_id]
+set user_id [ad_conn user_id]
db_1row user_name {
select first_names || ' ' || last_name as user_name
@@ -187,33 +187,10 @@
Master templates allow you do centralize display code that is used
throughout an application in a single file. In this case, we intend to
have a master template that does the standard page headers and footers
-for us - create the master.adp file, which looks like
-this:
+for us
-
-
-
-
-<%= [ad_header $title] %>
-<h2>@title@</h2>
-<%= [eval ad_context_bar $context_bar] %>
-<hr>
-<slave>
-<br clear="all">
-<%= [ad_footer] %>
-
-
-
-
-The main subtlety in this code is the inline Tcl code for running
-procs to build the header, footer, context bar, etc. Also, note the
-property substitutions that happen here, the values of which are set
-up in the <property> tags in the slave page.
-
-
-
After putting all these files into
ROOT/packages/notes/www, you should be able to go to
/notes/ URL for your server and see the input form.