From ec3976314de1d9820c0de3ba3c40eeffecf16740 Mon Sep 17 00:00:00 2001
From: xue <>
Date: Tue, 31 Jan 2006 14:13:20 +0000
Subject: Fixed a small issue about page configuration.
---
demos/quickstart/protected/pages/Configurations/PageConfig.page | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
(limited to 'demos/quickstart/protected/pages/Configurations')
diff --git a/demos/quickstart/protected/pages/Configurations/PageConfig.page b/demos/quickstart/protected/pages/Configurations/PageConfig.page
index 606d65a9..bd8a7186 100644
--- a/demos/quickstart/protected/pages/Configurations/PageConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/PageConfig.page
@@ -5,7 +5,7 @@
Page configurations are mainly used by TPageService to modify or append the application configuration. As the name indicates, a page configuration is associated with a directory storing some page files. It is stored as an XML file named config.xml.
-When a user requests a page stored under <BasePath>/dir1/dir2, the TPageService will try to parse and load config.xml files under <BasePath>/dir1 and <BasePath>/dir1/dir2. Paths, modules, and parameters specified in these configuration files will be appended or merged into the existing application configuration.
+When a user requests a page stored under <BasePath>/dir1/dir2, the TPageService will try to parse and load config.xml files under <BasePath>, <BasePath>/dir1 and <BasePath>/dir1/dir2. Paths, modules, and parameters specified in these configuration files will be appended or merged into the existing application configuration. Here <BasePath> is as defined in page service.
The format of a page configuration file is as follows,
--
cgit v1.2.3