From 9bba8d4a18a2aca0a83775e0a815c5a9f359dcc8 Mon Sep 17 00:00:00 2001 From: Aaron Trevena Date: Fri, 3 Aug 2007 14:33:11 +0000 Subject: [PATCH] Fixed links in flox to cookbook (bug 22899) git-svn-id: http://svn.maypole.perl.org/Maypole/trunk@578 48953598-375a-da11-a14b-00016c27c3ee --- lib/Maypole/Manual/Flox.pod | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/Maypole/Manual/Flox.pod b/lib/Maypole/Manual/Flox.pod index df3cff8..5e89777 100644 --- a/lib/Maypole/Manual/Flox.pod +++ b/lib/Maypole/Manual/Flox.pod @@ -20,7 +20,7 @@ university student population. Flox is still in, uh, flux, but it does the essentials. We're going to see how it was put together, and how the techniques shown in the -L can help to +L can help to create a sophisticated web application. Of course, I didn't have this manual available at the time, so it took a bit longer than it should have done... @@ -152,7 +152,7 @@ Very simple, as these things are meant to be. Now let's build on it. The concept of a current user is absolutely critical in a site like Flox; it represents "me", the viewer of the page, as the site explores the connections in my world. We've described the authentication hacks -briefly in the L, +briefly in the L, but now it's time to go into a little more detail about how user handling is done. @@ -195,7 +195,7 @@ The next stage is viewing the user's photo. Assuming we've got the photo stored in the database already (which is a reasonable assumption for the moment since we don't have a way to upload a photo quite yet) then we can use a variation of the "Displaying pictures" hack from the -L: +L Now we use the "Catching errors in a form" recipe from the -L and +L and write our form template: -- 2.39.5