Zend Controller & Zend View

In this article I discuss what I call Fat Models and how to create them using the Zend Framework. I also introduce an abstract base class that wraps up the idea in a reusable way. I finish up with a simple example showing the full MVC set

Shows how to configure a modern Zend Framework - I use 1.10 - application to use the Smarty template engine. Importantly, the tutorial shows how to use both Zend_View and Zend_Layout.

A Zend_View class extension to add an extra view layer, inspired by Joomla

A quick tip on how to deal with Zend Framework directory structure and the public document root directory in most shared hosting accounts, using mod_rewrite and an .htaccess file.

How to add language routing to your Zend Framework project and be able to use URL helper in the view or layout.

If your project runs on Zend Framework, it is very easy to create canonical link by retrieving the controllers/actions and Parameters that you are using in the current URL.
This tutorial will give a quick method for creating Canonical URLs.

If you work with Zend frame work and calls a non existing Controller then it causes showing an ugly error message on the screen telling the Controller not found.

Plugin de configuration du contrôleur frontal et initialisation de l'application. Largement inspiré de l'article de Matthew sur la DEVZONE : http://devzone.zend.com/article/3372-Front-Controller-Plugins-in-Zend-Framework

Shows how to use the Zend Controller with the PEAR package HTML_Ajax.

When working with views in the Zend Framework, you normally have a view for each action in your controllers. Each of the views run a view script, which then include header and footer views in them. This may lead to some repetitive code and may cause a problem if you want to modify the way the header and footer are included in your views.

A better approach could be to use a "layout". A layour is a master view, perhaps similar to the master page in ASP.NET - it has the header, footer and all other code except the content. It effectively replaces the header and footer and is used to include the content (the action view script) inside itself instead of the action view script including the header and footer.