summaryrefslogtreecommitdiff
path: root/demos/blog-tutorial/protected/pages/Day5/ErrorLogging.page
diff options
context:
space:
mode:
authorFabio Bas <ctrlaltca@gmail.com>2015-12-07 15:57:51 +0100
committerFabio Bas <ctrlaltca@gmail.com>2015-12-07 15:57:51 +0100
commit654a9cae43358c7eecf3b522e9876aa7815e2453 (patch)
tree545f2e42fdc6e824b247924adf083ad3fe51e61d /demos/blog-tutorial/protected/pages/Day5/ErrorLogging.page
parente99e35819d53dc48ae4e9a8491528a6b6011469f (diff)
Move urls from pradosoft.com to github's project page; drop unmaintained quickstart tutorial translations
Diffstat (limited to 'demos/blog-tutorial/protected/pages/Day5/ErrorLogging.page')
-rwxr-xr-xdemos/blog-tutorial/protected/pages/Day5/ErrorLogging.page2
1 files changed, 1 insertions, 1 deletions
diff --git a/demos/blog-tutorial/protected/pages/Day5/ErrorLogging.page b/demos/blog-tutorial/protected/pages/Day5/ErrorLogging.page
index 52f7ef54..6239d312 100755
--- a/demos/blog-tutorial/protected/pages/Day5/ErrorLogging.page
+++ b/demos/blog-tutorial/protected/pages/Day5/ErrorLogging.page
@@ -9,7 +9,7 @@ If we try to access the URL <tt>http://hostname/blog/index.php?page=EditPost&id=
<img src="<%~ output2.gif %>" class="output" />
<com:InfoBox>
-An important task in a Web application is <a href="http://www.pradosoft.com/demos/quickstart/?page=Advanced.Error">error handling</a> which is often associated <a href="http://www.pradosoft.com/demos/quickstart/?page=Advanced.Logging">logging</a>. There are two types of errors that may occur in a PRADO application: those caused by developers and those by end-users. The former should be resolved before the application is put into production, while the latter are usually within the initial design scope and should be handled nicely (e.g. log the error and display a special page instructing the end-user what to do next.) PRADO implements a very flexible yet powerful framework for error handling and logging.
+An important task in a Web application is <a href="http://www.pradoframework.net/site/demos/quickstart/?page=Advanced.Error">error handling</a> which is often associated <a href="http://www.pradoframework.net/site/demos/quickstart/?page=Advanced.Logging">logging</a>. There are two types of errors that may occur in a PRADO application: those caused by developers and those by end-users. The former should be resolved before the application is put into production, while the latter are usually within the initial design scope and should be handled nicely (e.g. log the error and display a special page instructing the end-user what to do next.) PRADO implements a very flexible yet powerful framework for error handling and logging.
</com:InfoBox>