http://www.zftutorials.com/templates/Default/img/logo.gifhttp://www.zftutorials.com/http://www.zftutorials.com/zend-controller-zend-view/http://www.zftutorials.com/zend-controller-zend-view/Add-language-route-to-your-Zend-Framework-project-l299.htmlHow to add language routing to your Zend Framework project and be able to use URL helper in the view or layout.http://www.zftutorials.com/zend-controller-zend-view/Implementing-a-Canonical-URL-with-Zend-Framework-l289.htmlIf 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.http://www.zftutorials.com/zend-controller-zend-view/Catch-Invalid-Controller-specified-Error-l280.htmlIf 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.http://www.zftutorials.com/zend-controller-zend-view/Front-controller-plugin-et-initialisation-l274.htmlPlugin 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-Frameworkhttp://www.zftutorials.com/zend-controller-zend-view/Marrying-the-Zend-Framework-and-HTML-Ajax-l239.htmlShows how to use the Zend Controller with the PEAR package HTML_Ajax.http://www.zftutorials.com/zend-controller-zend-view/Using-layouts-with-Zend-ViewRenderer-helper-l236.htmlWhen 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. http://www.zftutorials.com/zend-controller-zend-view/Smarty-Zend-View-take-three-l229.htmlI've seen two articles describing how to integrate Smarty with Zend_View, Integrating Smarty with the Zend Framework at Zend Developer Zone and Zend Framework: Using Smarty as template engine at Dmytro Shteflyuk's blog. Both of these are very outdated by now. So here's take three on integrating Smarty with Zend_View, this time hopefully staying useful for a longer time since the Zend Framework has reached version 1 now.http://www.zftutorials.com/zend-controller-zend-view/Breadcrumbs-with-Zend-Framework-View-Helpers-l226.htmlYet another demonstration of the power of the Zend Framework. This works with ZF Version 0.8 as well as the recent release of 0.9.(x?) This time we’re going to create dynamic breadcrumbs that might look like this: Home / Article / Editing: My Post Title Utilizing view helpers, all we need to do is do a little prep work; in my case, I use a bootstrap controller that all my controllers extend.http://www.zftutorials.com/zend-controller-zend-view/Complex-Views-with-the-Zend-Framework-Part-7-Zend-View-Enhanced-l224.htmlIt's been a long, and hopefully interesting, road to Part 7. In this concluding entry to the long running, and oft delayed, "Complex Views with the Zend Framework" series I introduce the Zend_View Enhanced Proposal for the Zend Framework, elaborate on its operation, and provide some opinions on the ongoing debate over its implementation. So sit back, relax, here's another long (be patient ;-)) blog entry.http://www.zftutorials.com/zend-controller-zend-view/Custom-Zend-Framework-Router-l212.htmlOne could tweak Zend Framework's Router_Route to meet almost all your routing needs. But what if you want something beyond what that package can offer? You can make your routing dreams come true with making your own custom router, all you need to do is implement Zend_Controller_Router_Route_Interface (that's a mouth full).http://www.zftutorials.com/zend-controller-zend-view/Handling-relative-links-with-Zend-View-Helper-l210.htmlIt's 4:30 AM, and I'm sitting in an airport lounge waiting for a flight to Brussels after accidentally bumping into Zeev and a couple of other guys (Amnon and Matti) from Zend, on their way to a management meeting in the US. Since they had to board, and I'm left all alone and still have an hour or so to pass, I'm going to share a nifty little thing I found in Zend Framework a couple of days ago: A nice and clean way to generate relative links in view scripts.http://www.zftutorials.com/zend-controller-zend-view/Extending-ViewRenderer-to-Support-Layout-Templates-l208.htmlContrary to what my tutorial says, I'm one of those people that doesn't want to have to render my common header and footer templates in every single view script file. I prefer a standard site-wide layout script file that will display the content of the action script files within it. The Zend_Controller_Action_Helper_ViewRenderer action helper is a great bit of code that automates rendering a view template based on which action has been called. This is very useful, but renders the action template, not my layout template. To solve this, I am experimenting with extending the Zend_Controller_Action_Helper_ViewRenderer and overriding it so that it know about my layout template. I also prefer to use the view suffix "tpl.php" for my view scripts, so I've made my class automatically set my preferred view suffix.http://www.zftutorials.com/zend-controller-zend-view/Having-a-bad-ViewRenderer-day-in-your-ZF-app-l202.htmlOver the last week a lot of the activity on the Zend Framework mailing lists has revolved around the introduction in 1.0.0 RC1 of the ViewRenderer action helper. As of RC1 this helper has been enabled by default. Lot's of queries have been raised about how to disable, modify it, and generally how current applications can be made to work with the ViewRenderer.http://www.zftutorials.com/zend-controller-zend-view/Complex-Views-with-the-Zend-Framework-Part-4-The-View-Factory-l201.htmlIn parts 1, 2 and 3 I've been taking a look at the Zend Framework and putting together a broad picture of a potential implementation to add support for complex multi-part web pages. This refers to the practice of building a web page in an application from a number of common reusable elements. An example of such elements include header sections, footers, menu bars, widgets, etc, which surround the main content returned by any client request. In Parts 2 and 3, I introduced two useful design patterns for this purpose: Composite View and View Helper.http://www.zftutorials.com/zend-controller-zend-view/Complex-Views-with-the-Zend-Framework-Part-3-Composite-View-Pattern-l200.htmlIn the previous two parts of this series of blog posts, I've been looking at the task of implementing complex views with the Zend Framework. Part 1 looked at what complex views are, what support for complex views the Zend Framework offers out of the box, and a reference to two design patterns useful in adding further support: View Helper and Composite View. In Part 2, I tackled the View Helper design pattern.http://www.zftutorials.com/zend-controller-zend-view/Complex-Views-with-the-Zend-Framework-Part-5-The-Two-Step-View-Pattern-l199.htmlIt's been a while since I continued this series. Unfortunately real life workloads are unforgiving of the best of intentions ;-). Part 5 of our series takes a small time-out from approaching a Composite View solution to reusable Views to take a peek at a simpler approach useful for simpler types of web applications. As we've discussed previously Composite Views allow the nesting of reusable View elements, effectively building a View based on a hierarchy of Views. But often there are simpler solutions to simpler problems. One such solution is the Two-Step View pattern, sometimes called Layouts if implemented in a specific way (as we do below!).http://www.zftutorials.com/zend-controller-zend-view/Build-Multi-lingual-Websites-With-the-Zend-Framework-l198.htmlA tutorial about using Zend_Translate to write multilingual applicationshttp://www.zftutorials.com/zend-controller-zend-view/Complex-Views-with-the-Zend-Framework-Part-6-Setting-The-Terminology-l197.htmlHalf the trouble in conceiving of a extended View system is agreeing on terminology. Everyone has their own idea of the basic concepts, but without names we're left with vague descriptions. Here I'll throw out some terms, some borrowed, others mangled slightly, the rest fairly obvious. These terms all describe specific rendering processes. Methods of capturing presentation logic in neat parcels which carry specific consequences, follow object oriented practices, and provide (we dare hope) commonly sought functionality.http://www.zftutorials.com/zend-controller-zend-view/The-Zend-Framework-routing-process-l190.htmlBecause I noticed some people find it difficult to understand the routing process the Zend Framework uses by default, I decided to write a little explanation. It’s really easy once you get the hang of it, even though it may seem complicated at first.http://www.zftutorials.com/zend-controller-zend-view/Complex-Views-with-the-Zend-Framework-Part-2-View-Helper-Pattern-l180.htmlPart two of my ongoing look at the View layer of the Zend Framework turns its attention to the topic of View Helpers. The Zend Framework manual provides a fairly narrow definition of its helpers which indicates they enable complex tasks, like generating form elements, to be extracted out of views into dedicated helpers. Here I'll try to explain in greater depth the View Helper pattern which is another of those patterns in the J2EE catalog, and which adds to the range of tasks View Helpers are capable of performing.http://www.zftutorials.com/zend-controller-zend-view/Complex-Web-Pages-with-the-Zend-Framework-l179.htmlRecently I've been involved in a long discussion about the Zend Framework on the PHP Developers' Network forum. Our approach was to pick a simple application (we decided to borrow the Java BluePrints Pet Shop for J2EE) and starting from a basic "Hello World!" example for the Zend Framework work towards a fully functional example. Of course, one of our goals wasn't just to "do it", we wanted to explore the framework in greater detail, and identify how best to use, misuse, subclass, and where it was logical to even replace components should they prove deficient for our needs.http://www.zftutorials.com/zend-controller-zend-view/NY-Thoughts-and-Zend-View-Helper-Notes-l178.htmlContinuing from my post last week of notes on the Zend Framework, IÂ’d like to provide some pointers on using helpers with views in a much more automated way. Just as views can be automated—that is, you donÂ’t have to instantiate a Zend_View object; the controller does it all for you when you call $this->render() from any controller action—you do not have to explicitly tell Zend_View where your helpers reside, as the manual suggests. Instead, place your helpers in a special “helpers” folder where the Zend_Controller_ActionÂ’s initView() can find them.http://www.zftutorials.com/zend-controller-zend-view/Zend-Framework-View-Notes-l154.htmlIÂ’ve been working a lot lately with the Zend Framework for a project at work, and in a recent upgrade from 0.8.0 Preview to 0.9.1 Beta, I made a few discoveries that IÂ’d like to share, especially since the manual for the Zend Framework is sorely out of date, and many of the examples are either deprecated or no longer work.http://www.zftutorials.com/zend-controller-zend-view/Doing-the-Poka-Yoke-l152.htmlAfter getting a little impatient looking at PHP code from however many projects and seeing the typical approach of making input filtering, sql and output escaping the responsibility of the human error-prone developer, I'm now making it standard practice on any of the projects I run to dump this sorry mess. And it is usually a mess. The fact is you cannot trust a developer to manually secure source code - it's like God relaying the Ten Commandments to Moses. No matter how many burning bushes, prophets, unnatural disasters, signs and miracles you use to emphasis those ten simple rules, you can still wager there will be a bunch of folk breaking them (including myself!) left, right and centre. It's human nature to err. It's my nature to make the verb "err" redundant.http://www.zftutorials.com/zend-controller-zend-view/Automatic-testing-of-MVC-applications-created-with-Zend-Framework-l149.htmlThis article contains information on how to improve your application stability by controlling how the changes affect the Model-View-Controller Zend Framework application. As a result, you will be able to deliver better software to your customers and reduce the time needed for testing of the software.http://www.zftutorials.com/zend-controller-zend-view/404-error-with-Zend-Framework-Front-Controller-l143.htmlA few days ago I noted a quick but very usefull tip on how to handle the situation when Front Controller is unable to dispatch the request, i.e. how to display 404 error page instead of Zend_Controller_Dispatcher_Exception with message "Invalid controller specified". And it looks like the common solution for this is to create a front controller plugin. The plugin detects whether the request is dispatchable and changes module/controller/action to appropriate action that will handle the request.http://www.zftutorials.com/zend-controller-zend-view/Zend-View-helpers-in-include-path-l124.htmlIÂ’m using the Zend Framework at the moment and came across a problem with creating custom helpers for the Zend_View class. All is fine if you place your helpers either within the zend frameworkÂ’s own helpers folder (not a good idea) or within a directory in your site structure. The problem arises if you place the helpers in a folder in the PHP include path and donÂ’t know the full path to the folder.http://www.zftutorials.com/zend-controller-zend-view/Managing-404-errors-in-the-Zend-Framework-l123.htmlEarly versions of the Zend Framework had a noRoute action that was called when the correct action couldnÂ’t be found. This was a way to deal with some page not found errors. At some point it was dropped - I donÂ’t know when or why because I only started using the Zend Framework recently. ItÂ’s still possible to handle non-existent actions using the __call() method of the controller class. But thereÂ’s no obvious way to deal with all page not found errors in one place, including instances where the controller doesnÂ’t exist.http://www.zftutorials.com/zend-controller-zend-view/Controller-Action-versus-Folder-Page-l120.htmlWeb site developers are familiar with a concept that a site consists of pages but Zend Framework proposes Controller/Action idea. Undoubtedly, Controller/Action is cool but how is it relevant to real world tasks? In other words, how is Controller/Action connected to the standard form flow?http://www.zftutorials.com/zend-controller-zend-view/Extending-Singletons-l117.htmlI was wondering about how to extend a singleton class such that you could retrieve the new class when retrieving the singleton later. In particular, Zend_Controller_Front is a singleton, but what if I want to extend it later? A number of plugins in the Zend Framework, particularly view helpers and routing functionality, make use of the singleton; would I need to alter all of these later so I could make use of the new subclass ?http://www.zftutorials.com/zend-controller-zend-view/Modules-l116.htmlOne of the new features to hit the Zend Framework since 0.7 is Zend_Controller_ModuleRouter and its sibling Zend_Controller_ModuleRewriteRouter. This allows for separating out sets of controlers, models and views into their own modules.http://www.zftutorials.com/zend-controller-zend-view/Zend-Framework-Programmer-s-Reference-Guide-Zend-View-l109.htmlZend_View is a class for working with the "view" portion of the model-view-controller pattern. That is, it exists to help keep the view script separate from the model and controller scripts. It provides a system of helpers, output filters, and variable escaping. Zend_View is template system agnostic; you may use PHP as your template language, or create instances of other template systems and manipulate them within your view script. Essentially, using Zend_View happens in two major steps: 1. Your controller script creates an instance of Zend_View and assigns variables to that instance. 2. The controller tells the Zend_View to render a particular view, thereby handing control over the view script, which generates the view output.http://www.zftutorials.com/zend-controller-zend-view/Zend-Framework-Programmer-s-Reference-Guide-Zend-Controller-l85.htmlZend_Controller provides the foundation for building a website based on the Model-View-Controller (MVC) pattern. The Zend_Controller system is designed to be lightweight, modular, and extensible. It is a minimalist design to permit flexibility and some freedom to users while providing enough structure so that systems built around Zend_Controller share some common conventions and similar code layout. The Zend_Controller workflow is implemented by several components. While it is not necessary to completely understand the underpinnings of all of these components to use the system, having a working knowledge of the process is helpful.http://www.zftutorials.com/zend-controller-zend-view/Zend-Framework-Overview-l81.htmlBootstrapping and Controllers and Actions.http://www.zftutorials.com/zend-controller-zend-view/HowTo-Handle-non-existence-controllers-actions-with-Zend-Framework-recovered-l76.htmlZend Framework has two versions of Routing mechanism: Zend_Controller_Router (the default) and Zend_Controller_RewriteRouter (sparingly documented). You can easily make them call indexController::noRouteAction() on unexistence controllers, but on unexistence actions theyÂ’ll throw you an exception.http://www.zftutorials.com/zend-controller-zend-view/Using-Zend-Controller-in-subfolder-l75.htmlWho works with Zend Framework, most likely, have read the “Zend_Controller / Getting Started” Zend Framework manual article, which explains how to use Zend_Controller in the root folder of the web server. But it does not answer on the “How to run my Zend Framework application in a subfolder of the web server document folder?” question and I propose you my solutions. First is rather a hack then a recommended solution, but with it you can start the applications and examples that use standard router. The second is neater but it depends on the Zend_Controller_RewriteRouter class.http://www.zftutorials.com/zend-controller-zend-view/Zend-View-l61.htmlPart of what I love about the Zend Framework is the ease at which a person can create views for static content.http://www.zftutorials.com/zend-controller-zend-view/Phrappe-Controller-Front-Part-2-Extending-Zend-Controller-Front-l53.htmlIn the previous article I introduced a method to describe routing information within a configuration file built specially for the Zend_Config object. The example code I gave was done in XML, but itÂ’s worth reiterating that the same can be done with an INI file or a file containing a PHP array. Now IÂ’d like to extend the Zend_Controller_Front class to automate the retrieval and use of the configuration settings we capture in our Zend_Config object. WeÂ’ll use the Zend_Config object to create and build out a Zend_Controller_RewriteRouter object. Once weÂ’re done, weÂ’ll simply set it to our front controller like normal (almost), and dispatch our HTTP request.http://www.zftutorials.com/zend-controller-zend-view/Phrappe-Controller-Front-Part-1-Using-Zend-Config-To-Describe-Routing-l52.htmlSo, this all started as I read about the Zend_Controller_RewriteRouter class. While building my own framework, routing was a particularly sticky issue to iron out, so I wanted to see how Zend handled the whole issue. And they did in a fine way, apparently somewhat borrowed from Ruby On Railshttp://www.zftutorials.com/zend-controller-zend-view/Zend-Framework-Views-and-the-Front-Controller-l51.htmlhttp://www.zftutorials.com/zend-controller-zend-view/Zend-Controller-l50.htmlExcelent review of Zend Controller classes.http://www.zftutorials.com/zend-controller-zend-view/Exploring-Zend-Controller-class-of-Zend-Framework-l41.htmlZend Framework team works with gusto on the Zend Framework, great framework for building powerful web-applications in PHP. But too many peoples are confused with its seeming complexity. In this post I will try to explain architecture of most useful part (in my opinion) of Zend Framework - Zend_Controller.http://www.zftutorials.com/zend-controller-zend-view/Zend-Framework-Router-for-subdirectory-based-site-l39.htmlI started discovering of Zend Framework and was confronted with a problem. When IÂ’ve placed my test sample into siteÂ’s subdirectory (http://localhost/test/), default router tried to find TestController which is not exists of course and routed me to IndexController/noRoute. ItÂ’s not good for me. I decided to create my own router.http://www.zftutorials.com/zend-controller-zend-view/Getting-to-know-Zend-View-l36.htmlLike many other PHP developers IÂ’m keeping an eye on the progress of the Zend Framework. ItÂ’s currently still in the very early stages of development but is nonetheless worth “getting to know”. These are some notes from a play around with the current View functionality.http://www.zftutorials.com/zend-controller-zend-view/A-little-bit-more-about-Zend-Controller-plugins-l13.htmlZend_Controller_Plugin is not covered yet in the documentation but it is a powerful way of extending a controller. Briefly, Zend_Controller_Plugin is used for extending controller functionality by attaching listeners to events, which are fired (or trigged) by the controller classes.