By default, the skeleton application in Zend Framework 2 requires you to include the module name in all of your URLs. This can be changed quite easily by making edits to an existing route. After following this tutorial, you will once again have pretty URLs just like in Zend Framework 1.
To many people who are used to Zend Framework 1, the process of just installing Zend Framework 2 seems overly complicated. In this tutorial we will step through installing Zend Framework 2 on OS X Lion in just a few minutes.
Keeping form classes together in each module is the preferred way to store them, rather than in the library folder, for instance. Keeping the Zend Framework naming conventions in mind, this is a very easy task.
Using a modular directory structure can logically separate parts of an application. By default, a Zend Framework application does not make use of such a structure, so in this article we shall see how to easily change this.
It is often necessary to add data to form elements from outside of the form. Examples of scenarios where this would be useful include data fetched from a data store or data saved in sessions. In this article, we will discuss two ways of doing this, one of which has several advantages over the other.
In the Zend Framework, there are many ways to add custom routes to a project. Adding them to the application.ini file quickly makes the file very big and harder to maintain. In this article, we will show two ways of writing custom routes in a separate configuration file.
It is not an unusual task to want to set the default values on elements in a form. Zend Framework provides multiple ways of accomplishing this, but as demonstrated in this article, the setDefaults method has surprising behavior.