> I am not quite following. Are you saying that you did or did not include
> parent::postDispatch($request) inside your extended class?
>
> FWIW: postDispatch() of the plugin is where the Layout component determines
> whether or not to initiate the final step in this "two-step" layout process
> with respect to the controller dispatch cycle. So if you are gonna extend
> this class, you MUST call postDispatch() or offer similar functionality as
> to what that method actually does.
>
Ok, thanks, then this is the intended purpose of this call. No bug at
all, maybe into documentation should be added this as a MUST add....
> The bigger question is: Why? Unless you are altering the way Zend_Layout's
> controller plugin does its job, its just as easy to create your own plugin
> that would run before the Layout Plugin and register it with the Controller
> Plugin broker.
>
Yes, is possibly to use a Controller Plugin as well. Since most of the
tasks were related to view side i was thinking is best to use the Layut
plugin.
--
Best regards,
Cristian Bichis
www.zftutorials.com | www.zfforums.com | www.zftalk.com | www.zflinks.com
没有评论:
发表评论