# HG changeset patch
# User paulb
# Date 1214004084 0
# Node ID 8d9c1e94e78b229aa7563d5f98cfa7862795f266
# Parent  a9ae62c24e69272bbc5cc08eff5f32fd20ed0787
[project @ 2008-06-20 23:21:24 by paulb]
Replaced template:id with template:section in the notes.
Updated release notes.

diff -r a9ae62c24e69 -r 8d9c1e94e78b README.txt
--- a/README.txt	Sat May 24 18:26:46 2008 +0000
+++ b/README.txt	Fri Jun 20 23:21:24 2008 +0000
@@ -67,6 +67,8 @@
     the WebResources and PyQtWebResources modules.
   * Added experimental OpenID support; improved the authentication resources
     and mechanisms.
+  * Fixed the LoginResource to work correctly when detecting the protected
+    application's location.
   * NOTE: Need to add persistence for OpenID associations.
   * Added XInclude support in templates (requires libxml2dom 0.4.6 or later).
 
@@ -284,21 +286,21 @@
 Choosing an element-path:
 
 When specifying the "context" of the in-page update, one must imagine which
-element the template fragment should operate within. If the template:id
+element the template fragment should operate within. If the template:section
 attribute marks a particular section, then the element-path should be a path
 to the applicable context element for that section in the complete template
 document. Note that if a template:element attribute appears on the same
-element as the template:id attribute then the element-path should refer to the
-element specified in the template:element attribute.
+element as the template:section attribute then the element-path should refer
+to the element specified in the template:element attribute.
 
-Choosing where to put template:attribute, template:id and id:
+Choosing where to put template:attribute, template:section and id:
 
 When specifying the extent of a template fragment, one must be sure not to put
-the template:id attribute on the same element as a template:attribute
+the template:section attribute on the same element as a template:attribute
 annotation; otherwise, the generated code will be improperly extracted as a
 fragment producing two versions of the element - one for when the specified
 attribute is present, and one for when it is not present. Generally,
-template:id and id can be placed on the same node, however.
+template:section and id can be placed on the same node, however.
 
 Stable element ordering and element-path: