When developing blocks in concrete5, you will most likely store data related to each block instance, such as settings. This data can easily be retrieved from within the block’s controller or in the block’s view scripts.
This article shows how to add foreign key constraints to concrete5 packages or blocks by using db.xml files or a package controller. Using foreign keys is important to help ensure data integrity in the database.
It is often useful or necessary to include parameters in URL addresses. Many people use one of PHP’s superglobals for this, but that is not a pretty approach. In this short article, you will learn a better solution while maintaining pretty URLs.
Displaying the advanced TinyMCE editor in your concrete5 forms is very easy, but finding the documentation on how to do it is not so easy. In this short article, we will show you how to accomplish it with just a few lines of code.
Avoiding hard coded dependencies is something the PHP community is still trying to grasp. The use of OOP tools such as interfaces are still making its way into the PHP programmers’ minds. Luckily, Zend Framework 2 makes both approaches possible when it comes to loading modules with the Module class.
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.
Getting Apache to work together with Dropbox turns out to be slightly more difficult than most would have anticipated. Adding a virtual host to point directly to a Dropbox folder will only get you a 403 Forbidden error. In this article, we will solve this problem by using symbolic links.
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.