Popular listings

In this article, we will be sending two types of e-mail messages. The first is a simple text-based e-mail that simply lists the feeds to which a user has subscribed that have been updated since the user last read them. The second is an e-mail that actually sends the new posts that have arrived since the last time the user read a particular feed.
We will first update the database so every feed has an accurate last-updated value. We'll also update subscribed feeds with a last-pulled value when the reader views them. Finally, we'll create the routine that compares these dates, creates the e-mail messages, and sends them

Zend_Acl est utilisé pour dire si un objet a le droit de faire une action ou non. Avec Zend_Acl, on va pouvoir dire : "tel internaute a le droit de lire le forum A mais pas d'écrire dedans, alors que dans le forum B il aura le droit de lire et d'écrire des messages".

One 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.

Like many frameworks, the Zend framework is fairly heavy by itself. Today, I decided to do some profiling on code running to see how all that load was distributed and see if there was any way I could pinpoint the problem to one particular location. I found a major one. Just to get things booted up and route the query to the appropriate method, over 40 files get included via require_once(). IO is definitely a problem here. I didnÂ’t keep the original cachegrind trace (from xdebug), but over half of the processing time was lost in those calls. Even if using APC or some sort of op-code caching, calls still have to be made and the code has to be retrieved.

Zend Framwork v0.6 has introduced new MVC code and one of the changes is that Zend_View_Interface now exists to allow for easy implementation of other templating engines other than PHP based ones like Zend_View or Savant.
We use Smarty at work and when we migrate our content management framework to Zend Framework, we intend to continue using Smarty. Hence, I've created AkCom_View_Smarty to play with how we are going to use Smarty within the Zend Framework. I think that part of the release also has an implemention of Zend_View_Interface that uses Smarty, so it's worth looking at that solution too!

I 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.

I started to play around a bit to integrate the Smarty template engine into the Zend Framework. My ambition was to minimize the required code in the controller actions but stay close to the given Zend_View API. I also wanted to integrate the Smarty caching feature. Here is the code I came up with.

In 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.

It'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!).

Zend_Filter provides a library of static methods for filtering data. For input filtering, you should use Section 9.2, “Zend_Filter_Input” instead, because it provides a framework for filtering input using the methods provided by this class.