I never use things such as "return sfView::ERROR" but instead I send flash messages to the user, and/or use only one specific "error template".

Therefore it's really boring to read and type all those "Success" suffixes on template filenames.

Split testing is a powerful tool for improving websites & applications. Unfortunately Google Web Optimizer et al aren't very good at supporting dynamic pages.

Symfony should include either as core or as a plugin, a way to easily segment users and then select a template to display to the user based on their segment.

Additionally, some wrapper class to send data to analytics packages would complete the process of making split testing dead easy to implement.

Actually, it seems we can not build our doctrine schema from a visual editor file.

To me, its a very big lack for a profesionnal framework : its impossible to work on a YAML file to define 80 tables and more than 60 fields in some of them.

This feature is a must have I think, and should be present with a plugin or in the core. Some plugins exists for Propel (dia, DBDesigner), but not for Doctrine (futur offical symfony ORM).

DIA could be a good choice (open source, xml files).

instead of generating new CRUD source files (template + actions + forms + filters) for every model, it would be nice to have a default skeleton and reuse that with introspection (like django does). in this way you will just override the templates/forms/actions that you wish to change (just in case), leaving the rest unchanged without producing new sources files for every module.

There are more tools which support gettext and it would be nice if the support in symfony would be as good as for the xml format.

phpunit is the standard for unit tests and should be used instead of the lime framework. It brings lots of features and is also class orientated instead of script orientated like lime.

Some texts are the same for all (like the "send", "cancel" buttons, "next", "previous" links, etc).

Why not make the xml catalog files inherit from other xml catalog files, so we could define the above kind of words just once, but still have different catalog files for different forms and etc.

Add more widgets and/or port already existed widgets to other js/orm (like sfWidgetFormPropelJQueryAutocompleter so it'll work with prototype and with doctrine).

Implement Rich Text Editor form widgets for TinyMCE and FCK editor.

Before releasing new version, please write the documentation, release both version and documentation togather.

Complete Form API documentation

When working with multiple applications within the same vhost (with subdirectories), the user session is shared for every applications. Attributes can be namespaced, but not the authentication nor the credentials. It would be great to have an way to specifiy per-application credentials (and maybe authentication).

Since PHP 5.3 this function will ship with PHP, but it can also be installed with pecl, and I think this would bring some performance improvements to symfony

give some standard data object,such as arraylist,tree and so on.

BDD is really cool, as Symfony already has a good testing framework, perhaps it could accommodate BDD too, with a place to check in user stories in BDD style, and generate the tests templates from it. or even just be able to reference the tests that ecapsulate the user story.

If no one knows what I am talking about, google behavior driven development, you will like what you see.

support right to left languages, possibly by adding direction to sfCultureInfo and right to left intelligence to asset helpers? http://trac.symfony-project.org/ticket/5636