Hi, While some issues have been addressed there are still lots of issues open here.
A pull request with some API tweaks has been partially merged: https://github.com/fabpot/symfony/pull/198 However the planned Message class is not yet implemented: http://trac.symfony-project.org/ticket/9346 I guess we also need better twig integration, since right now in order to iterate over all flash messages one needs to do something like: {% for key, flash in _view.session.get('_flash') %} <div class="{{ flash }}"> {% trans key from 'DoctrineUserBundle' %} </div> {% endfor %} However, I somehow still feel like we do not have a good plan for how to achieve what we want. Maybe we do not even know properly what Flash messages are supposed to achieve? To me flash messages are supposed to be "self contained", aka it should be very easy for anyone to consume flash messages without having to know much about the content. Furthermore flash messages form one container shouldnt collide with others. Furthermore I wonder if flash messages should be used only for stuff to be shown in a template? Are they also for non display stuff? Aka should they be used to pass a message to the next controller in the next request? In this case the remove() method might be necessary to easily remove the flash before it gets displayed in a layout where all flash messages are shown automatically. Why aren't they used in the security firewall for auth errors for example? I do not pretend to know the answers, but I think there is a need to discuss this further. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
