I would appreciate very much if you can help to answer how to process multiple row entries on a single form i.e. the form you provided in you code has one row. If we havd one form that has 10 rows how will we process these entries to add it to the database? e.g.
James Morrison Undiscovered
Asfaw Maru Out of Africa
Joan Smith On The Road

I'm tempted to include IIS support, but without using ISAPI_Rewrite, I
found that I had to create a new router class to handle routing of GET
parameters.

My code is here:

If I get some time, I'll write up how I got IIS support working. Will be
interesting to compare with your solution.

Ow, and at page 11: "$this->actionTemplate" should be "$view->actionTemplate".

The rest is Great!

Thanks, Antonis.

Warning: Zend_View::include(./application/views\) [function.include.html]: failed to open stream: Permission denied in G:\Apache2\htdocs\zf-tutorial\library\Zend\View.php on line 46

Warning: Zend_View::include() [function.include.html]: Failed opening './application/views\' for inclusion (include_path='.;./library/;./application/models') in G:\Apache2\htdocs\zf-tutorial\library\Zend\View.php on line 46

I didn't know about the .htaccess thing in cgi.

Regarding registering post and get in the bootstrap, I did that because, in my "real" application, my current router looks up stuff in get as it doesn't use rewriting at all. Thus, I needed to retrieve the $_GET in both the router and the controller action. Seemed logical to do it right at the beginning.

It also has a "best practice" benefit in that you can't "cheat" and use $_GET['myvar'] anywhere in your application, as $_GET is null before the dispatcher is called.

I'll try and update the tutorial with the feedback I've received by the end of the week.

Regards,

Rob…

A few small things I'd like to mention:

Your php_flag .htaccess settings…

zf-tutorial/.htaccess
RewriteEngine on
RewriteRule .* index.php

php_flag magic_quotes_gpc off
php_flag register_globals off

…will cause issues for anyone running php as cgi/phpsuexec where you cannot manipulate the php.ini settings within .htaccess. They should do it in a custom php.ini.

Do you find any specific benefit to "registering" the post in the bootstrap…

Zend::register('post', new Zend_Filter_Input($_POST));

Now we can get at a post variable with the following code:
$post = Zend::registry('post');

…versus just going…

$post = new Zend_Filter_Input($_POST);

…in the controller? There isn't anything wrong with it but it just seems a small additional layer and a little extra to take in when getting started.

Oh and this mention; "after creating a Zend_Filter_Input for $_POST, $_POST is then set to null" is very useful, one I hadn't taken note of and means you need to be careful to check for the presence of $_POST BEFORE using Zend_Filter_Input so you could well be caught out by doing this…

$post = new Zend_Filter_Input($_POST);

…then later in your code doing this…

if( !empty( $_POST ) )

…which would always be checking against a NULL'd $_POST.

Thanks for taking the time to put this together.