From 269c9a0010c2495db961c185e83fd52b33b04d73 Mon Sep 17 00:00:00 2001
From: xue <>
Date: Tue, 11 Sep 2007 02:09:27 +0000
Subject: Fixed #692, #700.
---
demos/quickstart/protected/pages/Advanced/Auth.page | 8 ++++++++
demos/quickstart/protected/pages/Configurations/PageConfig.page | 5 +++++
demos/quickstart/protected/pages/GettingStarted/NewFeatures.page | 3 ++-
3 files changed, 15 insertions(+), 1 deletion(-)
(limited to 'demos/quickstart')
diff --git a/demos/quickstart/protected/pages/Advanced/Auth.page b/demos/quickstart/protected/pages/Advanced/Auth.page
index a306c2ae..1c89e07d 100644
--- a/demos/quickstart/protected/pages/Advanced/Auth.page
+++ b/demos/quickstart/protected/pages/Advanced/Auth.page
@@ -74,6 +74,14 @@ When a page request is being processed, a list of authorization rules may be ava
In the above example, anonymous users will be denied from posting to PageID1 and PageID2, while User1 and User2 and all users of role Role1 can access the two pages (in both get and post methods).
+
+
+Since version 3.1.1, the pages attribute in the authorization rules can take relative page paths with wildcard '*'. For example, pages="admin.Home" refers to the Home page under the admin directory, and pages="admin.*" would refer to all pages under the admin directory and subdirectories.
+
+
+
+Also introduced in version 3.1.1 are IP rules. They are specified by a new attribute ip in authorization rules. The IP rules are used to determine if an authorization rule aplies to an end-user according to his IP address. One can list a few IPs together, separated by comma ','. Wildcard '*' can be used in the rules. For example, ip="192.168.0.2, 192.168.1.*" means the rule applies to users whose IP address is 192.168.0.2 or 192.168.1.*. The latter matches any host in the subnet 192.168.1.
+
Using TUserManager
diff --git a/demos/quickstart/protected/pages/Configurations/PageConfig.page b/demos/quickstart/protected/pages/Configurations/PageConfig.page
index e41019af..c52164b6 100644
--- a/demos/quickstart/protected/pages/Configurations/PageConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/PageConfig.page
@@ -39,4 +39,9 @@ The <paths>, <modules>, <parameters>DTD and XSD files.
+
+
+Since version 3.1.1, the id attribute in the <page> element can be a relative page path pointing to a page in the subdirectory of the directory containing the page configuration. For example, id="admin.Home" refers to the Home page under the admin directory. This enhancement allows developers to centralize their page configurations (e.g. put all page initializations in the aplication configuration or the root page configuration.)
+
+
$Id$
\ No newline at end of file
diff --git a/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page b/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page
index be754e65..e3e5c0e4 100644
--- a/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page
+++ b/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page
@@ -13,7 +13,8 @@ This page summarizes the main new features that are introduced in each PRADO rel
Added a new control TCaptcha that displays a CAPTCHA to keep spammers from signing up for certain accounts online. A related validator TCaptchaValidator is also implemented.
Added a new control TSlider that displays a slider which can be used for numeric input.
Added Oracle DB support to Active Record.
-Added support of TDataGrid to allow grouping consecutive cells with the same content.
+Added support to TDataGrid to allow grouping consecutive cells with the same content.
+Added support to allow configuring page properties and authorization rules using relative page paths in application and page configurations. Added support to allow authorization based on remote host address.
Version 3.1.0
--
cgit v1.2.3