summaryrefslogtreecommitdiffabout
path: root/htdocs/exceptions/preprocess.chtml
authorMichael Krelin <hacker@klever.net>2005-01-30 00:57:53 (UTC)
committer Michael Krelin <hacker@klever.net>2005-01-30 00:57:53 (UTC)
commit71f4cc84c3788c6904ede17cd626a9ca9c349e3b (patch) (unidiff)
treecfe7736ae3416ad314b7451b756e587335c357c7 /htdocs/exceptions/preprocess.chtml
parentacd2a536dd6bb3ef9438482725f77ac9044ae79b (diff)
downloadsitecing-71f4cc84c3788c6904ede17cd626a9ca9c349e3b.zip
sitecing-71f4cc84c3788c6904ede17cd626a9ca9c349e3b.tar.gz
sitecing-71f4cc84c3788c6904ede17cd626a9ca9c349e3b.tar.bz2
initial commit into repository
Diffstat (limited to 'htdocs/exceptions/preprocess.chtml') (more/less context) (ignore whitespace changes)
-rw-r--r--htdocs/exceptions/preprocess.chtml46
1 files changed, 46 insertions, 0 deletions
diff --git a/htdocs/exceptions/preprocess.chtml b/htdocs/exceptions/preprocess.chtml
new file mode 100644
index 0000000..8516139
--- a/dev/null
+++ b/htdocs/exceptions/preprocess.chtml
@@ -0,0 +1,46 @@
1% html(); return; /* vim:set ft=sitecing: */
2%%derive layout = "/ancestry/layout.chtml";
3<%constructor>
4 b_strict = false;
5</%constructor>
6<%codemethod string title() %>
7 return "preprocessor exceptions handling";
8</%codemethod>
9<%method void content() %>
10 <h1>site-C-ing preprocessor exception handling</h1>
11 <p>
12 It was one of those days when you just can't type right and can't think of
13 what you're typing. It is not unusual that, under such circumstances, you end
14 up with a code like <a
15 href="/view/htdocs/exceptions/development/preprocess.chtml" target="insert"
16 title="the link opens in the frame below">this</a> -- by the time you were
17 about to close your <code>&lt;%code&gt;</code> block you were thinking about
18 some constructor in some component elsewhere in the universe.
19 </p>
20 <p>
21 <em>site-C-ing</em> parser will see the inconsistency and throw an exception
22 which will be caught and passed to <a
23 href="/view/htdocs/handlers/exception_dev" target="insert" title="the link
24 opens in the frame below">the handler</a>, specified in <a
25 href="/view/htdocs/exceptions/development/.scrc" target="insert" title="the
26 link opens in the frame below">the configuration file</a>, which will produce
27 some nice, human-readable <a href="/exceptions/development/preprocess"
28 target="insert" title="the link opens in the frame below">output</a>. Well,
29 you may not wish to give out all this information in the production
30 environment, so you just put in your <a
31 href="/view/htdocs/exceptions/production/.scrc" target="insert" title="the
32 link opens in the frame below">configuration file</a> some <a
33 href="/view/htdocs/handlers/exception_prod" target="insert" title="the link
34 opens in the frame below">different handler</a>, which just gives user <a
35 href="/exceptions/production/preprocess" target="insert" title="the link
36 opens in the frame below">a friendly yet lame excuse</a>.
37 </p>
38
39 <div class="insert">
40 <iframe id="insert" name="insert" src="about:blank" width="95%" height="300">
41 <p>I wanted to put an &lt;iframe&gt; here, but your browser does not seem to
42 support it. That is okay, it still will open links somehow.</p>
43 </iframe>
44 </div>
45
46</%method>