Zend Framework 1.11.5 Released

April 7, 2011

News, Zend Framework

The Zend Framework team announces the immediate availability of Zend Framework
1.11.5, our fifth maintenance release in the 1.11 series. This release includes
a dozen bug fixes.

You may download ZF 1.11.5 from the
Zend Framework site.

For a full list of resolved issues, you can visit the changelog:

This version includes three notable changes.

First, Zend_Gdata has been updated to use HTTPS for those GData services that
support it. This should be a seamless change for most GData users.

Second, Zend_Application now supports “.dist” configuration files. This allows
you to create the following:

application/
    configs/
        application.ini.dist

and, while still specifying application.ini as the configuration file, fall
back to the .dist variant. This is useful for working on teams, where
individuals may wish to tailor their configuration environment without
necessarily checking in those environment-specific changes. Thanks goes out to
Wil Moore for this improvement.

Third, Mike van Riel offered to convert our API
documentation generation to DocBlox. We’d
already been considering it for ZF2, but on seeing the flexibility of the
templating system, and, more importantly for us in terms of packaging, the speed
and minimal resources it utilizes in generating the output, we were sold. (API
documentation generation time was reduced from taking 80-100 minutes to less
than 10.) You can view the results for yourself.

I’d like to thank everyone who contributed code to these releases, including
those who submitted patches, translated documentation, or reported issues. Keep
your eyes peeled for another maintenance release at the end of next month!

About Matthew Weier O'Phinney

Matthew is an open source software architect, specializing in PHP. He is currently project lead for Zend Framework, a project with which he has been involved since before the first public preview release. He is a Zend Certified Engineer, and a member of the Zend Education Advisory Board, the group responsible for authoring the Zend Certification Exam. He contributes to a number of open source projects, blogs on PHP-related topics, and presents talks and tutorials related to PHP development and the projects to which he contributes. You can read more of his thoughts on his blog, weierophinney.net/matthew/.

View all posts by Matthew Weier O'Phinney

14 Responses to “Zend Framework 1.11.5 Released”

  1. fdrouillard Says:

    It would be helpful to those trying to learn ZF if there were an explanation on how to install and use the downloaded documentation.

  2. poisa Says:

    I’m thrilled that there are still updates being pushed to the 1.x branch! Thanks!

    One minor suggestion regarding the new API docs: I think it would be more readable having the methods listed each in their own line rather than in a comma separated fashion. Just because it’s faster to skip to the one you are looking for if they are laid out that way.

    Other than that I don’t mind the new layout!

  3. stjuboss Says:

    It’s nice to see improvements! Good job Zend Team!
    But there is still long way to go – docs still can be improved, look at the beautiful and very elegant docs for Extjs : http://dev.sencha.com/deploy/dev/docs/?class=Ext.Button
    Current version of ZF docs comes nowhere as close..

  4. chrisdeman Says:

    It be nice when the API docs get an autocomplete like yii has:
    http://www.yiiframework.com/doc/api/

  5. weierophinney Says:

    While the comments here all tend to towards disliking the new API docs, I’m getting good reviews elsewhere (twitter, lists, etc.).

    Anytime there is a change in layout, it will please some, and annoy others. If you feel there are real usability issues, please report them to the DocBlox project (http://www.docblox-project.org) so that Mike can help us improve them. In the meantime, I stand by our decision to switch systems; the new system is faster and more flexible, under active development, and future-tolerant towards PHP 5.3. This is positive step forwards.

  6. weierophinney Says:

    The download link has been corrected at this time.

  7. zendsurfer Says:

    Yes the new API Doc layout has not improved. I think there is some template work to do. But I’ll use your Framework anyway! Thanks

  8. mmagnet Says:

    The link in ‘You may download ZF 1.11.5 from the Zend Framework site.’ is wrong. Lose the ‘.html’ part and it works fine (http://framework.zend.com/download/latest)

  9. gabelde Says:

    What happened to that good ol’API – ok. ok. phpDocumentor is nearly dead, but still neat and got a better usability than this docBlox theme. I really hope you can get an optimized theme for the API.

  10. oreales Says:

    I am sure there are reasons to generate API Doc with DocBlox: perfomance, speed… but the end result it is not so clear as it was the old API Doc: Easier navigation, It was easier to understand components interrelations with an overview…

    Great Job, but API Doc change it is not so positive to me.

  11. weberbodman Says:

    thank you very much for your great work!

    (i cannot see why it is necessary to load the full navigation?
    when i use the api i always need only a part of it.
    a partial navigation with breadcrumb would be enough for me.
    or just use ajax for loading the tree…)

  12. weierophinney Says:

    @chelmertz: yes, still frames. The primary reason has a ton of facets, all of which are technical: with a codebase the size of ZF’s, we have to consider the size of the navigation. If each page embeds the navigation, then each page ends up being something like .5MB in size — making for a large payload on each and every request, which slows down the experience and utilizes a ton of bandwidth. On the disk itself, we also then need to worry about storage: when we generated the docs with embedded navigation on each page, the docs were taking close to 1G — for a single version! Finally, when generating the docs, we consume far fewer resources and the process takes far less time if we can generate the navigation once, rather than on each page.

    I realize that it’s not an ideal situation, but hopefully you can see that we’re doing it for good reasons.

  13. chelmertz Says:

    I think it’s great that you’re still pulling innovations even though the focus is mainly on zf2 now.

    Never the less, how come ZF still has an API-doc supported by frames? You can not link properly to a page since the navigation is non existing when you arrive on it. With that comes the bonus of not having the url changed, which means I have to find the link to the current page in order to link to it.