Re: Checking RequestHandler::isPost() vs Controller's data

2010-03-24 Thread barduck
It looks to be somewhat of a mess, but the bug is not in RequestHandler itself. When you create the form, if you don't specify it, FormHelper-create assigns the method POST or PUT to the form depending on whether the record already exists or not. So when there is a record (edit), the verb is PUT

Re: Checking RequestHandler::isPost() vs Controller's data

2010-03-10 Thread Jimmy Bourassa
Thanks Miles, Can you be a bit more specific regarding the bugs you've seen? Thanks, On 10 mar, 00:17, Miles J mileswjohn...@gmail.com wrote: Yes exactly. RequestHandler would force it only if the HTTP method is POST, where as $data would work no matter what source it came from. I prefer

Re: Checking RequestHandler::isPost() vs Controller's data

2010-03-10 Thread Miles J
The main problem I always would run into would that it would not recognized a POST, so the form would do nothing. I would usually have to submit it twice before it worked. Never figured out why it did that. On Mar 10, 7:03 am, Jimmy Bourassa jboura...@gmail.com wrote: Thanks Miles, Can you be

Checking RequestHandler::isPost() vs Controller's data

2010-03-09 Thread Jimmy Bourassa
Hello, I realized that everyone seems to do an empty() call on $this-data in controllers in order to check if data has been posted or not. Is it just me or RequestHandler::isPost yields better results? This would allow to pre-fill Controller::$data in various situations. Thanks, Check out the

Re: Checking RequestHandler::isPost() vs Controller's data

2010-03-09 Thread Miles J
Yes exactly. RequestHandler would force it only if the HTTP method is POST, where as $data would work no matter what source it came from. I prefer RequestHandler, but it has been buggy sometimes. On Mar 9, 6:10 pm, Jimmy Bourassa jboura...@gmail.com wrote: Hello, I realized that everyone seems