From: Aaron Trevena <aaron.trevena@gmail.com>
Date: Mon, 2 Oct 2006 14:23:21 +0000 (+0000)
Subject: fixed typo in factory/edit template
X-Git-Tag: 2.12~52
X-Git-Url: https://git.decadent.org.uk/gitweb/?a=commitdiff_plain;h=e8ebb9e2413d25fe7accc675387dfad270d7367e;p=maypole.git

fixed typo in factory/edit template

git-svn-id: http://svn.maypole.perl.org/Maypole/trunk@522 48953598-375a-da11-a14b-00016c27c3ee
---

diff --git a/Changes b/Changes
index c4cc7db..5009e19 100644
--- a/Changes
+++ b/Changes
@@ -2,6 +2,11 @@ This file documents the revision history for Perl extension Maypole.
 For information about current developments and future releases, see:
     http://maypole.perl.org/?TheRoadmap
 
+2.12  October 2006
+   Fixed some db_colinfo test bugs
+   Fixed typo in edit form template
+   Now uses Class::C3 in all Classes to simplify inheritence
+
 2.11 Mon 31 July 2006
 
 SVN revision 519
diff --git a/Makefile.PL b/Makefile.PL
index 935c677..6d6cdfb 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -31,6 +31,7 @@ WriteMakefile(
         Digest::MD5			 => 0,
 	File::MMagic::XS		 => 0.08,
 	Class::DBI::Plugin::Type	 => 0,
+	Class::C3			 => 0.14,
     },    # e.g., Module::Name => 1.1
     (
         $] >= 5.005
diff --git a/lib/Maypole.pm b/lib/Maypole.pm
index d476b56..ec50419 100644
--- a/lib/Maypole.pm
+++ b/lib/Maypole.pm
@@ -12,7 +12,7 @@ use URI::QueryParam;
 use NEXT;
 use File::MMagic::XS qw(:compat);
 
-our $VERSION = '2.11';
+our $VERSION = '2.12';
 our $mmagic = File::MMagic::XS->new();
 
 # proposed privacy conventions:
diff --git a/lib/Maypole/Manual/Model.pod b/lib/Maypole/Manual/Model.pod
index 112effc..98f54cd 100644
--- a/lib/Maypole/Manual/Model.pod
+++ b/lib/Maypole/Manual/Model.pod
@@ -56,6 +56,29 @@ The second reason why we want our table classes to inherit from
 C<Maypole::Model::CDBI> is because it provides a useful set of 
 default actions. So what's an action, and why are they useful?
 
+
+=head2 Maypole::Model::CDBI::Plain
+
+The 'Plain' maypole Model : C<Maypole::Model::CDBI> allows you
+
+    package Foo;
+    use 'Maypole::Application';
+
+    Foo->config->model("Maypole::Model::CDBI::Plain");
+    Foo->setup([qw/ Foo::SomeTable Foo::Other::Table /]);
+
+    # untaint columns and provide custom actions for each class
+
+    Foo::SomeTable->untaint_columns(email => ['email'], printable => [qw/name description/]);
+
+    Foo::Other::Table->untaint_columns ( ... );
+
+    sub Foo::SomeTable::SomeAction : Exported {
+
+        . . .
+
+    }
+
 =head2 Extending a model class with actions
 
 Maypole operates primarily by turning URLs into method calls on a model
@@ -118,3 +141,5 @@ chapter and our case studies.
 L<Contents|Maypole::Manual>,
 Next L<Maypole View Classes|Maypole::Manual::View>,
 Previous L<Introduction to Maypole|Maypole::Manual::About>
+
+=cut
diff --git a/lib/Maypole/templates/factory/edit b/lib/Maypole/templates/factory/edit
index 4b589ed..3b0aca6 100644
--- a/lib/Maypole/templates/factory/edit
+++ b/lib/Maypole/templates/factory/edit
@@ -18,7 +18,7 @@ form similar to L<addnew> but with the current values filled in.
 
 [% IF object %]
 <div id="title">Edit a [% classmetadata.moniker %]</div>
-<form action="[% base %]/[% item.table %]/do_edit/[% object.id %]" method="post">
+<form action="[% base %]/[% object.table %]/do_edit/[% object.id %]" method="post">
 <fieldset>
 <legend>Edit [% object.name %]</legend>
    [% FOR col = classmetadata.columns;