I don't mean to beat a dead horse, but, no, it's not there. That says nothing that isn't already contained in this thread.
Please take my words as constructive criticism and understand that cake users are not mind readers. Meanwhile, the manual continues to refer to the session component with no mention of the helper. And nowhere is it documented what methods and properties are available with this new helper or is there a warning to people out there who may be using any and all methods and properties in their views. A security fix is always a good thing, but bundling it with changes that can break existing installations without warning people how that might happen is not fun. "It is recommended that everyone upgrade and change all references to $this->controller->Session in the view to the new helper, $session." That won't work if someone is using an unsupported sesssion method in the view. In fact, the announcement doesn't even mention that any kind of access to the session component from a view is totally unsupported now. Instead, it hints at a future day when that will be the case and that it's recommended to start migrating code over. A typical user sees that and thinks, 'hey, security update, I need to do this.' I really am not trying to be argumentative, and perhaps I'm nitpicking; my case is not a big deal. But then, this wouldn't have consumed so many back and forth posts if my initial valid point had not just been dismissed out-of-hand without a second thought. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php -~----------~----~----~----~------~----~------~--~---
